morieeeenyo_api

[clever moat]

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

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

[twin thicket]

We cannot offer non-English support here. If you need help in Japanese you'll need to reach out to support: https://support.stripe.com/contact/email?topic=api_integration

But the short answer is that you cannot facilitate 3DS/auth via backend APIs. You need to handle those challenge flows in your frontend, either with Stripe.js functions or manually using the redirect URL returned

[steep mauve]

thank you @twin thicket .
so, how can I handle 3DS/auth in my frontend? I can get redirect url for 3DS/auth challenge only in frontend?

I guess I can get redirect url → users redirect url in frontend when purchase ... is this correct?

[twin thicket]

You'd call confirmPayment via Stripe.js ideally: https://docs.corp.stripe.com/js/payment_intents/confirm_payment

So return the pi_abc_secret_xyz to your frontend and call that function and it'll handle it

[steep mauve]

Is it sufficient that I handle only one Payment Intent Id for multiple item purchase?

[twin thicket]

Generall people would handle one payment per 'order' yes

[steep mauve]

now I handle multiple payment for each purchased items in one order, this is not general approach, is it?

[twin thicket]

Not really, no. Sounds like you're describing line items which intents don't support