#knuppi.
brittle swanBOT
Hello! We'll be with you shortly. 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.
- knuppi., 3 hours ago, 9 messages
- knuppi., 7 hours ago, 97 messages
- knuppi-payouts, 3 days ago, 60 messages
- knuppi-subscription-events, 5 days ago, 46 messages
thick chasm
As far as I know, tax rates only work with our subscriptions and invoices APIs
Can double check
unique rampart
We have clients all over Europe, thus the TaxRate for e.g. a Product may be different
thick chasm
For payment intents, I think the only option may be tax calculations https://stripe.com/docs/api/tax/calculations/object
Though tax rates are a flat rate correct?
unique rampart
Yes, "food & beverage" has e.g. 12% tax rate while "goods and services" has 21%
So depending of what a) our client (the connected account) resides, and b) what they're planning to sell, there's different flat tax rates attached to each Product
all direct payments are created through PaymentIntents, while using stripe_account
thick chasm
So the tax calculations API (or automatic tax on our other surfaces such as Checkout or Invoices) would be the only way to automatically calculate tax based on location
I have not gotten to fully confirm but I think that raw payment intents do not support the Tax Rates API, I think at that point you would have to determine the correct rate, multiply your original amount by 1.12 and such, and then create your intent at that amount
unique rampart
Hmm, OK. I mean, the company would pay taxes in the country they're operational in, not necessarily in the country the buyer exists in
thick chasm
Stripe tax would calculate it based on the address that they input. Our forms have autocomplete based on location, but you can input a location that you are not currently in
Which I think would also be what you want to do if you calculated it manually, take the address info they input and find the right rate based on that
unique rampart
OK, I see. It won't work for us though, as we're using your Google Pay/Apple iPay solution - we never ask for the end-user's address
thick chasm
I thought there was a way to get postal code from those, can check in to it
unique rampart
Another question before we develop our own solution; do you have a "down payment" feature?
Use case; we have a Connect Account which charges for very high-ticket items such as yacht/boat rentals which costs +$1.000 per day.
Is there way where we can charge only e.g. 20% of the $1.000 price and mark that payment as a "down payment"/"reservation fee"?
thick chasm
Unfortunately we don't have anything built in for that. So you would have to manually calculate that percentage and make a one-off payment for that amount upfront
unique rampart
OK, thank you very much for your answers 🙂