#sanjeev-future-payments
1 messages · Page 1 of 1 (latest)
Hi there 👋 sorry to hear you're running into problems. Would you mind clarifying what you mean when you say:
But it gives me authentication required error every time for offline payments.
After creating SetupIntent, when I use the payment method to create a PaymentIntent with confirm=true, It still requires authentication.
When you create the Payment Intent for that, are you setting the off_session parameter to true?
Yes
Hm, could you provide the ID of a Payment Intent where you saw this behavior?
Thats when it gives me error that authentication required
Ok
pi_3KYtGuLgXGrn8mLp247b1Xun
This is id of payment intent
Which I have created using payment method
And it gave me below error
Your card was declined. This transaction requires authentication.
It looks like you're using a test card that also requires authentication there, so what you're seeing is expected behavior. Could you try with this test card number, that doesn't require authentication for off-session payments if setup first:
4000002500003155
https://stripe.com/docs/testing#regulatory-cards
Ok let me try
It worked for the above card
But in live environment, wont all cards require a 3d secure authentication? So will this work with real cards?
That can actually be hard to predict. When you go through the Setup Intent process, we store the necessary payment details, but also if you tell us the payment method will be used off-session then we take steps to try to optimize the customer's experience. Part of this is that, for off-session payments, we send an exemption request to the issuer asking to be exempt from the 3DS/SCA flow. What makes it tricky is that it's up to the issuer whether they accept that exemption request (typically they do) or require 3DS anyway. So you'll want to prepare flows for both scenarios.
Alright, Got it. Thanks for your help.
Any time!