#wobedi
1 messages · Page 1 of 1 (latest)
Hi! Thanks a ton for the quick reply
In the example of our app, this is what happens:
exactly
I actually see a feature request internally already for this. I'll tack your note on here to let the team know there is more interest. Hopefully it will get prioritized in the future!
Thanks for the feedback!
Some further context on how we use this, if it helps:
- Let's say our app's URL is example.com/app
- User clicks on checkout button within our app (on example.com/app)
- We create a checkout session and pass
cancel_url: example.com/app?abandoned-checkout=trueas a Stripe API parameter
-
IF user now clicks on UI button within Stripe Checkout, they will get forwarded back to
example.com/app?abandoned-checkout=true -
BUT, IF user uses their browser's back button (much more common) they will instead get forwarded back to
example.com/app--> We won't know that they just abandonned checkout
Yep makes total sense
Basically we want to display special UI for users who just abandonned checkout, and if the user uses their back button then we currently can't do that