#abd1hass
onyx cypress
stiff kettle
Hello
stiff kettle
Thanks, taking a look
bold cobalt
here is the strange thing, same customer tried again just now but failed. pi_3O04YTJW5eVJnn2s1Opkha7k. He says that after he approves on his Natwest bank account, if his not quick enough to return back to the website and click "I have approved in the App" payment fails and his not redirected too
He is refferring to this bit that Stripe shows
stiff kettle
That isn't something we show, that is the issuer's 3DS frame
So for the first instance you shared I can see that 3DS was successfully completed. You are saying that they are not redirected after completion?
What happens exactly?
bold cobalt
ok putting this to aside, i think after the issuer deals with the authentication, somehow stripe isnt redirecting back to the redirect_url or if something went wrong, its not displaying the error. i am handling the error correct since i have tested with all test cards
bold cobalt
What happens exactly?
they get sent back to the original checkout page the stripe confirmPayment starts from
and by then, my react state is lost.
i have placed debug logs, but nothing gets fired
stiff kettle
Hmm do you have a screen capture by chance that shows the whole flow?
And are there any Console errors?
bold cobalt
since it happens randomly, i cant reproduce the error. this user luckily is a friend of mine. he is using his phone
stiff kettle
Does it only happen on mobile web?
bold cobalt
i can make a screencast video to show you the flow. Its quite simple, users get taken to a checkout page. Fill in Stripe Elements. Hit the payment button. A quick fetch happens (without await) and then immediately i call await stripe.confirmSetup
yes users who complain about this error are all mobile
stiff kettle
Hmm okay that's interesting. Have you/they hooked up a mobile device to a laptop and checked logs?
bold cobalt
No. They r not a developer. I saw the request from server. It literally goes to the checkout page and not the thank-you page
For others it goes to thank you page. Do you think that any other fetch request if not unresolved or something could effect the redirect ?
stiff kettle
Really I can't say. We would need further information to be able to help. We need to see if there are any logs, we need to know if there is a reliable way to reproduce the issue, is it affecting only certain types of mobile devices, etc.
bold cobalt
Ok what's the best way to go about it
stiff kettle
I'd recommend doing the above... if you can't reproduce this yourself in test mode then you'll need to work with one of your customers to capture a video with logs and provide that and the device information to us as well as the PaymentIntent that you tested with. The best thing to do at that point is to write a detailed report with this information to https://support.stripe.com/contact/login and then we can dive into it.