Lost MRR Calculator
Up to 40% of SaaS churn happens without the user wanting to cancel — their credit card simply fails (industry report estimates). Use our interactive calculator to simulate the impact on your recurring revenue and how much you could recover.
See how much you're losing (silently)
Cards expire, banks decline charges, and you lose subscribers without ever knowing. Use this calculator to see your real revenue leak.
Typically 5%–10% of B2C/B2B payments fail each month.
Revenue Lost Per Year
That's code you shipped that you're not getting paid for.
Recoverable with Dunning Lite
Add your email to join the closed Beta and start recovering your revenue.
Executive Summary (TL;DR)
- •On average, 5% of all subscription transactions fail every month.
- •Without an active dunning system, you cumulatively lose key dollars from your Lifetime Value (LTV).
- •Connecting Dunning LITE to your Stripe account automates up to 40–60% recovery rate instantly.
Involuntary Churn: The silent MRR killer
Building a SaaS is hard. Acquiring users is even harder. That's why it's a tragedy when, after getting someone to love your product, you lose them because their American Express card was replaced or their bank blocked the payment due to insufficient funds. This is called passive or involuntary churn.
B2B Benchmarks: What does the data say?
4–7%
of transactions fail monthly
15–22%
recovered by Stripe Smart Retries alone
40–60%
recovered with dedicated dunning
How can I plug this leak?
The manual approach is to go to your Stripe Dashboard, search for failed payments month by month, and send a one-off email to each customer from your Gmail asking them to update their card. This doesn't scale and you'll forget.
The smart solution is to connect a specialized Dunning tool. Dunning LITE connects to your Stripe in 2 clicks and springs into action only when a charge fails. It analyzes the error code (bank, CVC, expiry) and fires a hyper-personalized recovery sequence.
How Payment Failure Codes Affect Your Recovery Rate
Not all failed payments are created equal. When Stripe returns a decline, it comes with a specific error code — and that code tells you a lot about whether you can actually recover that payment, and how fast you need to act.
Most tools ignore this signal entirely. Dunning Lite classifies every failure automatically so the right message goes out at the right time.
Here are the three categories that matter:
Soft Declines — Insufficient Funds / Temporary Block
Recovery: 50–70%This is the most common type. The card is valid, the customer hasn't left, but their account didn't have the funds at billing time — or their bank flagged the charge as suspicious. Stripe error codes like insufficient_funds, do_not_honor, and card_velocity_exceeded fall here.
What to do
Send a friendly nudge within 24 hours. Keep it short, no blame. The customer probably doesn't even know the charge failed. A plain-text email from a real person works better than a branded HTML template here.
Hard Declines — Canceled or Expired Card
Recovery: 30–45%The card no longer exists. This includes cards flagged as lost or stolen (lost_card / stolen_card), genuinely expired cards (expired_card), and closed accounts. Stripe will not retry these — there's no point.
What to do
You need the customer to add a new card. Subject line and CTA are critical. Link directly to your Stripe billing portal or a hosted payment update page — every extra click kills conversion. Dunning Lite generates that link automatically.
SCA / 3D Secure Failures
Recovery: High (if handled correctly)Strong Customer Authentication (SCA) is required by European banking regulations, and it's growing globally. When a customer's bank requires 3D Secure verification and the charge was submitted without it — or the customer didn't complete the challenge — the payment fails with codes like authentication_required or payment_intent_authentication_failure.
What to do
Don't retry the charge server-side. Generate a new PaymentIntent that requires customer action, and email them a secure link to complete the authentication. This is one of the most under-handled failure types in bootstrapped SaaS — and one of the easiest to recover once you have the right tooling. See our Stripe invoice.payment_failed webhook guide for the full technical walkthrough.
Stripe Smart Retries vs. Dedicated Dunning: The Numbers
If you're on Stripe Billing, you already have Smart Retries enabled by default. Stripe's machine learning picks the optimal time to retry a failed charge — typically over a 4-week window. It's better than nothing. But "better than nothing" is not a revenue strategy.
Stripe Smart Retries
15–22%
recovery rate
Retries the charge silently. Customer is never notified. No personalization by failure type.
Dedicated Dunning
40–60%
recovery rate
Retries + personalized email outreach. Failure-type aware. Customer knows what to do.
💡 Why does Stripe fall short?
Smart Retries only retries the charge — it doesn't tell the customer anything. They're completely in the dark. Their access may get suspended, they get frustrated, and they churn for real. On top of that, Stripe has no way to personalize the outreach based on failure type. A soft decline and an expired card need completely different messages — Stripe treats them the same.
Dedicated dunning tools — including Dunning Lite — layer email outreach on top of retries. The moment a payment fails, the customer gets a human-written email explaining what happened and what to do. No AI copy, no generic "Your payment failed" subject line. A real message that sounds like it came from you. That's the difference.
Want to see how the alternatives stack up? Full comparison: Stripe Smart Retries vs. dedicated dunning tools and Dunning Lite vs. Churnbuster.
⚠️ Early Access note
Dunning Lite currently sends one email per failed payment. Multi-step sequences are on the roadmap. Even with a single well-timed email, founders report meaningful recovery — because the bar is low when you're competing against silence.
What Happens to Your LTV When You Ignore Failed Payments
Let's make this concrete. Say you have 200 subscribers at $49/month. Your MRR is $9,800. A 5% monthly failure rate means 10 charges fail every billing cycle. You ignore them.
Month one, you lose $490. That's annoying but survivable. Here's where it gets ugly: those 10 customers don't come back. Month two, your active base is 190 — and 5% of that fails again.
By month 12, you've churned through the equivalent of 45–50 subscribers due to payment failures alone. That's roughly $2,200–$2,450 of MRR gone — not from dissatisfied customers, but from a fixable billing problem.
And that's just the MRR math. It doesn't account for:
- Lost expansion revenue. Customers who churn can't upgrade. Every customer you lose to a failed payment is a customer who will never move to your higher tier.
- Lost referrals. Happy long-term customers refer others. Involuntary churners don't — and some of them will write a negative review because their access got cut off without warning.
- Inflated CAC. You spent money acquiring those customers. Payment failures wipe out that acquisition investment entirely.
- LTV compression. Every failed-payment churn directly reduces your average LTV, which in turn affects how much you can afford to spend to acquire the next customer. It's a compounding problem.
✅ See it for your own numbers
The involuntary churn calculator at the top of this page lets you model this accurately. Run it with a 5% failure rate and see what 12 months of inaction actually costs. Then check out the dunning email generator to see what a recovery email looks like in practice.
If you want to go deeper on the terminology, our SaaS metrics glossary covers involuntary churn, payment failure rate, and LTV in plain language.
Frequently Asked Questions
What percentage of SaaS transactions fail each month?
Industry benchmarks consistently put the figure between 4% and 7% for subscription businesses. The exact number varies by average transaction size, customer geography, and billing cycle length. Annual plans tend to have slightly higher failure rates because cards expire in the intervening year.
If you're seeing numbers above 7%, audit your customer base for geographic concentration (EU customers trigger more SCA failures) or outdated default payment methods.
How much MRR can I recover with dunning?
Realistically, a well-configured dunning setup recovers 40–60% of failed payments. If you're currently relying only on Stripe Smart Retries, you're leaving 20–40% of failed payment revenue on the table.
For a $10K MRR business with a 5% failure rate, that's $200–$400/month in recoverable revenue. Over 12 months: $2,400–$4,800. The math makes the tooling cost easy to justify.
Does Stripe already handle failed payments?
Sort of. Stripe Billing includes Smart Retries, which automatically retries failed charges at optimized times over a 4-week window. This recovers about 15–22% of failures on average.
What Stripe doesn't do: send personalized emails, generate card update links, or classify failures by type to customize outreach. That's what dedicated dunning tools add. Full breakdown here.
How quickly should I contact customers after a failed payment?
Within 24 hours for soft declines. Within 48 hours for hard declines (expired or canceled card). The faster you reach out, the higher your recovery rate — customers are more receptive before they've had time to rationalize the cancellation.
Dunning Lite fires the recovery email as soon as it receives the invoice.payment_failed webhook from Stripe, which typically arrives within minutes of the charge attempt. See our webhook implementation guide if you want to understand the technical flow.
Is Dunning Lite free to try?
Yes. There's a live demo where you can see the product without connecting your Stripe account.
When you're ready to go live, Dunning Lite is $29/month flat — no percentage of recovered revenue, no usage tiers, no surprise bills. You pay the same whether you recover $500 or $50,000. Commission-based pricing creates misaligned incentives. We'd rather just charge a flat rate. Early adopters lock in at the founding rate.