#nunu
wind perchBOT
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- nunu, 23 minutes ago, 23 messages
strong steppe
many of our connected accounts raising issue that their payment failed , when we checked we can see the error "Your card was declined. This transaction requires authentication.", in attaching card to a customer in this endpoint POST /v1/payment_methods/pm_1Oxxxxx
we can see that there is a change in stripe recently https://support.stripe.com/questions/october-2023-default-3ds-radar-rule-update
pls check req_T5qFqXJKGIopwH
will it effect?
is there anything for us to do code change?
or the connected account need to do any settings change?
many Sweden based business reported issue
fair elm
Attaching a card to a customer can trigger a card validation, which may requires 3DS. And so the attachement failed.
Can you give more context to your flow? Why are you attaching a card and not using a SetupIntent for example?
strong steppe
This code was done 3 years ago according to stripe doc (sca change) and everything was working till now,
our flow is that :
create customer
attach payment method
create payment intent
fair elm
That's a pretty bad flow, because, as you saw, this can request 3DS multiple times in a row, which result in failed payments.
Instead you should:
- Create a customer
- Create a PaymentIntent with
setup_future_usageto charge the card and alos save it for later - Confirm the PaymentIntent on the frontend with the PaymentElement
This si covered in details here: https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements
strong steppe
ok , but now in our development server , inorder to support RBI guidelines india we removed the payment methd attachment
instead using "payment_method_options": {
"card": {
"mandate_options": {
will this resolve problem
fair elm
Oh you are in India, I didn't see this, sorry.
fair elm
Unfortunately I'm not very familar with RBI. So I would recommend to ask Stripe support about this: https://support.stripe.com/contact
strong steppe
ok let me ask one thing , the sca change which was i think 3 years ago, that time we change dour code according to stripe doc at that time
create customer
attach payment method
create payment intent
this flow
it is not the correct methid>
method?
fair elm
If this question is about RBI then I don't know. If you are asking more generally, then like I said this is not a great flow. We no longer recommend using the "attach payment method" endpoint. Instead directly use a PaymentIntent with setup_future_usage (or a SetupIntent)
strong steppe
no this not about rbi
this is about sca
fair elm
Then yes follow the steps I mentionned above:
Instead you should:
- Create a customer
- Create a PaymentIntent with setup_future_usage to charge the card and also save it for later
- Confirm the PaymentIntent on the frontend with the PaymentElement
This is covered in details here: https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements
strong steppe
ok thanks
one more question
as a quick solution any settings change in stripe dashboard will help to solve the problem
fair elm
No sorry, it's the bank that is requesting 3DS, not Stripe.