How much is leaking from a book your size?

A benchmark of how much recurring revenue a SaaS business of your size typically loses to failed payments that were never recovered, computed from your MRR and, if you enter it, your monthly churn rate. It needs no billing access and shows the order of magnitude, not your accounts. Your exact number, with the customer names attached, comes from Exeechain reading your Stripe on a paid plan.

When you connect Stripe on a paid plan the access is read-only: no charges, no refunds, no writes, nothing in your account is touched. The product reads subscriptions, invoices and payment methods to name the failed payments, expiring cards and slipping renewals per customer.

No. On a connected account it reports what is failing and what it is worth, in three labelled buckets: money you are losing right now (failed and past-due payments), contracted renewals at risk, and expansion that is an estimate and is never counted as a loss. A recovery rate is only ever reported after a sequence has actually run on your book.

Seven things, roughly in order of size: failed payments never recovered, cards expiring before renewal, discounts that never ended, seats used but not billed, renewals that lapsed unnoticed, plan changes never invoiced, and ad-hoc credits. The revenue leakage guide on the blog covers each one with the billing query that finds it.

A customer whose card failed did not decide to leave; they are usually still using the product. That makes it the cheapest churn to recover: a pay link and a follow-up on day 3, 7, 14 and 21, with copy that matches what the bank actually said. In most subscription books it is 20 to 40 percent of what gets called churn.