#erast_api
1 messages · Page 1 of 1 (latest)
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1384435050740977785
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi! Can I check if you are asking how do you always get customers to go through 3DS authentication?
We want always to have strongly 3DS authentication with OTP checkout, but right now we can see that for some clients payment going to requires_capture status immediately after payment created.
Using challenge doesn't guarantee 3DS authentication. Our API docs mention: Stripe can’t guarantee your preference because the issuer determines the ultimate authentication flow. (https://docs.stripe.com/api/payment_intents/create#create_payment_intent-payment_method_options-card-request_three_d_secure)
Can we pass payment with guaranteed 3DS authentication or decline if is not supported?
or how else can we solve our problem? Perhaps there are some setting in Personal account page or another ways.
Looking into this, just a moment.
Hey! Taking over for my colleague. Let me catch up.
I think you can use Radar for this