--
You received this message because you are subscribed to the Google Groups "Stripe API Discussion" group.
To post to this group, send email to api-d...@lists.stripe.com.
Visit this group at http://groups.google.com/a/lists.stripe.com/group/api-discuss/.
To unsubscribe from this group and stop receiving emails from it, send an email to api-discuss...@lists.stripe.com.
I've used Avalara's (http://www.avalara.com/) API for handling tax, and even wrote a python connector/API layer for it (if that happens to be the language you're working with: https://github.com/activefrequency/pyavatax)
--
You received this message because you are subscribed to the Google Groups "Stripe API Discussion" group.
To post to this group, send email to api-d...@lists.stripe.com.
Visit this group at http://groups.google.com/a/lists.stripe.com/group/api-discuss/.
To unsubscribe from this group and stop receiving emails from it, send an email to api-discuss...@lists.stripe.com.
Hey all,
I'm currently integrating the recipient API into our app, and had some questions about how to store the Tax ID of each recipient locally.
At tax time, we're going to have to generate 1099s for the recipients to whom we send transfers (as you guys document on your site). The recipient API doesn't look like it exposes any tax information; do I have to go ahead and store SSNs and EINs myself? Do you have any advice about how to handle this requirement? I'd imagine there are some legal requirements to storing sensitive information like this.
I was also curious if the recipient API could support returning the last 4 digits of the active bank account's routing number, so I can display this for users without storing the information on my end.
Thanks!
Hey all,
I'm currently integrating the recipient API into our app, and had some questions about how to store the Tax ID of each recipient locally.
At tax time, we're going to have to generate 1099s for the recipients to whom we send transfers (as you guys document on your site). The recipient API doesn't look like it exposes any tax information; do I have to go ahead and store SSNs and EINs myself? Do you have any advice about how to handle this requirement? I'd imagine there are some legal requirements to storing sensitive information like this.
I was also curious if the recipient API could support returning the last 4 digits of the active bank account's routing number, so I can display this for users without storing the information on my end.
Thanks!
Yes, you poll for a tax amounts (they're service is geared towards physical good and takes shipping sources/destination into accounts). And then later once everything is confirmed you can commit the tax. And they help prepare all the goods necessary for accounting based on those numbers.Since their target/specialty isn't for digital goods/services you may find something else that has a better rate. But generally, payment processors are never going to handle tax for you (since it varies so widely, and payment processing is enough of a hurdle).
Sadly, the Avalara website isn't very developer/small biz friendly. Best bet is to get on a phone call with them to find out if it fits for you
--