If you were on Hacker News yesterday, you saw it. A detailed post-mortem from a merchant who lost thousands of dollars to friendly fraud — customers disputing legitimate charges after receiving the product — and Stripe, according to the author, doing effectively nothing.
The article, by the team behind gingerlime, has 146 points and is climbing fast. The comments section is a parade of developers recounting their own chargeback horror stories. The consensus is sharp: Stripe's dispute resolution system is structurally tilted against the merchant, and Stripe's own support team admitted they don't use cross-merchant fraud signals. A fraudster who burns one Stripe merchant walks away clean and hits the next one.
This conversation matters to us directly. Progenix runs its billing on Stripe. Our SaaS tiers — $0, $49, $149, and $499 per month — all flow through Stripe's payment infrastructure. When the developer community we serve is scrutinizing billing trust, we owe an honest answer. Here's what we think about the friendly fraud problem, why we chose Stripe anyway, and the fraud mitigation stack we're building around it.
The Gingerlime Critique Is Real — and It's Not New
The core of Yoav's argument on gingerlime is this: Stripe does not maintain a shared reputation graph across its merchant base. A customer who files five fraudulent chargebacks against five different Stripe merchants looks, to Stripe's system, like five independent disputes with no pattern. Each merchant fights alone. And because the card networks (Visa, Mastercard) default to siding with the cardholder, merchants lose even when they submit compelling evidence.
