#testanib - texts & 3DS
distant urchin
Hi! The Stripe 3DS payment flow requires the client to interact with a 3DS modal.
Can you share an ID for a failed payment Intent?
And how are you collecting payment information currently?
Stripe Elements and Stripe Checkout take care of this pretty well as part of the automated process.
livid bane
Hi @distant urchin , here's the faild payment id: pi_3KYx81CFi9AUHYSb0IolfJKd
Are you able to join VC? It may be easier if we discuss over a call
please ignore the above transaction id, that's due to a different error
distant urchin
I cannot join a call. This will need to do or you can request a call from Stripe Support. Let me know when you have a good example ID.
livid bane
pi_3KYdKXCFi9AUHYSb0dqZjaTK
let's try this one
pi_3KYcAnCFi9AUHYSb0pONYULw
this one as well
hazy iron
What exactly are you looking for help with in terms of your integration?
What are you trying to do?
If you want to always request 3DS, then you can use request_three_d_secure=any
https://stripe.com/docs/payments/3d-secure#manual-three-ds
Or you can use your Radar rules
sharp whale
to start we just wanted to clarify that texts requiring a user to answer yes or no if they authorized a charge, would still follow this 3ds implementation. As oppose to typical 3ds where a code is sent to the buyer and they have to verify it on the website
hazy iron
The actually mechanism of 3ds verification is entirely up to the issuer of the cards, Stripe has no control over it
sharp whale
so would it be possible to handle our rare and random cases of 3ds so that the payment intent does not return 500 or do we need to request 3ds for every payment from now on?
if i am understanding the docs correctly, we would need to check the three_d_secure property of the card for each charge to tell if 3ds has been requested?
hazy iron