#kudos112
1 messages · Page 1 of 1 (latest)
That decline code indicates that the bank requested 3DS/auth for the payment, so you need to handle that. Recommended way to is to do that client-side with Stripe.js, but you can redirect your customers server-side if you prefer: https://docs.stripe.com/payments/3d-secure/authentication-flow#manual-redirect
Okay great, every time for a payment method I have to initiate this process?
Depends if 3DS is requested for the payment, you'll know because the status transition to requires_action
Okay. So basically we need to use the same payment intent secret for client side payment?
well if you're using stripe.js to handle 3DS then yes you pass the client_secret of the PaymentIntent to functions like confirmCardPaymenthttps://docs.stripe.com/js/payment_intents/confirm_card_payment#stripe_confirm_card_payment-attached
Thanks. Let me try the suggestions if something I need to ask I will get to you guys 🙂.
Can you tell me one more thing, how much expiry time does a payment intent have?
what do you mean precisely by expiry time?
yes
sorry, I don't understand
Sorry, I mean to say is there any expiry time for payment intent secret that is generated by the server?
Plus If i got the issue of authentication_required then will the user have to enter the card details again while authenticating?
@hollow ruin @wide obsidian
no there's no expiry time, the PaymentIntent can stay in status:requires_action forever.
then will the user have to enter the card details again while authenticating?
no