#geoff
1 messages · Page 1 of 1 (latest)
hello! If the payment is off-session, 3DS won't be requested for i.e. the PaymentIntent won't go into requires_action state [0]. In the rare case that the issuer requires 3DS and the payment is off-session, the issuer will decline the card with authentication_required [1]
[0] https://stripe.com/docs/payments/intents
[1] https://stripe.com/docs/declines/codes
Then does 3DS get triggered if the SetupIntent is created with usage="off-session"? How does this differ from PaymentIntent usage="off-session"?
Or, should I not be creating SetupIntent's with usage="off-session" ? Is this reserved for a situation where I'm creating a new SetupIntent and the user is not on the line?
you must create SetupIntents with usage="off_session" if you intend to use the PaymentMethod for payments off-session in the future
if authentication is required during the setup of the PaymentMethod, then it'll be requested for accordingly
whether it's required or not depends on a variety of factors.
What's the concern here regarding 3DS?
Mostly just that we worry about another possible route for payments to fail that we have no control over, is difficult to explain and will degrade our user's experience. Outside of just an insufficient funds or something else
payments can always fail for various reasons. For example, you could see generic "do_not_honor" declines : https://support.stripe.com/questions/decline-code-do-not-honor. Ultimately, it's up to the issuer to decide whether to decline or accept the payment. I'd recommend that you ensure you make sure that you're prepared to bring the customer back on session to provide another card in the situation that payment fails