My Stripe Tax Story (gist.github.com)

Article summary

The author of the article experienced issues with Stripe Tax, which caused hundreds of recurring subscription invoices to be disabled due to missing location inputs, resulting in significant financial losses. The author had enabled Stripe Tax to charge provincial sales tax for Canadian customers, but the integration failed to work correctly, and Stripe did not notify them of the issue. The author had to spend time and effort to resolve the issue and communicate with affected customers. The incident highlights the importance of careful integration and testing of payment systems.

Main themes

• payment system integration
• tax regulation complexity
• communication and support
• financial losses and liability
• fee structures and value proposition
• testing and quality assurance

What commenters say

• The author's failure to thoroughly test the Stripe Tax integration was the primary cause of the issue.
• Stripe's silence on the failed invoices was a significant failure, and the company should have notified the author sooner.
• The complexity of tax regulations and payment systems can lead to unexpected errors and financial losses.
• The extra fees charged by Stripe for its tax integration service are not justified by the value provided.
• The incident highlights the need for more transparent and proactive communication from payment processors like Stripe.
• The author's experience was likely due to a botched integration, but Stripe could have done more to help resolve the issue.
• The financial losses incurred by the author could have been mitigated if Stripe had provided more timely and effective support.