#huncsuga_3ds-auth-flow
ivory frostBOT
👋 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/1423067369592586442
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- huncsuga_code, 11 hours ago, 23 messages
cold flower
Hi there!
A few things, which I think will steer the discussion forward:
Sorry, I was just refreshing my memory on this integration
- 3DS comes into play when Stripe talks to the user's financial institution through the networks, typically, or if we know 3DS is required by local regulations, but in either case this is generally at confirmation time.
- Creating/confirming a SetupIntent and then using the Payment Method to create/confirm a PaymentIntent off-session after you've determined product availability is conceptually quite similar to the two-step confirmation
- I'm not sure that I see a benefit to using manual capture here for the purposes you've described
ivory frostBOT
ancient adder
What I’m trying to achieve is this: after the PaymentIntent is created on the backend, the next step is confirmPayment. The problem is that if the user has to authenticate with their bank during confirmPayment (3DS), that process can take some time, and meanwhile the product they’re trying to buy might go out of stock. That’s the scenario I need to handle.
My idea was to trigger the 3DS validation before actually running confirmPayment. If that succeeds, then I would perform another stock check, and only if everything is still available would I proceed to actually charge the customer.
vocal crystal
Hello 👋
I'm taking over as my colleague had to go.
As was mentioned earlier, if you need to perform any required 3DS before you create the Payment Intent, then we recommend you first save the Payment Method use a Setup Intent like we document here: https://docs.stripe.com/payments/save-and-reuse
There are multiple tabs to this doc so make sure you look at the one that matches your integration.
Specifically you will want to use a Setup Intent and 3DS should be triggered during the confirmSetup step here: https://docs.stripe.com/payments/save-and-reuse?payment-ui=elements#submit-payment-details
ancient adder
Got it, thank you. I followed that doc when building my integration - https://docs.stripe.com/payments/build-a-two-step-confirmation?lang=php&client=html . My question is: in this case, can I just replace the PaymentIntent with a SetupIntent?
vocal crystal
I think you can just drop in the Setup Intent instead of the Payment Intent as long as you modify the Submit step here to use confirmSetup instead of confirmPayment.
To be clear, this means your flow will only save the Payment Method configured for off-session use. You will need to handle creating/confirming the Payment Intent in a separate step.
ancient adder
Thank you for your quick and clear answers.
vocal crystal
Sure thing! It's why we're here 🙂