#oss - Checkout email

1 messages · Page 1 of 1 (latest)

runic rampart
#

Hi there! Are you specifying a Customer id when creating the Checkout Session in order to fill the email form? Or is that form being filled in manually by the customer?

cyan turtle
#

Everything is being filled in manually except the email

#

I use the email to authenicate if someone has paid

#

I was having issues with the email being case sensitive so i passed in the email to the form so the client can't change it after signing in

runic rampart
#

Are you using Stripe Checkout? Or are you using a custom payment page?

cyan turtle
#

strip checkout

#

here's what it looks like

#

sometimes however, it'll be a different email... sometimes a different clients email. Not sure why someone elses email is getting stored and showing up on my machine?

runic rampart
#

What is the URL on the page from that screenshot?

#

So it looks like your integration is creating a Checkout Session and passing in a Customer id (see here: https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-customer)

If the Customer already has a valid email set, the email will be prefilled and not editable in Checkout. If the Customer does not have a valid email, Checkout will set the email entered during the session on the Customer.

Do you know where your integration is getting the Customer ids from? Is it from earlier in the payment flow? An internal database? API request to Stripe? Etc.

cyan turtle
#

The way my application is setup, is it signs in throgh google.

Takes the session and takes out the email and sets the email as a global veriable

In the Strip api, i pass in that same email as :

customer_email= email,

runic rampart
#

Is the email being retrieved from a session cookie? Or is it being passed directly via the POST body when /create-checkout-session is activated?

cyan turtle
#

being passed directly via the POST body when /create-checkout-session is activated

#

I mean both... ?

#

The email is being retried from the google session, I hold it in my code until the /create checkout session is created

#

retrieved

#

is there any other way to do it?

runic rampart
#

I would start by putting print() statements at every step of the process so you can nail down exactly where the mixup is happening. Have you been able to reproduce this behavior?

cyan turtle
#

I mean it's just not making sense to why this is happening... Like for example if you hit my sign in button right now, you'll see someone elses email in the on your computer

#

That's how i found out about the issue

#

Its not a local host issue

runic rampart
#

Ah, yeah. I'm unsure of where to begin with that one, to be honest. Are you using a Google-hosted sign in form? Or do you have your own sign in form/portal?

cyan turtle
#

google sign in

runic rampart
#

I see. I wish I could be more helpful here, but I'm not very familiar with how integrating that product looks and it sounds like the wrong emails are coming from upstream (beyond your integration and Stripe's side of things)