Stripe doesn’t want to support this question and blamed it on me first, then Bubble.
What is supposed to happen in Stripe’s Checkout Process when the user wants to go back to my app?
I am redirecting the user to Stripe Checkout where all credit card processing takes place. This Stripe hosted URL has no cancel button. Only a “Pay” button.
If the user wants to bail out, they can hit the back button in a browser.
BUT… my app is going to be BDK wrapped so the user won’t see a back button will they??
In the browser, even though I have set the cancel_URL parameter in the API call to the right thing and this correct URL shows in the logs at Stripe - my browser is getting redirected to my top level domain instead of to the proper cancel_URL
2 questions:
-
Why is stripe not redirecting to my cancel_URL when someone hits the back button in the browser? What could cause this? Seems like a caching problem to me, but maybe it’s something else? I’m at my own domain, not in bubble test.
-
Is it even necessary to look at this problem at all? Will my users not have a back button wrapped in BDK anyway? And if they don’t, how do they abort a Stripe checkout process with no cancel button?