#katsching_code
terse heronBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1247547651545759794
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
azure moatBOT
sullen delta
Hi there 👋 the best way to always get details, since the Payment Element only collects details that have a dramatic impact on authorization rates, is to set our fields to never and add your own fields for collecting those details.
When you do, you'll want to make sure you pass the values you collect to us in your confirmation request, via confirmParams.payment_method_data.billing_details:
https://docs.stripe.com/js/payment_intents/confirm_payment#confirm_payment_intent-options-confirmParams-payment_method_data-billing_details
silver niche
Hm, but it will be a bit hard to integrate it with the embedded stripe layout. Is there a reason the checkout element collects the cardholder name, but there's no way to customize it on paymentElement? I want it to basically look like this:
sullen delta
Yup, because Checkout Sessions also optimize for our other features, like sending email receipts. Payment Element can be used for those other features, but it's meant to be more customizable so you may have to do some extra plubming to get that all set up, the tradeoff is you have more control over how things look/flow.
silver niche
Okay. If I collect the data myself, do I always have to provide the email/cardholder name in billingDetails to Stripe? Even if e.g. credit card payments don't require these?
sullen delta
I would go ahead and provide it. It'll make the integration smoother if you ever plan to expand the type of Payment Methods you support, instead of requiring you write bespoke code for each type of payment method.
silver niche
Alright, thanks a lot for the help!