BrianC - Checkout Hide Email | Stripe Developers | Page 1

magic basin Mar 30, 2022, 5:37 PM

#

Hi 👋
How are you creating your Checkout Session?

#

And Follow up, do you know who your customer is at that point and do they exist as a Stripe Customer?

last pawn Mar 30, 2022, 5:39 PM

#

Using SessionCreateOptions and then var service = new SessionService();
Session session = service.Create(stripeOptions, requestOptions);

#

We know our customer and have already validated email address. May or may not be an existing stripe customer.

magic basin Mar 30, 2022, 5:40 PM

#

Okay perfect. You can simply specify the email when creating the Checkout Session. As our docs say here:
https://stripe.com/docs/api/checkout/sessions/create?lang=python#create_checkout_session-customer_email

If provided, this value will be used when the Customer object is created. If not provided, customers will be asked to enter their email address.

last pawn Mar 30, 2022, 5:41 PM

#

But that makes it appear as a read-only field on the checkout.

#

"to have the field read only is confusing our customers"

#

The question was how do we hide the field.

#

I'm aware of how Stripe works

magic basin Mar 30, 2022, 5:44 PM

#

AFAIK there isn't a way to hide the field entirely. It's either required or pre-filled but those are the only options I've ever seen.

last pawn Mar 30, 2022, 5:45 PM

#

Yes, me too. And it's bad UI so we were wondering if anyone on your end knew how to hide it. Some obscure api call? 🙂

magic basin Mar 30, 2022, 5:47 PM

#

Personally I disagree about the UI. Given that Checkout is a redirect to a different page I want to see the email to know I (as a customer) am on the correct page and have confidence this form knows who I am. But that's a personal preference.

I cannot find anything in the API doc that suggests it would actually hide the field, just pre-fill

last pawn Mar 30, 2022, 5:49 PM

#

But it is a read only field. We have done user testing and about 35% of the people click on it and a number of people expressed frustration. This is possibly the most critical page on any site so all hurdles need to be removed. You guys should know better. Plain text display, NOT a disabled field would be the best compromise. Don't you agree?

#

Just a little feedback. After investing so much time implementing your product and following all of the best practices you give us, to not allow at least some customization for this is really disappointing.

#

It's bad UI. Sorry.

magic basin Mar 30, 2022, 5:51 PM

#

I believe that is why we also have several more custom solutions such as the Payment Element.

#

However, the line_items is a very popular feature of Checkout

last pawn Mar 30, 2022, 5:52 PM

#

Right. Which we have implemented in the past but you folks keep pushing the the pre-built and we bit. Sorry that we did.

magic basin Mar 30, 2022, 5:54 PM

#

I'm seeing that we do have this feedback logged in our tickets. I will "bump" the feedback by providing yours as well.

last pawn Mar 30, 2022, 5:55 PM

#

Thanks

magic basin Mar 30, 2022, 5:58 PM

#

Question: What if a user wanted to update their email? How would you think that should be enabled?

#

Bearing in mind we have some users who rely on the Customer object in Stripe to store these details.

last pawn Mar 30, 2022, 5:59 PM

#

This wouldn't be the place for them to update their email - at least in our flow. Plus, what sort of email validataion are you folks doing? We have confimred users and to allow them to just edit it on the checkout form is actually a security flaw.

magic basin Mar 30, 2022, 6:00 PM

#

Plenty of our users utilize the Checkout form to collect Customer data. We need to consider any/all updates.

last pawn Mar 30, 2022, 6:00 PM

#

The customer object has an ID which is the /unique identifier. Email, especially one that can be edited

#

It just needs to be more flexible. We're one of those users too. Over and out.... Thanks

#BrianC - Checkout Hide Email