Failed card payments are involuntary churn - revenue you lose without the customer ever choosing to leave. See how much MRR is at risk, how much you are losing today, and how much a better dunning process can win back.
Your monthly recurring revenue.
Share of MRR whose card payment fails each month.
Share of failed payments you recover today.
Best-practice dunning recovers about 70%.
What you recover at different target recovery rates, holding your MRR, failure rate, and current recovery fixed. Best-practice dunning lands around 70 percent.
| Target recovery | Recovered / mo | Additional vs now / mo | Annual uplift |
|---|
of all SaaS churn is failed payments
of failed charges, done well
typical hit to a subscription business
Voluntary churn is a choice: the customer decided to leave, and you fix it with product and pricing. Involuntary churn is different - a card failed, and the customer never meant to go anywhere. You fix that one with timing and tone, not roadmap work.
Lumping the two together hides the cheapest revenue you will ever recover. The failed-payment slice wanted to stay; it just needs a smarter retry and a card-update prompt. Measure it on its own and the fix gets obvious.
Recoverable MRR = MRR × failure rate × (target - current) Example: $50,000 MRR, a 7% failure rate, lifting recovery from 30% to 70%:
When a card fails and the subscription lapses, most billing exports just show a churned customer. The loss gets miscoded as voluntary churn, so it hides in the dashboard and never gets fixed. Name it as involuntary churn and it becomes recoverable.
Dunning is a retry schedule plus card-update messaging. No new customers, no ad spend - just revenue you already earned landing in the bank. Since Stripe charges nothing on a decline, the recovered MRR is almost pure margin against the cost of the workflow.
Involuntary churn is revenue lost when a subscription cancels because a payment failed - an expired card, insufficient funds, or a bank decline - not because the customer chose to leave. They wanted to stay, so most of it is recoverable. It's the same idea as the recoverable side of revenue churn: cash leaving your book for a reason you can fix with billing logic rather than product work.
It varies by segment and payment mix, but failed payments commonly drive 20 to 40 percent of total churn and cost the average subscription business around 9 percent of recurring revenue a year. Use those as typical ranges to sanity-check your own number, not as a target - the only figure that matters is the share of your MRR whose card fails each month.
A well-run dunning process recovers about 70 percent of failed charges. That comes from stacking layers: smart retry timing, pre-dunning warnings that prompt a card update before the charge fails, and in-app or email card-update prompts. No single layer carries it - they add up. If you're well below 70 percent today, most of the gap is timing and tone, not engineering.
No. There is no processing fee on a decline, so a failed payment costs you nothing in fees - you only lose the revenue if the subscription lapses. That makes recovered revenue almost pure margin: the only cost is running the dunning workflow. You can size the fee side separately with the Stripe fee calculator.
Voluntary churn is a choice: the customer decided to leave, and you fix it with product and pricing. Involuntary churn is a billing glitch: a card failed, and you fix it with retries and messaging. Different problems, different tools. Lumping them into one churn number hides the cheapest revenue you will ever recover.
Four moving parts: smart retry timing that spreads attempts across paydays, pre-dunning emails that warn before the card fails, in-app card-update prompts, and a clear final notice that sounds like support rather than collections. Read the dunning guide for the full retry cadence and recovery stack.
The median across subscription businesses is about 48 percent of failed payments recovered, per Recurly's benchmark of tens of millions of subscribers, so anything north of 50 percent is above the pack and best-practice dunning reaches roughly 70 percent. The jump comes almost entirely from retry logic: intelligent, spread-out retries recover roughly 71 percent of failures versus about 53 percent for basic single/batch retries. If you are sitting near the median, the gap to 70 percent is timing and messaging, not new engineering.
Recurly's data puts recovery on failed annual renewals at about 23 percent versus roughly 53 percent on monthly plans. A monthly charge that fails gets several cheap retries across the next payday cycle, and the customer is in the habit of paying you. An annual charge is one large amount, often on a card that expired in the eleven months since the last payment, with no recent paydays to retry into - so it skews your involuntary churn harder. Pre-dunning warnings before the renewal date and a card-updater service do most of the heavy lifting on annual plans.
No, and the reason for the decline is what sets the ceiling. Expired or replaced cards recover at roughly 80 to 90 percent because a card-update prompt or an account-updater service fixes them outright. Insufficient-funds declines recover around 60 to 70 percent once you retry into the next payday. Hard declines and fraud blocks recover only about 20 to 30 percent because no retry will clear them. So your achievable recovery rate depends on your decline mix, not just your dunning effort. Splitting failures by reason code tells you which lever to pull.
Mowt splits involuntary from voluntary churn straight from your Stripe data, so you see exactly how much MRR is leaking to failed payments - and how much your dunning is winning back, updated daily.
No credit card required · Connect Stripe in 1 click
No credit card required. Connect Stripe in 1 click.
We're building iOS and Android apps that'll bring your metrics everywhere.
Our mobile apps are currently in active development. Follow us on social media for updates and be the first to know when they launch.