#david-thorand_api
proper gullBOT
👋 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. Thank you for your patience!
⏱️ We automatically close idle threads, which makes them read-only. Make sure you stick around to chat in realtime! If this thread is closed and you have another question you'll need to start a new thread.
🔗 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/1214651646286499851
📝 Have more to share? You can add more detail below, including code, screenshots, videos, etc.
gray scrollBOT
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.
- david-thorand_address-element-fields, 5 hours ago, 6 messages
- david-thorand_api, 1 day ago, 14 messages
visual oyster
Hello! No, if you want to collect that information you would collect it with your own form fields alongside the Stripe Elements you're using.
sterile bobcat
Any best practices on sending that data to Stripe then? Does the SDK provide something for this or do I need to handle it myself?
visual oyster
It depends which Stripe products you're using. Can you tell me more about what you're building and what APIs you're using?
sterile bobcat
We're building a SaaS product. For the checkout we're currently using stripe-js and react-stripe-js
visual oyster
Are you using Checkout? Payment Element? Card Element? Something else?
sterile bobcat
AddressElement and PaymentElement
visual oyster
The Address Element can collect the name, but otherwise you would collect this info yourself with your own form fields and pass the data along wherever it's needed.
sterile bobcat
So what does "wherever it's needed" mean? Does Stripe has a specific API to pass this or does our backend have to handle it from scratch?
Also the AddressElement collects the name but does not set it as the cardholder name, does it?
gray scrollBOT
visual oyster
It depends. If you have the Address Element in billing mode it would set the cardholder name.
As for what to do with the VAT, that also depends on what you're using as far as APIs. Are you creating Payment Intents directly? Invoices? Subscriptions?
sterile bobcat
Subscriptions. The VAT needs to be collected when customers opt-in for a paid plan or upgrade to a paid plan from the free plan
visual oyster
You would take the VAT and update the Subscription's Invoice settings with it: https://docs.stripe.com/api/subscriptions/update#update_subscription-invoice_settings-account_tax_ids
You can do that in the same update when you switch plans.
sterile bobcat
The VAT ID needs to be connected with the customer though. But I guess there is no way around implementing it from scratch then.
Why is this standard in the Stripe hosted checkout but not with the React elements? Seems odd to me
mild arrow
👋 catching up here
Our team won't have a ton of context on why certain product decisions were made 🙂 However, I can help raise this as feature request.
If you'd like to flag this yourself then you can use the support form via
https://support.stripe.com/?contact=true
(this way you'd also be in the loop in case we do implement VAT collection via elements)
visual oyster
You can also update the Tax IDs on the Customer if you want: https://docs.stripe.com/api/tax_ids
sterile bobcat
@mild arrow gotcha. Just curious. The Stripe API is mostly super nice to use but there are some things that just don't make sense. To me at least.
In any case, really like the dev support here. As always: Thank you guys!