#benk
1 messages · Page 1 of 1 (latest)
Are you able to share more details about the error(s)? Is there an example payment that experienced this that I can look at? Anywhere to reproduce?
What we would like to know if there is a server version of the 3DSv2 flow where our payment page would get an update about each steps of the flow?
You can't initiate/complete a 3DS flow server-side no
even if the payment page is hosted by us? eg: we are not using the Stripe hosted payment page
The 3DS flow needs to be initiated and completed client-side, otherwise how are your customers meant to authenticate the payment with their bank UI?
I'm checking our team to see if I can get the transaction details but regarding the error in the browser we don't know much about it since the customer has closed the browser before we were able to contact the person
the authentication does happen client side, but what I'm asking is whether Stripe provide a notification about each of the step back to the integrating payment page
Could it just be that they're failing the 3DS authentication? What makes you think this is an integration issue as opposed to just a failing payment?
some PSPs have the 3DSv2 flow where each stage yields a "response/notification" to the integrating payment page
Well you'd subscribe to payment_intent.payment_failure/.succeeded events and the status field would reflect the steps of the auth flow (i.e. requires_action -> requires_payment_method (fail) or succeeded)
I'm getting a transaction identifier from our support team for you to look into it. One of our developer stated that based on the customer feedback it sounds like the last bit of the flow where the JS is making the final "complete payment" call (that carries the CRes) is not getting a reply from Stripe.Liek there was a network issue and the connection being dropped
in such case what happens with the incomplete 3DS authenticated payment? Does Stripe provide a notification after some sort of "3DS completion timeout"?
3DS authentications don't timeout. It's just be stuck in a requires_action state
It'd only transition to requires_payment_method if there was an explicit failure
so in case the CRes message was never received by Stripe (eg: network issue) the transaction would just stay in the "open" state? The problem is that our payment page in such case doesn't receive a response from Stripe
It no auth attempt was made, then it'd still be in requires_action yes
It'd be a lot easier for me if there was an example payment to look at
I'm getting the details, give me a few minutes