Anar

[sour iron]

hi! do you have an example of a PaymentIntent pi_xxx that required 3DS when you didn't expect it to?

[sterile jasper]

sec

pi_3MP3EUKnG67zhble1W359fFC

I created PM: pm_1MP3A5KnG67zhbleqzY9YHIT
And I confirmed it using 3d secure confirmation url

in here: pi_3MP3BVKnG67zhble1f74yaST

[sour iron]

you should pass off_session:true if it's a recurring payment your server is processing, so we know to treat it as merchant-initiated and claim exemptions

[sterile jasper]

that's all? 🙂

[sour iron]

https://stripe.com/docs/payments/save-and-reuse?platform=web#charge-saved-payment-method

[sterile jasper]

thank You so much

appreciate it

[sour iron]

no, you also need to be using a test card that supports this

you need to use the 3155 card to test this flow
https://stripe.com/docs/testing#authentication-and-setup

[sterile jasper]

yes I'm using it

[sour iron]

no you're not, that example you shared was using 3184

[sterile jasper]

ah 🙂

understood

but is it possible in reallife that 3184 may exist

[sour iron]

yep

the docs linked above cover what to do if that scenario occurs

[sterile jasper]

🔥

thank You