#greggles-price-taxbehavior
1 messages · Page 1 of 1 (latest)
Moving this here
One example is API ID price_1L5WZ9GxG8m2870UGhkUhSoq
Thanks
Hi, are you seeing an error? Do you have the specific request id? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
I'm not seeing an error. I think it's because the price is a one-time payment that I can't alter the tax behavior in the dashboard
Also, we're about to enable tax collection. How will this affect existing subscriptions moving forward?
greggles-price-taxbehavior
Hey @distant walrus sorry those are pretty vague questions without much details just yet
usually this Discord server is to help developers with questions about their code, not as much about Dashboard flows
So the question would start with how you integrated Stripe exactly
Thanks, where would I get answers to those questions?
like which products and APIs are you using and are you the developer yourself?
I am and we are using both a card element and a paymentintent element integration
what do you mean by "a paymentintent element integration". Like PaymentElement? Which doc are you following exactly?
I don't need help with the integrations, thanks. We're about to flip the switch in the dashboard settings to enable automatic tax calculation. If this is the wrong forum to ask about this, can you direct me to the correct place?
I mean you do need help with the integration based on the way you are wording your question. But to help you understand what flipping this does, I do need to understand how you built your integration in the first place
Like when you flip that default it will suddenly start calculating tax on all subscriptions. Any subscription were tax can't be calculated will be "blocked" and you'll have to remediate them
usually it's for old customers where you never collected a valid address for example
So usually what we've seen is that people start enabling automatic tax collection on a per subscription basis, for example for net new customers, build that entire integration, the recovery flow, etc.
and only after that all works fine they consider flipping the global Dashboard default
@distant walrus does that make sense?
It does, thanks.
Have you added support for automatic tax collection already or is the "switch it on in the Dashboard" your first step?
I've added support for tax collection but we haven't deployed that. What's the minimum required address info that needs to be associated with the subscription customer for the charge not to be blocked? Zip/Postal code and country?
I think it depends on your country
We're in the U.S.
so yeah for US looks like postal code and country mostly
If I were you I think that what I'd do is write a script to run through all my Customers via the https://stripe.com/docs/api/customers/list API and I'd explicitly use the Expand feature https://stripe.com/docs/expand to include the tax property (https://stripe.com/docs/api/customers/object#customer_object-tax) in the response