Definition · SaaS Payment Recovery
Dunning is the process of recovering failed subscription payments through automated retry logic and customer communication sequences. In SaaS, a dunning system fires after a subscription payment fails — sending emails, SMS, and in-app notices over a 7–30 day window to recover the revenue before the account cancels. A properly configured dunning system recovers 50–75% of failed payments. Default processor behavior recovers 30–40%.
Definition
Definition
Dunning is the process by which a subscription business attempts to collect overdue payments from customers whose billing has failed. The term originated in traditional debt collection, where creditors sent escalating written demands — called “duns” — to debtors. In modern SaaS, dunning refers to the automated system that fires when a subscription payment fails: a combination of payment retry logic and customer communication designed to recover the revenue without manual intervention.
A dunning system has two components that must work together:
Key stat: According to Recurflux platform data across thousands of SaaS subscriptions, 9–15% of MRR is at risk from payment failures at any given time. Of that, 50–75% is recoverable with a properly configured dunning system — versus 30–40% with default processor behavior.
How It Works
How It Works
| Timing | Step type | Message focus | Purpose |
|---|---|---|---|
| Day 1 | Notification | Payment failed — what it means for their account | Inform, not alarm. Gives customer context before they notice access issues. |
| Day 3–5 | Recovery prompt | Direct link to update card or confirm payment method | Catches customers who check email within a few days of billing. |
| Day 7 | Urgency signal | Account status warning + payment update link | Converts customers who need a deadline to act. |
| Day 14 | Final notice | Account will be cancelled — last chance to recover | Highest urgency. Should include exact date of cancellation. |
| Day 21–30 | Win-back | Re-engagement offer or reactivation prompt post-cancel | Captures customers who let the account lapse but want to return. |
The sequence above is a baseline. Effective dunning systems vary each step based on why the payment failed — sending different email copy, different retry timing, and different urgency levels for insufficient_funds versus a stolen card versus an expired card. Generic, one-sequence-fits-all dunning leaves 15–25% of recoverable revenue on the table.
Types
Types
Passive dunning
Fires before a payment failure. Monitors card expiry dates 30, 15, and 7 days in advance and prompts customers to update their card proactively — before the charge ever fails.
Recovery impact: eliminates 20–30% of failures before they occur, reducing the size of the active dunning queue.
Active dunning
Fires after a payment failure has occurred. Combines retry logic with email/SMS sequences to recover the failed charge over a 7–30 day recovery window.
Recovery impact: recovers 50–75% of failed payments when code-specific retry and messaging logic is applied.
Best-practice dunning systems run both in parallel. Passive dunning (card health monitoring) reduces the volume of failures that reach the active dunning queue. Active dunning recovers the failures that still occur. Running only active dunning is the equivalent of mopping the floor without fixing the leaking pipe.
Benchmarks
Benchmarks
| Approach | Recovery rate | At $100K MRR |
|---|---|---|
| No dunning (manual only) | 10–20% | $12,000–$18,000 lost annually |
| Default Stripe Smart Retries | 30–40% | $8,000–$14,000 lost annually |
| Basic 3-step dunning email | 40–50% | $6,000–$10,000 lost annually |
| Code-specific retry + 5-step dunning | 60–70% | $3,000–$6,000 lost annually |
| Full 5-layer recovery stack | 65–75% | $2,000–$5,000 lost annually |
Assumes 12% MRR at risk monthly from payment failures. Industry average across SaaS billing platforms, 2026.
FAQs
FAQs
What is dunning in SaaS?
In SaaS, dunning is the process of communicating with customers whose subscription payments have failed to recover the revenue before their account is cancelled. It typically involves a sequence of automated emails, retry attempts, and in-product notices sent over 7–30 days after the initial payment failure.
What is the difference between dunning and payment retry?
Payment retry is the automated re-attempt to charge a card after a failure. Dunning is the customer-facing communication — emails, SMS, and in-app notices — that accompanies those retries. Effective recovery combines both: smart retry logic that chooses the right time to re-charge, and dunning messages that prompt customers to update their payment method when the card cannot be fixed automatically.
How many dunning emails should you send?
Industry data from Recurflux across thousands of SaaS subscriptions shows a 3–6 step dunning sequence captures most recoverable revenue. Step 1 (Day 1): notification of failure. Step 2 (Day 3–5): first recovery prompt with payment link. Step 3 (Day 7): urgency message with account impact. Step 4 (Day 14): final warning. Steps 5–6 (Day 21–30): win-back framing if still failed. Beyond 6 steps, incremental recovery drops below 2% per additional email.
What is a good dunning recovery rate?
A well-configured dunning system with code-specific retry logic recovers 50–75% of failed subscription payments. Default Stripe Smart Retries alone recover 30–40%. The gap between 40% and 70% recovery rate at $100K MRR is roughly $40,000–$60,000 in annual revenue.
Does dunning work for all payment failure types?
No. Dunning emails are effective for soft declines — failures where the card is valid but the payment cannot be processed right now (insufficient_funds, do_not_honor, try_again_later). For hard declines — fraudulent cards, lost/stolen cards, account closed — the card is permanently invalid and dunning emails should not prompt for a retry. They should prompt for a new card. Code-specific dunning sequences send different messages based on why the payment actually failed.
What is passive dunning vs. active dunning?
Passive dunning (also called pre-dunning) catches failing cards before a payment attempt fails — by monitoring card expiry dates 30, 15, and 7 days in advance and prompting customers to update their card proactively. Active dunning fires after a payment failure has already occurred. Best-practice dunning systems run both in parallel: passive dunning reduces the failure rate, active dunning recovers the failures that still occur.
Stop relying on default retry behavior
Recurflux runs code-specific retry logic and adaptive 5-step dunning sequences across Stripe, Paddle, Razorpay, Cashfree, and RevenueCat. Connect in under 5 minutes and see your current recovery rate versus what's recoverable.
Related Features
Related Features
Dunning email sequences →
Adaptive 5-step sequences that vary by decline code, tier, and subscription value.
Smart payment retry →
Code-specific retry cadences for 30+ decline codes — not generic Stripe retries.
Recovery dashboard →
Full attribution dashboard tracking recovery rate by code, tier, and sequence step.
Win-back emails →
Reason-aware re-engagement sequences for customers who still cancel after dunning.