Dunning management: how to recover failed payments
What dunning management is, why subscription payments fail, a step-by-step retry and email sequence, how to automate it and which numbers to track.
By Florian
Dunning management is the structured, usually automated process of following up when a recurring payment fails, so a temporary problem such as an expired card or a bank decline does not turn into a lost customer. Done well, it combines timed retries, clear customer messages and a defined end point. If you run a SaaS or subscription business on Stripe, Chargebee, Paddle, Recurly or another billing system, NoChurn automates this routine, free until $300 MRR and then from $9 per month.
TL;DR
- Dunning management is the process of retrying failed subscription charges and notifying customers until the payment is recovered or the subscription ends.
- Failed payments are involuntary churn: the customer usually did not decide to leave, so the fix is recovery, not a retention discount.
- A good sequence has four parts: classify the decline, retry at sensible times, send short emails with a one-click card update, and set a clear final deadline.
- Automating the process removes manual follow-up and lets billing, product, finance and support each own a clear piece.
- Pricing models differ: some tools take a share of recovered revenue, while NoChurn publishes flat monthly plans based on your MRR.
What dunning management means
The word “dunning” comes from debt collection, where it meant repeatedly asking a debtor to pay. In subscription businesses it has a milder meaning. A card is charged every month or year, the charge fails, and the company has to get the customer back to a paid state without friction.
That makes dunning a recovery workflow, not a collections effort. The same word is used in accounts receivable for overdue invoices, and the principle is the same: remind, retry, escalate, resolve. For SaaS, the emphasis is on speed and tone, because the customer is still using, and usually wants to keep using, your product.
Dunning, involuntary churn and voluntary churn
Voluntary churn happens when a customer decides to cancel. Involuntary churn happens when the payment fails and the subscription lapses anyway. The two need different responses. A customer who chose to leave may respond to an offer, a pause option or a better plan. A customer whose card expired needs a reminder and an easy way to update it. For the full picture of causes and fixes, read our guide to involuntary churn.
This distinction shapes everything in the sequence below. Do not send a discount to someone whose only problem is a declined card. Send them a clear message and a link that fixes it in seconds.
Why payments fail
Most failures fall into a few groups. Knowing which one you are dealing with decides what happens next.
| Failure type | Typical cause | Best response |
|---|---|---|
| Soft decline | Insufficient funds, temporary issuer hold, a limit reached | Retry later, notify the customer |
| Expired or replaced card | Card reached its expiry date or was reissued | Ask for a card update, send before expiry if possible |
| Authentication required | The issuer wants extra verification from the cardholder | Send the customer to a page where they can complete it |
| Hard decline | Closed account, lost or stolen card, suspected fraud | Do not keep retrying the same card; request a new payment method |
Card networks publish material on this. Visa’s paper on balancing convenience and control notes that categorizing decline codes helps identify and troubleshoot declines, including those caused by insufficient funds, suspected fraud and the need for additional customer authentication. In practice, your dunning logic should read the decline code and branch, rather than treating every failure the same.
The automated dunning process, step by step
Here is how a well-built process runs from the first failed charge to a final outcome.
1. Detect the failure and read the decline code
Your billing system reports the failed charge with a code and a reason. This is the input for everything else. Common mistake: logging only “payment failed” and losing the reason, which forces you to treat a temporary hold and a closed account the same way.
2. Choose the retry schedule
Retries work best on soft declines, where the cause may clear on its own. Spread attempts over days, not minutes, so a customer has time to be paid, to top up an account or to see your email. Avoid hammering a card that returned a hard decline. Repeated attempts on such cards add little and can create more declines.
Two practical rules:
- Space the attempts so they land on different days of the week and different times of the month, since balances change around paydays and billing dates.
- Stop retrying when the decline code says the card cannot work, and move straight to a card-update request.
3. Notify the customer
Email is the main channel, and the first message should go out quickly. It should say what happened, what the customer needs to do, and how long they have. Keep it calm and short. State the plan name and amount, and put one button in the message: update payment method.
A workable sequence for a monthly plan:
- Day 0: a friendly notice that the payment did not go through, with the update link.
- Day 3: a short reminder that mentions what the customer keeps access to.
- Day 7: a firmer message that gives the date access will change.
- Final notice: a last message before cancellation or downgrade, with the update link repeated.
- 01 Day 0 Payment failed: what happened, one update button
- 02 Day 3 Short reminder: access continues for now
- 03 Day 7 Firmer: the date access will change
- 04 Final notice Last chance before cancel or downgrade
These timings are a starting point, not a rule. Adjust them for annual plans, where a failed payment is a larger amount and deserves a more personal follow-up. For wording you can reuse at each step, see our dunning email templates.
4. Give the customer a one-click way to fix it
Every step you add between the email and the updated card loses some customers. Link straight to a secure page where the customer can enter a new card, with no login wall if you can avoid it. When the update succeeds, trigger an immediate retry rather than waiting for the next scheduled attempt.
5. Decide what happens at the end
Define the final outcome before you start: cancel the subscription, downgrade to a free tier, or pause access. Write it down and say it in your emails. A vague ending creates support tickets and accidental free usage.
6. Record the result
Track each failed payment to one of three results: recovered by retry, recovered after the customer updated the card, or lost. This record is how you improve the schedule over time.
- 01 Recovered by retry A later attempt went through
- 02 Recovered after an update The customer added a new card
- 03 Lost The final date passed without payment
How to automate dunning
Automating dunning means connecting your billing data to a system that reacts to failures without anyone clicking anything. There are three common routes.
Built-in billing features. Most billing platforms include basic retries and templated emails. These are a good first layer. Recurly, Chargebee, Lemon Squeezy and Maxio each offer retries and emails out of the box, with settings that stop at different points.
A dedicated recovery tool. This connects to your billing system, reads decline reasons, personalizes messages and reports on what was recovered. NoChurn integrates with Stripe, Chargebee, Paddle, Recurly and other billing systems, or any billing through its API, and writes personalized emails with AI. It also scores churn risk from customer data so you can act before a payment fails, and it handles chargebacks and customizable cancel flows.
An in-house build. Your engineers can listen to billing webhooks and send emails themselves. It works, but you then own the retry logic, templates, deliverability, edge cases and reporting indefinitely.
Who owns what
Automation still needs clear responsibilities. One practical split gives billing the balances and payment attempts, product the access decisions, finance the credits and exceptions, and customer success the personal escalation. Write this down once and your team stops asking who should handle a particular failed invoice.
Writing dunning emails that customers act on
The tone should be neutral and helpful. Most customers who hit a failed payment did not do anything wrong.
- Use a clear subject line. Say that the payment failed and name the product.
- Lead with the action. The update button should be visible without scrolling.
- Explain in plain words. Say “your card issuer declined the charge” instead of quoting a raw error code.
- State the consequence and the date. Customers respond to a specific deadline more than to a vague warning.
- Offer a human route. For high-value accounts, add a line saying who they can reply to.
- Send from a recognizable address. Emails from your own domain look familiar and are less likely to be ignored. NoChurn offers sending from your own domain from $9 per month.
For customers in different regions, adapt the currency format, the language and the date style. Keep the layout and the single action the same everywhere.
Pricing models for dunning tools
If you are comparing dunning options, the pricing model matters as much as the feature list.
| Model | How it works | What to watch |
|---|---|---|
| Percentage of recovered revenue | The vendor takes a share of every payment it recovers | Cost rises as you grow or as recovery improves |
| Flat monthly fee by revenue tier | A fixed price for a range of monthly recurring revenue | Predictable; costs change only when you move up a tier |
| Usage or per-email pricing | You pay per message or per retry | Hard to forecast during spikes |
| Built-in billing add-on | Part of your billing platform’s plan | Fewer customization options |
NoChurn does not charge a percentage of recovered amounts. Its plans are based on MRR, with every feature on every plan:
| MRR | Price |
|---|---|
| Up to $300 | Free |
| Up to $2k | $9 per month |
| Up to $10k | $19 per month |
| Up to $25k | $29 per month |
| Up to $75k | $49 per month |
| Up to $125k | $99 per month |
| Up to $200k | $149 per month |
| Up to $250k | $229 per month |
| Up to $300k | $299 per month |
| Up to $400k | $349 per month |
| Up to $500k | $399 per month |
| Above $500k | Custom |
The only exception is sending emails from your own domain, which needs a paid plan, from $9 per month.
How to measure dunning performance
A process you do not measure will drift. Track these numbers monthly:
- Recovery rate: the share of failed payments that end in a successful charge.
- Time to recovery: the average days from first failure to payment. Shorter is better for cash flow and for the customer relationship.
- Recovery by decline type: soft declines should recover far more often than hard declines. If they do not, your retry timing needs work.
- Email performance: open and click rates on each message in the sequence, plus how many card updates each one produced.
- Involuntary churn rate: the share of customers lost to payment failure each month, tracked separately from voluntary churn.
Review them together. A rising recovery rate with a growing support ticket count may mean your emails are confusing, not that the process is better.
Common dunning mistakes
- Treating all failures alike. A hold on an account and a canceled card need different handling.
- Sending a discount to an involuntary churner. It trains customers to let payments fail on purpose and gives away margin you did not need to give.
- Cutting access on day one. A short grace period protects the relationship and costs little.
- Burying the update link. If the customer has to log in, find billing settings and re-enter details, many will not.
- Having no owner. Without one, exceptions pile up unanswered.
- Forgetting consumer plans. Individual subscribers behave differently from business accounts, so tune timing and tone.
Where NoChurn fits
If your billing system’s built-in retries are not enough, NoChurn’s failed payments feature connects to your billing platform and runs the recovery routine described above: retries, AI-written personalized emails you can review, a hosted card update page, and win-back emails for customers who already left. Pricing is flat by MRR, never a cut of what is recovered.
Why we approach dunning this way
A failed payment is a billing event, not a goodbye. Most customers whose card declines still want the product, and the company’s job is to make the fix easy and the tone respectful.
That is also why pricing should not punish success. A fee that takes a percentage of recovered revenue grows as your recovery improves. Flat plans by MRR let a startup see its cost in advance and keep the gains.
Dunning should not stop at retries either. Scoring churn risk from customer data, personalizing messages with AI and offering customizable, click-to-cancel flows let a team deal with involuntary and voluntary churn in one place, connected to Stripe, Chargebee, Paddle, Recurly and other billing systems.
FAQ
What is dunning management?
Dunning management is the process of following up when a recurring payment fails. It combines retries, customer emails and a defined final outcome so the subscription can continue. The goal is to recover revenue and reduce involuntary churn.
What is automated dunning?
Automated dunning runs the retry and notification steps without manual work. Software reads the failed payment from your billing system, chooses what to do based on the decline reason, and sends the right message at the right time. Your team only handles exceptions.
How many retries should I schedule?
There is no single number that suits every business. Spread attempts across several days, retry soft declines, and stop for hard declines. Review your recovery data by decline type and adjust the schedule from there.
What does a dunning tool cost?
Prices vary by model: a share of recovered revenue, a flat fee by MRR tier, or per-message charges. NoChurn uses flat plans, free until $300 MRR, then from $9 up to $399 per month at $500k MRR, with custom pricing above.
Is dunning only for failed card payments?
No. The term also covers reminders for overdue invoices in accounts receivable. For subscription businesses, it mostly refers to failed card or bank charges on recurring plans.