#himel_code
amber forgeBOT
👋 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/1262387175048220672
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
nimble geodeBOT
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.
- himel_code, 2 minutes ago, 11 messages
wild ginkgo
hi there!
fossil cove
Hey!
wild ginkgo
no, that's not possible. what you could do is remove the billing fields completely from the Payment Element, and then use your own disabled inputs that the user cannot change
fossil cove
But this input will still be visible!
wild ginkgo
like I said, you can remove the billing details field if you want. with this: https://docs.stripe.com/js/elements_object/create_payment_element#payment_element_create-options-fields-billingDetails
fossil cove
thanks!
is there any benefit of collecting this even though this information are already collected in application level
wild ginkgo
some payment method require this information. so you could remove the billing details fields from the Payment Element, but you will still need to pass that information when confirming the PaymentIntent.
fossil cove
in customer object they usually have this information already right?
wild ginkgo
depends on your integration. but you'll still need to pass that information explicitely when confirming the PaymentIntent, depending on the paymentmethod used.
I recommend doing some tests in test mode to see how this works.
fossil cove
Okay thanks, soma!
wild ginkgo
happy to help 🙂