|
Good point! If you'll allow me to provide a bit more background, when we started talking to users, a merchant of record set up was certainly a fit for some, especially those that didn’t want to even think about tax, but it wasn’t for all. Some users didn’t want to forgo control over the checkout experience, others didn’t want someone else’s name on the statement descriptor, and others pointed out that merchant of record meant their buyers were paying more than some competitors as they were collecting tax everywhere from day 1, (vs. if you handle yourself you may not need to collect tax in a state or country until you reach a threshold, e.g. California is $500k). However, one pain point in common across all users, was around the integration and maintenance aspects of handling tax during checkout, so our focus really became how do we abstract away tax at checkout…which is why enabling Stripe Tax really comes down to `automatic_tax[enabled]:true`. All that is to say, we’re definitely not perfect and always want to hear how we can improve. We’re optimistic that we’ve built solid foundations such that we can now add much more functionality to meet any and all user’s tax needs, or even taking on all liability. All and all we very much rely on user feedback to prioritize what we build, so if merchant of record would, to quote Patrick recently, be the thing that makes you say “FINALLY”, do let us know! |