#Euclid
1 messages ยท Page 1 of 1 (latest)
Hello ๐
Can you share a screenshot of the field you're referring to?
sure
just so that I'm on the same page
You can share the screenshot here as long as it doesn't have any private/sensitive information
It will have my email address from test mode ?
You can redact it by editing the image if you want
Ah gotcha. So you want to disable email address collection on checkout?
Yes Correct
Thanks for you help with this ๐
I have tried passing customer_email: ''
without success
No worries! I don't think we currently support disabling email collection on Checkout unfortunately.
It's not related to firebase extension exactly but thats just how checkout works.
OK but could it be modified
to display something else... as im using the extension with the checkout.session.create attributes
Hello, hanzo had to step out so I can help out here going forward.
Unfortunately there aren't parameters to pass in to checkout.session.create right now that will hide that input. Putting in a blank string will make sure you never actually collect an email addres but at the moment there is not a way to hide the text box itself.
OK but as the extension is for authorised users only its displaying their email.... is it possible to pass another customer_email to checkout.session.create ?
Yes, you can pass whatever email you want to that parameter and the Checkout page will display it to the user
this works with the firestore extension also ?
at the same level as mode: 'payment',
Yes it should be
Interesting, when you pass in that empty string, the Checkout Session still shows some email?
Yes because its a signed in user
Gotcha. I will ping a colleague who is more familiar with this and will get back to you
but im calling this on the frontend so the email is not correct
As im using dynamic pricing instead of price_id
Quick question: is this just a UI preference then that their email shouldn't show up? I assume the user already knows that you have their email if it is associated with a customer in your system already
Gotcha. Actually in just testing this endpoint itself, I don't think that you can have these payments associated with the existing customer object while also not displaying that email
I can put in a feature request but can't promise if/when it might get added
And I cant pass another in the .create to display instead..... ?
Thanks for the feature request also....
If you pass both customer and customer_email the endpoint actually errors out. So I think the firebase extension is preventing that from happening by just not passing in the value you pass for customer_email.
it like this is passed a level above...
Not quite sure I understand the use case. The email showing will always be the buyer right? The person who created the product shouldn't have their email showing
OK Thanks @weak storm
Of course! Putting in the feature request now