andrew_api

[long crag]

👋 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/1331322976540295169

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[languid seal]

Hello! There is no payment_method_options on stripe.confirmCardSetup. You would need to set that on the Setup Intent itself when you create it server-side.

See here: https://docs.stripe.com/api/setup_intents/create#create_setup_intent-payment_method_options-card-request_three_d_secure

[open verge]

Hi! Here it says we can manually request 3DS when either creating or confirming a SetupIntent: https://docs.stripe.com/payments/3d-secure/authentication-flow?api-integration=setup-intents-api#manual-three-ds.

[languid seal]

That means when you confirm server-side, not when you confirm using Stripe.js client-side.

Note that code snippet is using your secret key, and that request would need to be made from your server.

[open verge]

Ahhh ok. We are currently creating the SetupIntent server-side and then confirming client-side. Is there no option to manually request 3DS auth from client-side? It must be done server-side?

[languid seal]

It must be done server-side.

If you could do it client-side the client could alter the code and just turn it off.

[open verge]

That makes sense

Thank you!

[languid seal]

Happy to help!