#hellotika
1 messages · Page 1 of 1 (latest)
Hi, is confirmCardPayment the prefer approach in the front end to handle 3ds when next action said so? Or setting the return url on create pi then using the next action (which is a redirect url) that front end then open in an iframe?
Hi, is confirmCardPayment the prefer approach in the front end to handle 3ds when next action said so? Or setting the return url on create pi then using the next action (which is a redirect url) that front end then open in an iframe? we are using dynamic radar (subscribed to that) if that makes a difference.
thanks @hybrid osprey
Either method should work ehre
Yep yep, just making sure we kept things all in one place
is there a prefer approach over the other?
Nope, you can use whichever makes more sense for your site
and does the front end stack make a difference? the confirmCardPayment is under stripe.js, so essentially any FE stack should be able to leverage it.
what are some flow/use case that you know of that would use confirmCardPayment over the other approach?
we are currently listening to ready to capture webhook to finalize the payment after 2fa
Honestly as far as I know it is mostly a UI preference. confirmCardPayment means that Stripe's 3DS modal appears over your site, a full page redirect of course doesn't use your site's UI at all, and displaying the site in an iframe would let the user stay on your page with a UI that you have a bit more control over