xpaghkman-customer-email

[neat tangle]

I can explain a bit more actually. We are currently using stripe's checkout by using customer session, so we are creating customers, and we don't want checkout to create a new customer always.

And in stripe checkout user is providing email address, and we are able to update our own database through stripe.

So, we will migrate to Stripe Payment Elements which will be Express Checkout Element I think. And My question is if user uses lets say Link, or Apple pay or google pay, will stripe still retrieve email from those providers and update the customer object?

I hope the questions is clear @thin falcon, let me know if you need more details.

[thin falcon]

No, the customer object won't be updated with emails from those providers

[neat tangle]

Are you sure?

I have some examples currently from Stripe Checkout who used Apple pay, and their customer object got updated with the email

Is it okay to provide a customer id here for you to be able to check it?

[thin falcon]

Yes, please!

[neat tangle]

Customer Id: cus_PaaYgEtQLIYeGA

[thin falcon]

Okay, I see the customer was updated when the payment was confirmed and you're using the Pricing Table

Give me a few minutes please

[neat tangle]

Yes, correct. I am providing customer session secret to pricing table, but customer object still had no email in that time

[thin falcon]

Gotcha, okay

[neat tangle]

So, this is our current flow, and another question is also when we move to stripe payment elements and use it in our own website, is it gonna be the same behaviour ?

[thin falcon]

I'm able to reproduce this on my end but it seems specific to subscription payments only: the customer email is updated with details from the wallet only if the Checkout Session was for a subscription payment

[neat tangle]

So which is the type of checkout session that we only need actually. So do you think is it okay to rely on this behaviour? and so we can keep using the email updates from stripes side.

[scarlet grotto]

Hi 👋

My colleague needs to go so I'm taking over. This approach will set the email from the Customer's Apple Pay account. Otherwise they will be required to fill out the email field in the Checkout UI.

[neat tangle]

So, this would be also same behaviour across express checkout options like "Link", Google pay etc right ?

As I understand, stripe will always require email to complete a payment, would this statement fit here ?

[scarlet grotto]

With the Pricing Table you are creating Subscriptions. Subscriptions require Customer objects to be created. When we create Customers automatically, we collect email addresses to identify them.

stripe will always require email to complete a payment
This isn't literally true since you can process payments without a Checkout Session or Customer. But in your specific case it will be true

[neat tangle]

One thing here is I am creating the customer object and providing the customer session client secret to pricing table, so stripe does not automatically create customers in my case.

[neat tangle]

Yes my question is in terms of checkout sessions for subscriptions.

@scarlet grotto Another important questions was this already asked above but putting here again.
Another question is also when we move to stripe payment elements and use it in our own website, is it gonna be the same behaviour ?

So we are planning to stop stripe checkout and pricing table, and would like to integrate the stripe elements.

[scarlet grotto]

Sorry, with all the quote highlighting it's making your questions really hard to read.

[neat tangle]

the original message.

[scarlet grotto]

If you integrate with the Stripe Payment Element you will need to add a field to collect your customer's email address yourself.