#Tony Thomas - paymentintent
weak crest
3184 is a card that always requires authentication though
try 0446
list of test cards : https://stripe.com/docs/testing
lunar pelican
oh yeah, I know. It works with other cards. I always test with this carad to emulate the worst possible case
previously, when I had the things in this message: #976747231547883540 message
It used to move to a pending state instead
warm vortex
When you create a PaymentIntent with off_session: "True" with a card that requires 3DS, the PaymentIntent will fail since the user is not on session and cannot go thought the 3DS flow.
lunar pelican
Aha, okey. That was one of the major changes I did in this testing release. How would you recommend to fix this though ? 🤔
In our case, this charge happens off-session (as part of an external approval process). And we do really want to handle these cards (meaning, we want to keep the PI alive)
warm vortex
You need to catch that error, and then ask your users to come back to your website to go thought the 3DS flow.
You can see a quick example of this here: https://stripe.com/docs/payments/save-and-reuse?platform=web#charge-saved-payment-method
lunar pelican
Aha, but question though @warm vortex - when this happens, is a payment_intent.payment_failed sent immediately on the webhooks ?
warm vortex
Yes you will get a payment_intent.payment_failed event.
lunar pelican
okey, I will have to adjust some logics there then.
One more question @warm vortex : Is a PaymentIntent with a payment_failed status recoverable ? In the sense, can I retry it with a different payment method ? I know this is possible for incomplete PIs, but just asking.
Eg: the PI from above