#zooooooooo
nocturne wadi
There's no payment in setup mode, so tax is moot
That only applies in payment scenarios
And is unrelated to on or off session
What are you trying to do?
rotund wasp
trying to collect details for a usage-based billing subscription (but via manually generated invoices via the api, since we have a weird billing model that doesn't jive with stripe's current support for usage-based billing)
related is #dev-help message
nocturne wadi
Gotcha -- so with checkout and setup mode, what are you expecting to happen?
rotund wasp
mm I'm expecting to collect payment information and hopefully address info (for auto tax calculation) so that I can later generate invoices according to their usage
all in a "checkout session" so I can reduce my UI building and avoid Stripe Elements
nocturne wadi
Gotcha, i think you might be looking for billing_address_collection=required then
which you can set on setup mode too
this would get a full billing address for the customer/PM
rotund wasp
cool, ok; that would allow me to collect the amount of address info to then pipe into the "auto tax" at invoice creation time then?
that's looking improved, ok
nocturne wadi
Yes, unless you provide a higher-priority address later with the subscription/customer
The PM billing address is the third highest
rotund wasp
ok
so collecting the billing info in the setup intent should hopefully avoid customer_tax_location_invalid as long as the higher priority values don't take precedence w/ a less specific location? https://stripe.com/docs/tax/customer-locations#handling-errors
nocturne wadi
Yes, i think that's right.
As the docs say, if you provide one of the customer addresses that is incomplete, you see:
Using an address that isn’t precise enough to calculate tax returns a status of requires_location_inputs.
rotund wasp
thx for the help! last question: there's no way to alter the submit button text, to something like "upgrade plan" right?
probably a job for Stripe Elements?
nocturne wadi
Which button text?
frail deltaBOT
old sorrel
We have a couple pre-defined options for what that button can say but unfortunately none of them fit this situation https://stripe.com/docs/api/checkout/sessions/create?lang=curl#create_checkout_session-submit_type
rotund wasp
yep, a "manual subscription" type would be helpful here ig 😅
which is kinda amorphous, so it makes sense why that doesn't currently exist
old sorrel
Gotcha, I'll put in feedback for that. I have heard of a few use cases for that kind of subscription just this week so we definitely have a bunch of users that do some pattern like that