#pingpong2_code
gusty cairnBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1288157741860257813
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- pingpong2_code, 5 days ago, 11 messages
- pingpong2_api, 6 days ago, 11 messages
sonic sparrowBOT
sick pawn
Hi there 👋 you disable the inclusion of the email field by settings fields.billingDetails.email to never when creating the Payment Element:
https://docs.stripe.com/js/elements_object/create_payment_element#payment_element_create-options-fields-billingDetails-email
I've not heard of a flow that removes the need for email address collection completely when accepting ACH Direct Debit payments, and anticipate you will need to include the email address that you collected from your form when confirming the intent via payment_method_data.billing_details:
https://docs.stripe.com/js/payment_intents/confirm_payment#confirm_payment_intent-options-confirmParams-payment_method_data-billing_details
If you're expecting to be able to skip email address collection completely due to being in a beta of some sort, I would suggest reaching out to the support contact you were provided as part of that beta if you encounter errors.
granite gulch
ok so try something like
<PaymentElement
options={{
terms: { card: "never" },
defaultValues: {
billingDetails: {
email: "never",
address: {
country: "US",
},
},
},
?
sick pawn
No, you put it in defaultValues.billingDetails, but it needs to go into fields.billingDetails. The defaultValues objects is used for populating the payment element with default values, the fields object controls what fields are hidden.