kratos6753

[uneven crown]

hello! can you share your account id for me to take a look at your current integration?

your radar rule is already set to only request for 3DS if required. Can you share an example PaymentIntent id where it's requesting for 3DS (for an already added card)?

for context, the issuer is the one who decides if 3DS is required.

If your customer's card was originally saved on-session with permission to charge their card later [0], you can re-use the card details at a later date to attempt a charge using off_session=true [1].

However, it's still up to the issuer whether they require 3DS. In the event 3DS still needs to be performed, you will need to manually bring the customer back on-session to perform/complete the authentication.

[0] https://stripe.com/docs/payments/save-and-reuse, or https://stripe.com/docs/payments/save-during-payment
[1] https://stripe.com/docs/api/payment_intents/create#create_payment_intent-off_session

[golden sapphire]

I don't have an example with me now. Already added card wouldn't ask to re-add, right? But, 3ds authentication may be requested while payment is being made.

[uneven crown]

If payment fails, the PaymentIntent would return to requires_payment_method status and you should collect the payment method again : https://stripe.com/docs/payments/intents

If you use off_session=true and the PaymentMethod requires authentication, the PaymentIntent will simply fail because the customer isn't on_session and can't authenticate

I suggest that you test the scenario using a test card that always requires authentication : https://stripe.com/docs/testing#regulatory-cards

[golden sapphire]

Sure, will take a look.

Thanks.