#Decybel
1 messages · Page 1 of 1 (latest)
Hi, I'm getting a teammate who is more experienced with this. Thank you for your patience.
No problem, I'll wait.
Hello! The Payment Sheet is designed to collect payment information only, not arbitrary information like an email address. Some payment methods require an email address as part of the payment process, but that's the only time the Payment Sheet will collect it. If you need to collect an email address every time you need to do so outside of the Payment Sheet.
I understand. Why do they have a field to enter an email for some payment methods?
Because some methods of payment require an email as part of the payment flow.
It is not possible to force such a flow for all, through some configuration?
I don't believe it is supported to force it right now, checking something real quick
How does stripe send the payment confirmation to the email if there is no way to enter it?
yep don't see a way to force email collection on PaymentSheet or its Configuration object
good feedback to send to the stripe-ios development team at https://github.com/stripe/stripe-ios by creating an issue as a feature request (I didn't see one there)
How does stripe send the payment confirmation to the email if there is no way to enter it?
no email is sent in that case
you should collect email in your UI and pass it on the PaymentIntent's receipt_email field
I have an identical problem on the android side
I don't need to use PaymentSheet, if there is any other ready solution in your library that will solve my problem then I can use it
depends on what your goal is
if you only want to support cards, then you probably shouldn't use PaymentSheet (though I personally would)
the benefit of PaymentSheet is that you get n different payment methods supported all with the same lines of code
otherwise, if you don't use PaymentSheet, then you need to integrate each PaymentMethod separately by writing lots of custom code
I mainly care about cards, unfortunately in this method of payment there is no field to enter the email
yeah so in that case, use CardFormView from the iOS/Android SDKs and mount your own email input field
Ok, thank you. This is some temporary solution
If I report the problem on github, in what period of time can I expect the problem to be solved?
I can't say, it all depends on how it gets prioritized based on the roadmap of the SDK teams. They are busy with adding lots of other features (and making fixes)
Thanks for your help