Subscription payment failures cost SaaS businesses 5-15% of MRR through churn that neither them or their customers requested. Most of that loss is recoverable through smart retry logic.
5 Key Facts
- Involuntary churn accounts for 5-15% of MRR loss in SaaS businesses. Industry-cited band, varies by sub-base age and geography.
- Card updaters (account updater services) recover 30-50% of expired-card failures automatically. Stripe, Adyen, and Checkout.com all provide them.
- Smart dunning sequences recover 10-20% of failed payments within 7 days of first failure. Industry benchmarks.
- Optimal retry timing is not immediate. Most issuers attempt retries 2-4 days after initial decline.
- Visa, Mastercard & American Express mandate at least one retry attempt before a subscription is classified as cancelled by issuer. Compliance consideration.
Subscription businesses obsess over acquisition and voluntary churn. They often accidentally overlook involuntary churn, which is the failure mode that costs the least to fix and the most to leave alone. Involuntary churn from failed card payments sits at 5-15% of MRR for most subscription businesses. The businesses that recover it use four things: a structured dunning sequence, smart retry timing, network tokenisation, and email recovery before retry.
The cost of inaction: for a £1m monthly subscription business, equates to £70k/month lost in compounded list revenue. For a stable business, over 4 months this could be as high as £700k per month in lost recurring revenue. 1-2 weeks of engineering work or a good subscription billing tool.
Why do card transactions fail?
The customer did not cancel. Their card failed. The reasons, in rough order of frequency:
- Insufficient funds: 30-40% of failures. Temporary. Often recoverable with retries at different days weekly.
- Card expired: 20-25% of failures. Customer forgot to update card or auto-updating of cards not available. Recoverable with card updaters, automatic customer message or telephone prompts.
- Card reported stolen or fraud-blocked: 10-15% of failures. Requires card auto updaters, automated messaging or telephone.
- Issuer-side decline (no specific reason): 15-20% of failures. Recoverable with smart retry.
- 3DS authentication failed: 5-10% of failures. Customer abandoned the flow.
- Bank-side velocity or risk block: 5-10% of failures. Hard to recover without customer action.
Most of these are temporary. A retry, timed correctly, recovers the majority. The merchants who do not retry lose the transaction.
The dunning sequence: timing, retry, and communication
Dunning is the polite word for "chase the customer for money they owe you." The dunning sequence is the series of emails and retry attempts you make after the first charge fails. Most subscription billing tools have a dunning feature. Most are configured badly out of the box.
The default sequence in most tools: retry every 3 days for 4 attempts, then cancel. The problem: 3-day spacing is too short for the most common failure (insufficient funds). Customers get paid weekly or monthly. A retry 3 days after the failure misses the next payday.
Smart Retry vs Blanket Retry
Smart retry is the practice of timing retries based on the failure reason and the customer's payment history. Static retries is the practice of automatically retrying payments a set number of days or hours after the previous failed attempt, regardless of the reason or context. Sequences of smart retries typically recover 15-25% more failed payments than static retries.
The basic pattern:
- Retry 1: 24-48 hours after the original failure (catches short-term temporary issues)
- Email 1: 48 hours after failure (heads up: your payment failed, here's the link to update)
- Retry 2: 5-7 days after failure (catches next-payday timing for insufficient funds)
- Email 2: 5-7 days after failure (firmer: update your card to keep your subscription)
- Retry 3: 14 days after failure (catches card-update customers)
- Email 3: 14 days after failure (last chance: subscription will cancel in 7 days)
- Retry 4: 21 days after failure (final attempt)
- Cancellation: 28-30 days after original failure
This sequence catches the next-payday timing. It also gives the customer three weeks of warning before cancellation. Most customers update their card within the first two emails.
Network tokens: the real prevention layer
Network tokenisation is what Visa and Mastercard built to solve the card-expired failure mode. When a customer first pays, the card scheme (Visa or Mastercard) issues a network token. The token is automatically updated when the customer gets a new card from their bank. Your PSP stores the token, not the card number. When the underlying card expires, the token stays valid.
This single feature removes 20-25% of involuntary churn for subscription businesses. Most PSPs (Stripe, Adyen, Checkout.com) support network tokenisation. Most subscription billing tools (Recurly, Chargebee, Stripe Billing) use it automatically when the PSP supports it.
If you are not using network tokens, your failure rate on expired cards is whatever Visa and Mastercard report. If you are using them, your failure rate drops because the token resolves the expiry silently.
Email timing for recovery
Email is the lever that determines whether the customer updates their card or cancels. Three rules:
- Send the first email 48 hours after failure, not 24 hours. The customer may not have noticed yet. A 48-hour delay reads as attentive, not panicky.
- Send the cancellation-warning email 7 days before cancellation, not 3 days. 7 days gives the customer time to act. 3 days is not enough.
- Use clear and informative language, not jargon. "Please check your payment method" reads better than "Your subscription has entered dunning state."
Recovery rate benchmarks
Recovery rates by strategy:
- No dunning (one retry, immediate cancellation): 10-20% of failed payments recovered
- Static retry (every 3 days, 4 attempts): 30-40% recovered
- Smart retry + dunning emails: 50-65% recovered
- Smart retry + dunning + network tokens: 70-80% recovered
The difference between "no dunning" and "smart retry + dunning + network tokens" is roughly 60% of failed payments recovered instead of 15%. On a £1m MRR business with 7% involuntary churn, that is £42k/month recovered.
Tools that handle this well
Recurly, Chargebee, and Stripe Billing all have smart retry + dunning + network token support. The differences are in UX, reporting, and pricing. Most businesses above £100k recurring monthly revenue benefit from one of these tools. Below £100k MRR, your providers billing engine should be sufficient.
The investment: 2-10 days of integration work to build your own billing engine or an off the shelf subscription tool's cost and implementation effort. The payback: 4-12 weeks of lost recurring revenue, depending on your size and current billing retry model.
Want to see how much lost revenue involuntary churn is costing you? Send Tonkr three months of subscription billing data and we will then model the financial impact for you, alongside estimated gains of smart retries, dunning and account updaters. Free, with no obligation.
The Numbers
5-15%: Recurring revenue lost to involuntary churn70-80%: Recovery with smart retry + dunning + network tokens2-6 weeks: Payback period for the fixsources:F³ Fund ItRecurly churn benchmarks Stripe involuntary churn benchmarks
