#kiro34-paymentintent
1 messages · Page 1 of 1 (latest)
Hi there!
- I'm not sure, let me look into this.
- Can you share a PaymentIntent ID where you saw this issue?
Thank you very much! Please find this paymentIntent where it failed ch_3LBatpDh91j58svV2sbfESdc, then the one where it succeeded : pi_3LBatpDh91j58svV2fC301kW
I think this is normal and how Stripe works. When you create a charge, Stripe will talk to the bank to try to directly make the payment. At that point the bank may decline because 3DS is required, so Stripe automatically retry the payment with 3DS. So on your end you can completely ignore that first charge.
Ok I see thank you! Can you please take a look at this one? It seems the customer attempted to pay multiple times pi_3LAwzmDh91j58svV15uasv4R before succeeding and the error is the same. I'm concerned that this is not normal Stripe behavior if the customer has to enter his credit card details again?
Why do you think they attempted to pay multiple times?
If you look at the bottom of the paymentIntent page, there are related payments
You can see the customer attempted to pay with two different cards. If we only focus on the payment attempted with the same card (ending 4851), you can see the customer attempted 2 times before succeeding
And when you click on these paymentIntents, the error is Bank declined authentification The bank returned the decline code authentication_required.
Got it! For questions about declines in live mode, I recommend asking Stripe support directly here: https://support.stripe.com/?contact=true