#boomer_api

1 messages ยท Page 1 of 1 (latest)

trail rivetBOT
#

๐Ÿ‘‹ 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/1257352895679168596

๐Ÿ“ Have more to share? Add details, code, screenshots, videos, etc. below.

vital hollow
#

Hello

winged pivot
#

Hello!

vital hollow
#

The way to do this would be to leverage metadata

#

Otherwise, yes, you would need multiple PaymentIntents as you can only set one shipping.address

winged pivot
#

Yeah, I think that's the only way.

#

Because there's no way that I have found to impact the sales tax nexus thresholds. It happens automatically.

vital hollow
#

I'm not sure what you are referring to with the "sales tax nexus thresholds".... I assume that is related to a third party integration?

winged pivot
#

If you use Stripe's tax API, they automatically monitor your tax thresholds in every country / state.

#

So for example, in Missouri US, once you hit $100,000 USD in transactions you automatically meet that state's threshold for capturing and remitting sales tax.

#

In Michigan US, once you have had 200 transactions you meet that state's threshold, etc...

vital hollow
#

Ah yeah, with the Tax Calculation API it is basically assumed that there is a one-to-one relationship between PaymentIntent and product (thus shipping address)

winged pivot
#

Yeah, this will be frustrating to code for ๐Ÿ™‚

#

For example, a customer may have 1 invoice to pay that ships to 1 state

1 invoice that ships products to 2 states

10 invoices that ship products to 10 states

#

Right now, all of our customers are tax-exempt, and we haven't his any thresholds, so we haven't had to collect anything. But we've just onboarded a few customers that are not exempt, and will need to use the calculatiojn API on those.

#

So if one of these taxable customers has a situation like the above, the code will have to drastically change :/

vital hollow
#

Yeah unfortunately it really isn't designed to be split up like that

winged pivot
#

Yeah

#

It may ultimately make more sense to not use Stripe's threshold monitoring at all and completley offload this to TaxJar or something.

vital hollow
#

With this specific setup that may indeed be a better choice

winged pivot
#

You're very responsive, I appreciate it. Are you with Stripe or just active here?

vital hollow
#

Yes I work at Stripe -- my team staffs this channel 24/5.

winged pivot
#

That's awesome! Well it is much appreciated. I love Stripe, I've used your platform since v1 when you guys were the first to tokenize cc numbers.

vital hollow
#

โค๏ธ

winged pivot
#

๐Ÿ™‚

vital hollow
#

Feel free to pop in here anytime that we can help with something!

winged pivot
#

Thanks bismarck. Have a great day!