#xmy_stripe-tax

1 messages · Page 1 of 1 (latest)

slim emberBOT
#

👋 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/1358829446433476649

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

edgy tulip
#

Hi 👋 are you planning on implementing Stripe Tax, or are you planning to create and manage Tax Rates yourself?

slim emberBOT
wraith sail
#

Hey, what would the difference be between the two in terms of implementation? I think I'm more inclined on Stripe Tax but curious about the alternative path

edgy tulip
#

Stripe Tax is the more automatic version for this, where you capture address details and we automatically determine which taxing jurisdictions are involved as well as the amount of tax to collect.

The alternative is the more manual but more free approach, where you determine the apporiate rate to charge for each taxing jurisdiction yourself and manage those via Tax Rate objects. Then you can either apply those based on the address you collect.

wraith sail
#

But either way I'd need to capture the address of the customer during the checkout process. Correct?

lunar kraken
#

Hi 👋

I'm stepping in as my colleague needs to go. If you want to manually apply Tax Rates, then you would just need to know whatever info you need to manually set the appropriate tax rate.

If you want to use Stripe's automatic tax product, then yes you would need to capture some level of detail for the customer's address to properly assess tax registrations.

wraith sail
#

So for manual process I'd need to have to:

  • Create a tax rate object for each region I want to offer to purchase from
  • Have a region select on checkout and select the right tax rate

For the automatic product I need to:

#

What I am also trying to understand are the implications of only using one tax rate. Wouldn't that require my customer to confirm they are resident of my tax rate region e.g. Germany?

lunar kraken
#

What I am also trying to understand are the implications of only using one tax rate. Wouldn't that require my customer to confirm they are resident of my tax rate region e.g. Germany?

That is up to whatever one tax rate you choose to utilize. Taxes are a complex situation and we are not tax advisors. We can tell you how to build the API part but we cannot offer advice for how to collect the correct amount of tax for your purchases.

wraith sail
#

Ok regarding the automatic solution. Would the implementation approach be correct?

lunar kraken
#

Using the Address Element in your checkout flow is a good way to ensure you collect sufficient location information to correctly compute the tax rate to be applied.

If you want to manage the tax rates yourself, then creating the appropriate Tax Rate objects and applying them would be up to your integration.

wraith sail
#

Would you recommend it doing as I suggested by always updating the customer object or is there another way?

lunar kraken
#

Sorry but that isn't clear to me. What are you suggesting?

wraith sail
#

This part

For the automatic product I need to:

  • Enable the Automatic Tax setting (and verify my documents)
  • Add an Address Element to my checkout that updates the customer country / code whenever I change the value?
lunar kraken
#

That will work but you don't need to manually handle updating the Customer object. That will occur as part of the confirmation processes. I recommend you build this in test mode to simulate some checkout flows to see this in action.

wraith sail
#

Does the Automatic Tax Product of Stripe Require OSS to be registered?

#

What should / do I have to update to pass along the region information so the subscription can be handled by Stripe Tax?

lunar kraken
#

We have a guide specifically for this here

wraith sail
#

This guide suggests updating the customer before initializing the payment. So I think my assumption is correct

lunar kraken
#

This guide does not factor in use of the Address Element.

#

I recommend building these integrations in test mode and simulating the behavior yourself

#

I think you can design an integration flow that suites your needs more easily once you are famliar with how each component behaves

wraith sail
#

Does the Automatic Tax Product of Stripe Require OSS to be registered?
Just would need this clarifications so I can try building

lunar kraken
#

I don't know what you mean by OSS

wraith sail
lunar kraken
#

That is outside my domain of expertise. I recommend you reach out to Stripe Support to better understand what tax registrations are required.