Ask HN: Stripe closed us after one $1,500 invoice and never asked for evidence
A small business found its Stripe account unceremoniously shut down after a $1,500 invoice, highlighting the opaque and often frustrating world of automated risk assessment by large payment processors. The incident has ignited a familiar debate on Hacker News about Stripe's customer support, its similarity to PayPal's historical issues, and the precarious position small businesses find themselves in when algorithmic decisions dictate their financial lifeline. The community is buzzing with advice on proper payment integration and commiseration over the perceived corporate coldness.
The Lowdown
A small business operating in the pre-booked appointment space for contractors faced an abrupt account closure by Stripe following their first significant transaction. After an initial $1 payment successfully confirmed a client's card, a subsequent $1,500 invoice for completed services was blocked, and the account swiftly terminated. Stripe cited "unacceptable level of risk" and payments that "don't appear to have been authorized by the customer," yet allegedly never requested any of the extensive evidence the business had, such as call recordings or client communications.
Key details of the incident include:
- The business charges contractors for pre-booked appointments with homeowners.
- A $1 payment link was used to save the client's card, which processed without issue.
- A $1,500 invoice charged to the saved card was blocked, and the account closed two days later.
- Stripe rejected appeals without requesting evidence, stating the business model was too risky.
- The client confirmed they did not dispute the charge and is now paying outside Stripe.
- The business suspects the $1 test charge followed by a large first invoice contributed to the "risky" flag.
- The owner sought guidance on both getting Stripe to review their case with evidence and structuring future payments to avoid similar issues.
This case underscores the challenges small businesses face when their operations, even if legitimate, inadvertently trigger automated fraud detection systems, leading to severe financial disruption without apparent human oversight or a clear path to resolution.
The Gossip
Algorithmic Anomalies and Fraudulent Fortunes
Many commenters quickly pinpointed the likely culprit: the payment pattern of a small $1 charge followed by a significantly larger one. This sequence is notoriously used by criminals to test stolen credit card numbers, triggering automated fraud detection systems. While some acknowledged this as a valid risk indicator, others debated whether it should lead to an immediate, irreversible ban without further investigation, especially for a new account. The proper use of Stripe's `SetupIntents` for saving cards for future, off-session use was frequently cited as the correct technical solution the OP should have employed.
Corporate Coldness and Customer Care Conundrums
A prevalent sentiment in the comments is deep frustration with Stripe's (and other large platforms') customer support, characterized by opaque decision-making, automated rejections, and a perceived lack of human interaction. Several users shared their own harrowing experiences of accounts being frozen or closed without clear explanations, even after being long-time or high-value customers. The discussion frequently drew parallels to PayPal's historical issues with arbitrary account closures, leading to a cynical conclusion that once an account is flagged, appealing to a human becomes nearly impossible, unless the story gains significant public attention like on Hacker News.
Business Model Bumps and Banking Best Practices
Commenters offered practical advice to the original poster, suggesting alternatives and best practices for payment processing. Recommendations included using Stripe's dedicated invoicing features, correctly implementing `SetupIntents` for recurring payments, and avoiding the problematic $1 test charge pattern. Beyond technical solutions, some speculated that the OP's specific business model (selling pre-booked appointments for contractors) might inherently carry a higher risk profile due to potential chargebacks or regulatory complexities in the construction sector, potentially resembling "high-risk" categories. For such cases, specialized "high-risk" payment processors or even local banking relationships were suggested as more suitable alternatives to Stripe.