#Kamesh
covert ridge
odd jungle
Hi, @plush lotus let's chat here
Test scenario setup intent: seti_1MUf4dL9xUjrGzqOYn3NpHwS
payment method: pm_1MUf5HL9xUjrGzqOKXUEohgj
plush lotus
Thanks
odd jungle
You're trying to confirm why a SetupIntent that went through 3DS is requiring another authentication? Looking at these objects now.
plush lotus
yes, thanks
odd jungle
What is the pi_ id that is requiring 3DS authentication for this SetupIntent?
plush lotus
paymentIntent create has failed with this error. NOTE we are also passing confirm:true while creating payment intent
odd jungle
Can you share this request id please? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
If it's this Payment Intent, pi_3MUf5zL9xUjrGzqO0gWj5fj5 it does not look like you passed the correct parameter. When you create the Payment Intent, you'd need to set off_session: true https://stripe.com/docs/api/payment_intents/create#create_payment_intent-off_session
If that is not the correct Payment Intent, can you share the correct request id please so I can further investigate this on my end?
plush lotus
thanks. looking
sorry, please give me some time, I am struggling to login to dashboard
will get back soon
please keep this session alive
plush lotus
requestid for setupIntent - req_qoi7ZwISLti5F9
request id for payment intent - req_B1WTn6R4C6oRLU
wide hull
you're using the test card ending with 3220 (https://stripe.com/docs/testing#three-ds-cards), this test cards requires 3DS for the payment to be successful.
you should use 3155 if you want to test the flow where the test card is successfully setup and you want it to go through off_session payments without 3DS : https://stripe.com/docs/testing#authentication-and-setup
plush lotus
thanks let me try. Is all the parameters supplied correct?
wide hull
it looks correct from a quick scan, but as usual, you should run through all the possible scenarios to ensure it meets your requirements
plush lotus
thanks. let me try and get back
plush lotus
Hi, how about test card number for 3ds2?
can you please let me which card number we can use for testing 3ds2 scenario
wide hull
do you mean the corresponding test card to 3155 but using 3ds2 instead?
plush lotus
yes
wide hull
we don't have one. there's really no need for it though, the flow is the same
plush lotus
how do we ensure that it works for 3ds2? considering this is payment flow, we need to show it works with test numbers. what other options do we have ?
wide hull
since you're using stripe.js to handle 3DS, if it works for 3155, you can take it as it works for 3DS2 also.
plush lotus
thanks. But I wonder what is the purpose of having a dedicated test nunber for 3ds2?
wide hull
it could be specifically for users who handle 3DS2 flows on their own i.e. they don't use stripe.js
i don't have the background on why though
plush lotus
can you please get more information. this is critical for us to proceed.
number ending 3220 is specifically for 3ds2, and that doesn't for our scenario. so we really to understand and document why before we can proceed further. thanks
wide hull
i'd suggest reaching out to Stripe Support then, they'll check on it and get back to you
plush lotus
can you please point me to any documentation where it suggests if code works for 3ds, it should work for 3ds2 as well,. we can use that as a refference for us to proceed. thanks
wide hull
there's no such documentation that i'm aware of which explicitly states this. stripe.js will attempt to complete any required actions (if necessary). We abstract away the complexity, and ensure that you can handle the response the same way (whether it's 3DS1 or 3DS2).
i'm not sure how you expect 3DS1 / 3DS2 to differ in terms of your handling
plush lotus
considering we have a 3ds2 specific number, there must be something different between 3ds and 3ds2 test cases isn't it? otherwise I don;t see a reason why there is a need for 3ds2 specific number. One of the reason I want to make sure we have the right answer before we can proceed. thanks