#milan_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/1417947867187908760
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello, with Stripe.js the typical way to handle that is to pass the intent's client secret to the frontent and then call handleNextAction on it which shows the 3DS modal. This doc is for a decently different flow but it shows how to do it well
https://docs.stripe.com/payments/finalize-payments-on-the-server?platform=web&type=payment#next-actions
Looking at this....
Is there a way to do this without the Stripe JS?
I think all we need is to save a payment method in a certain way and then use that moving forward with the off_session flag, right?
In other words, we'll definitely get user authentication the first time, but we want to go off session from that point forward with the same payment method.
For example, if we use the same PaymentMethodId on a subsequent payment, would that work with off session?
3DS is less likely with off session payments, but it always can happen so we reccommend being able to handle it for off session payments.
For handling this without Stripe.js, I know that in at least some cases we give you a URL and you can either redirect to it or display an iframe with it. I forget if there is a way to force that as opposed to a flow that requires the Stripe SDK. Looking in to that and will get back to you https://docs.stripe.com/payments/3d-secure/authentication-flow#manual-redirect
Yep - we use the NextAction.url today with our existing 3ds implementation
Ah it looks like you should always get the redirect URL if you are confirming your intents like this. It looks like use_stripe_sdk should be reserved for when Stripe.js confirmed the intent itself