#Bobby Z-wrong-email
1 messages · Page 1 of 1 (latest)
I'm worried that if I don't handle this well, it'll result in a lot of chargebacks.
Good question. What aspects of this are you currently looking in to? Correcting the customer email and resending the receipt?
Or is this even an email receipt question?
So I've got a checkout flow. Right before the last step, which is redirecting the customer to Stripe checkout, my website currently checks whether or not the user is logged in. If not, they will be redirected to login. However, this results in a higher rate of cart abandonment than I'd like.
If I removed the logged in requirement, then they'd enter in an email in checkout. If that email is wrong, the stripe receipt and the product would be assigned to the wrong email.
It could be another existing customer, an email that doesn't exist, or an email that does exist and is used by someone else, in which case that person could log on and use the product without having paid themselves.
@worn walrus what's the difference with them entering a bad email when they sign up for your service though?
What you can do is show a success page at the end with their current email to confirm they entered the right one and be allowed to change it if needed
Then the usage rights would be assigned to an account with an email they cannot access.
Okay. Sounds like a plausible solution.
But this sounds like I'd have to generate a temporary and unique URL for each instance, to make sure that nobody else can access that specific page.
Anything less complicated?
I don't really grasp what you describe I'm sorry. What would you need a generic and temporary URL?
they come back to your website, you know who they are from a cookie for example, either they are logged into their account with you -> you check the email entered in the session matches what you have on file and alert if no, or they don't -> you show what you have on the session and ask if it's correct and if they want to create an account with you