#dan_api
real frostBOT
đ 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/1326645513822670903
đ 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.
- dan_api, 35 minutes ago, 5 messages
copper wadi
Appologies, previous thread timed-out
real frostBOT
dim kindle
Hello, no worries. Can you tell me more about your connect setup?
And what Stripe surface(s) you are using to charge here? Like Checkout or your own Elements page
copper wadi
Yes, I'm using Express dashboard for the host accounts
I'm calling const session = await stripe.checkout.sessions.create(... on my frontend web-server (using Next.Js)
And I'm passing that to EmbeddedCheckoutProvider and EmbeddedCheckout components
I'm using Destination Charge also
dim kindle
Gotcha. And to double check, you are using Stripe Tax here with Checkout?
Checking in to how to set this up
copper wadi
That's the goal. I really don't want to have to research each location for sales tax amounts.
dim kindle
Still looking. I see that we have a setting that differentiates whether the tax liability is on the platform or the connected account. If that applies to your situation it could be helpful to try in test mode, that definitely could change the location that we calculate tax from. Still seeing if we have something that changes the location of just that
https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-automatic_tax-liability-type
copper wadi
Interesting, reading the docs right now and trying to figure out which field to set on top of automatic_tax.enabled
Like can I pre-populate the tax address for the buyer?
dim kindle
Yes, the typical flow here would be to specify which connected account this is connected to while creating the Checkout Session
copper wadi
Right so in the general case for a random physical product, I would just need to use the billing_address_collection or the shipping_address for the buyer. However here, I don't want to ask the buyer for their address but instead need to pre-populate it with the rental address. I guess I'm trying to figure out if when setting automatic_tax.enabled = True, I can also progrmatically set the billing_address_collection to avoid asking the buyer
I can try it out in test and see what happens
dim kindle
Let me know what you see in your tests. Billing address is supposed to be the customer, and I don't know if shipping will work for the tax codes that you are working with. I will reach out to my colleagues to see if they have a better understanding of what you can do here