#JuliusVit-3DS-off-session
1 messages · Page 1 of 1 (latest)
Hi 👋 no, there is no guarantee that a customer won't need to complete 3DS again for future purchases after setting up their payment method via a Setup Intent.
It's up to the issuing bank to decide whether they will require 3DS for each transaction. When a payment method is set up with us, we request exemptions from 3DS/SCA for future off-session payments but the issuing bank decides whether they will grant that exemption.
Your flows should be prepared for the possibility that off-session payments may fail due to the customer needing to complete an authentication challenge.
will I get some specific error in that case?
The payment may error with an authentication_required decline code depending on the information that the issuer returns to us alongside their decline decision.
This is talked about in a bit more detail in the last 3 paragraphs of this section:
https://stripe.com/docs/payments/save-and-reuse?platform=web#charge-saved-payment-method
Do you know if that situation where 3D Secure is required afterward is quite rare? We have been integrating other payment service providers previously and didn't observe that happening.
It's hard to give a definitive answer on that as it largely depends on the issuer. Anecdotally, I don't see it happen frequently, but I would still recommend that your flows be ready to handle the scenario.
Let's say I split my payment process into two parts where first I create a payment intent, but don't capture the amount immediately and second part where I capture the amount. Will I get 3DS auth request only on payment intent creation or only on capture request or it can happen on both?
It will only happen when the payment intent is confirmed (which I am assuming you are doing while creating the PI here)