#zzking
1 messages · Page 1 of 1 (latest)
btw: in the second case I also received a charge.failed event with "failure_code" saying authentication_required
Hi
yes when you use a card that require 3DS, that mean in all case the user need to authenticate their payment throw 3DS
if they all mean "SCA is required", then I wonder what's the benefit of using "off_session: true" in paymentIntent ?
would it make Stripe "optmise" the payment flow behind the scene ?
👋 stepping in
If you set up a card for future use and then charge it off_session we apply for a 3DS exemption with the issuer
You basically want to test with the 4000002500003155 card
This card requires authentication for off-session payments unless you set it up for future payments. After you set it up, off-session payments no longer require authentication.
How do you setup a card for "future usage" ? I'm building a setupIntent first according to here: https://stripe.com/docs/payments/save-and-reuse , does it count as "setup the card for future use" ? OR is there some other param that I should set for paymentIntent as well ?
Yep a SetupIntent works
The other way is to pass setup_future_usage with a PaymentIntent
oh thanks, we want to save a card details first WITHOUT a payment, so I guess I have to create a setupIntent first, right ?
Yep that's the correct flow
thank you. And suppose if I setup everything like indicated above (create setupIntent first, then create paymentIntent with "off_session" set to true), then when I receive "charge.failed" or "payment_intent.failed" event with error "authentication_required", I can assume that means SCA is required by the bank , right ? ( I know SCA can still happen even if everything is setup correctly)
Yep exactly
In that case you want to bring your customer back on-session to handle 3DS
This should be pretty rare though
nice , thanks for the help .