#demmerson - Confirm Payment Intent
fickle sapphire
The return URL is related to handling next actions: https://stripe.com/docs/payments/payment-intents/verifying-status#next-actions
for payment types that require them.
quasi fable
Right, how can I force a redirect in development when using stripe.confirmCardPayment to confirm a card payment? I've tried several of the cards requiring 3DS auth https://stripe.com/docs/testing, but do not understand how to force a redirect in development (to correctly handle if/when that case occurs in production).
fickle sapphire
It is possible to attempt it but it's not 100% guaranteed https://stripe.com/docs/api/payment_intents/create?lang=ruby#create_payment_intent-payment_method_options-card-request_three_d_secure
We do recommend (as the doc states) that you rely on Stripe's built in SCA engine to take care of prompting your users for 3DS authentication.
quasi fable
Hmm, okay. I've read through all that a couple times and this still is not obvious to me. To my understanding, I am using Stripe's SCA engine with stripe.js, by first creating the PaymentIntent on my server, then on the frontend calling stripe.confirmCardPayment with that PaymentIntent's client secret. With my current dev setup, for cards requiring additional auth, Stripe is popping up a modal - in dev environment, the modal has options to complete or fail. With my current setup, I receive the response when the promise from stripe.confirmCardPayment resolves. However, my understanding is there are cases where the customer will be redirected to their bank, and then back to my app. How do I force this workflow in development? Or, do I have a misunderstanding here?
noble palm
I don't think there will be a full redirect for confirmCardPayment
I think that is mostly for the flow with the PaymentElement/confirmPayment
I believe you can choose to do a full 3DS redirect flow but that is when you ask for it
Still checking in to this to confirm but it is looking like these are slightly different flows