#antogin_testing-frictoinless-auth
turbid finchBOT
👋 Welcome to your new thread!
⏱️ We automatically close idle threads, which makes them read-only. Make sure you stick around to chat in realtime!
🔗 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/1212042007648669756
📝 Have more to share? You can add more detail below, including code, screenshots, videos, etc.
⏲️ 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. Thank you for your patience!
stark cedarBOT
steep haven
Hi 👋 I'm not sure there is a way to specifically force a frictionless 3DS flow in testing, but let me see if I can find anything suggesting otherwise.
stoic linden
Is there a way to disable it in the mean time?
steep haven
I don't believe so, I'm fairly certain that's controlled by the issuers, though I think there is an option to indicate you'd rather not see it. Let me find that parameter for you.
The closest thing I'm finding, is that you can indicate you'd like to have the customer complete a 3DS challenge (as opposed to letting us or the issuer recommend that), and when doing so you can specify your preference for that authentication to be a challenge:
https://docs.stripe.com/api/payment_intents/create#create_payment_intent-payment_method_options-card-request_three_d_secure
Are you using Payment Intents in your integration, or a higher order object?
stoic linden
We are using payment intents let me check real quick
There is no way to test it?
We would like to not disable if it's working fine
Also as we are based in france we can't even test it in production
steep haven
What are you hoping to test exactly? The frictionless flow doesn't really show anything, and to you the end result is the same as if a customer has to complete a challenge-based authentication.
stoic linden
As we implement our own checkout form with very custom flow and messages we want to know if we handle that case correctly
If we display the right info/ message and if we can optimise the UX to promote speed or safety to the user
steep haven
Gotcha (and sorry for the delay). I don't think you need explicit testing for the frictionless specifically there. The outcome of the 3DS flow will be the same for you regardless of whether the customer completed frictionless auth or a challenge auth.