#Kamon

1 messages · Page 1 of 1 (latest)

cedar basinBOT
vagrant warren
#

Hi there

#

Hmm good question. Give me a moment to look

#

Can you clarify about "can't create transactions unless they are tied to a calculation"?

drowsy dust
#

Correct, that's what I'm using.

If you see here: https://stripe.com/docs/tax/custom#tax-transaction

You need to create a transaction from a calculation and the calculation expires after 48 hours. Our problem is it can potentially be months from the initial calculation before we actually record a transaction.

vagrant warren
#

Ah okay yeah thanks for clarifying. I see what you are saying now.

#

The reason for this is that tax rates can change. So it isn't really reliable to calculate one rate and then use it in the far future...

#

So not sure there is any workaround here really beyond re-calculating when you are going to charge the Customer and then alerting them if the rate is actually different.

drowsy dust
#

Correct, I get that, but when using other tax software situations like this haven't been a problem.

It's a common use-case to give a customer an agreed upon price and calculate the tax rate at the time and wait to charge the customer until goods are being shipped out. When it comes time to collect payment, you record the amount of tax collected, the transaction date and you're good to go.

#

Also, the 48 hours doesn't necessarily align the the 7 day auth/capture window y'all have

vagrant warren
#

Yeah I think that is fair feedback. I haven't seen this come up before yet, our direct Tax API endpoint is relatively new. I'll certainly pass your feedback along internally so that we figure out a better way to handle this going forward.