#slingdinger_docs
1 messages ยท Page 1 of 1 (latest)
๐ 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/1371877174369587270
๐ 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.
- slingdinger_best-practices, 20 hours ago, 5 messages
Hi! Stripe doesn't pull address information from customers' payment methods for calculating taxes, it would have to be collected along with the Payment Method in order forthe Payment Method to have an address for that purpose.
Doesn't this documentation say otherwise? https://docs.stripe.com/tax/customer-locations#address-hierarchy
No? That indicates the order in which we will try to find an address - and therefore address data source precedence - but doesn't say anything about pulling address details from outside of Stripe.
All of those lines end with "if present": if your application has caused that information to be collected from the customer, and sent it in the API call to create or update the relevant object type - i.e., made it present - it will be available there for that order of precedence.
I'm not talking about pulling data from outside of stripe. I'm trying to understand why the API docs say customer address is required for collecting taxes if there alternative ways of doing so via the hierarchy listed above. I'm trying to understand if there are use cases where having the address on the customer is "better" than relying on the address being collected on the customer's payment method.
Also thank you for your help.
In our payment flow, it would be a better UX for the customer to only grab the card's zipcode along with the rest of the payment method information, rather than a separate step to collect it for the customer themselves
You're welcome!
One challenge here is: what is the right tax jurisdiction? If I use my Singapore VISA with a billing address including a Singapore Postcode, to order a product to an address in British Columbia, Canada, which tax rate is correct?
Can you tell me? I'm not a tax expert.
That's why i want to use the stripe tax product
Or maybe the answer is, "it depends"
The answer is nearly always "it depends". ๐
My question is, is it "good enough" to use the payment method address. Or is that something I need to consult a tax subject matter expert on, and not something stripe can answer
But in this case, BC would expect the taxes be submitted for product purchased & delivered in BC.
Ya, this is more of an accounting/legal/compliance question, rather than a technical one.
Ok. Got it. Ultimately stripe gives flexibility to collect the information in a variety of ways, but we need to implement based on our specific (legal/compliance) use cases. Thank you very much for your help.
That is a wonderful description, yes. ๐
Of course - we're nearly always here, and defintely always happy to help!