Resources

What Is Dunning? Definition, Process, and Examples

Dunning is the process of retrying a failed payment and reminding the customer to fix it, so a subscription that would have been lost by accident gets paid and stays active.

That is the whole idea. The rest unpacks it plainly: why payments fail, what happens step by step, and what a real sequence looks like day by day.

If you run anything people subscribe to — software, a membership, a box, a newsletter, a service billed monthly — dunning matters because many subscribers you lose never decided to leave. Their card expired. Their bank blocked the charge. There was not enough money in the account on the morning the renewal ran. The payment failed, nobody fixed it in time, and the account was cancelled. That loss is called involuntary churn, and Recurly estimates 20–40% of subscriber churn is involuntary, according to Recurly research. Dunning is the work between the failed payment and that cancellation.

Where the word comes from

To dun someone, in older English, meant to press them persistently for money they owed — to keep asking until the bill was paid. Modern dunning kept the persistence and dropped the pressure. Nobody sends an angry letter because a card declined. Today the process is mostly automatic, polite, and practical: try the payment again at a smarter time, tell the customer clearly what happened, and give them an easy way to update their card. The goal is not to chase a debt. It is to fix a small problem before it quietly ends a subscription the customer still wants.

Why payments fail

A renewal is a quiet transaction. There is no checkout and no customer present to notice a problem. The system tries to charge the card on file, and the bank says no. Banks say no for many reasons, and the reason matters, because it decides what should happen next.

The most common reason is not having enough money available at that moment. Across 5.4M failed payments, insufficient funds is the largest decline category at 40.6%, according to Churnkey's published analysis of Stripe data. That failure is often temporary — the account may look different after payday. Other common reasons include an expired card, a replaced card, a bank flagging an unfamiliar charge, or a processing error. Some failures are different in kind: a stolen card, a closed account, or a bank instruction not to try again. Those are hard declines, and retrying them will not help. Good dunning treats each type differently.

The dunning process, step by step

1. A payment fails and the reason is recorded. The charge is declined and the decline code is saved. Nothing is lost yet — the customer is usually still in a grace period and still has access.
2. The system reads the reason before it acts. An expired card needs a new card. A temporary lack of funds needs time. A hard decline needs to stop. Reading the reason prevents wasted retries — and hammering a card that should never be charged again.
3. The payment is retried at a better moment. A smart retry waits until success is more likely — for example, after a likely payday. Swipe Again, for instance, makes up to 6 attempts over about 16 days, and never retries hard declines.
4. The customer is told, clearly and early. A short email explains: your payment did not go through, your subscription is still active for now, here is how to fix it. Each additional dunning email touch adds roughly 1–2 points of recovery, according to Churnkey's published analysis of Stripe data, which is why one email is rarely the whole sequence.
5. The customer gets an easy way to fix the card. The email links to a branded card-update page where they can enter a new card in under a minute. Most recoveries that need a new card happen here.
6. Reminders escalate, then it ends cleanly. Later touches follow — often including a text message, because texts get seen when emails do not. The message gets more direct: access will pause on a specific date. If nothing works, the subscription is cancelled at the end of the grace period, with a final notice.

Retries handle failures that fix themselves with time. Reminders and the card-update page handle failures that need the customer. The grace period holds the two together. For the operational version — who owns each step and how to improve it — see our dunning management guide.

A worked example: day by day

Here is a typical sequence for a fictional subscriber. Maya pays $29 a month for a membership she uses every week. She wants to stay. Her bank has sent her a replacement card, and the number on file no longer works.

• Day 0 — the payment fails. The renewal is declined, the system records the reason, keeps Maya's access on, and starts her grace period. Maya sees nothing yet.
• Day 0 to Day 1 — a first smart retry. If the failure looked like a passing error, the system may try once more quickly. In Maya's case the card itself is the problem, so it moves to telling her.
• Day 1 — the first email. A short email from the business she knows: her $29 payment did not go through, her membership is still active, and she can update her card with one link. Many customers fix it right here.
• Day 3 to Day 5 — another retry and a second reminder. A further retry may run where timing helps. A second email uses firmer wording and repeats the link. People miss emails; a payment problem is easy to postpone.
• Day 7 to Day 9 — a text message. A short SMS: your payment needs attention, here is the link, your access pauses soon. This is often the touch that finally reaches the customer.
• Day 10 to Day 14 — Maya fixes it. She taps the link, lands on a branded page, enters her new card in under a minute. The next retry succeeds and her subscription continues — no support call, no embarrassment.
• Day 16 — the final notice, if nothing worked. If Maya never responds, a final notice says the subscription has been paused or cancelled and explains how to restart. No further retries run.

Maya was never threatened, never charged a penalty, and never retried dozens of times. The sequence gave a temporary problem several calm chances to resolve. For the words themselves, see our dunning email templates and our guide to dunning emails that work.

Dunning is not collections

Collections is what happens when someone owes money, knows it, and is not paying — a disputed bill or a debt handed to an agency. Dunning is what happens when a willing subscriber's automatic payment fails by accident and needs to be retried or updated. The customer in dunning usually wants to pay; the mechanism broke. Treating them like a debtor damages trust and recovers less. We break the difference down in dunning vs collections.

What good dunning looks like

• It acts on the reason, not just the failure. Different declines get different timing and messages, and hard declines are never retried.
• It starts fast and stays calm. The first reminder goes out while the problem is fresh, and the tone is helpful from first touch to last.
• It makes fixing the card effortless. One link, one simple branded page, no login maze.
• It uses more than one channel. Email does most of the work; a text message catches the people email misses.
• It knows when to stop. A clear end: a final notice, access paused or the subscription cancelled, and no endless retrying.
• It can be measured. You should see how many payments failed, how many were recovered, and which step recovered them.

Bad dunning is the mirror image: the same generic email five times, retries at random, a confusing card-update page, and a customer who learns of the problem only when access suddenly stops — and often does not come back.

Do you need dunning software?

Every billing platform does a little of this on its own — a few retries and sometimes a basic reminder email. For a very small business, that plus a personal follow-up may be enough. Once failures are a weekly event, doing it by hand stops working. That is where dedicated dunning software earns its place, running the sequence the same way every time, at any hour.

Swipe Again is one example, built for subscription businesses: decline-code-aware smart retries — up to 6 attempts over about 16 days, hard declines never retried — branded dunning emails and card-update pages, SMS in the sequence, and cancel deflection offers included. It is $179/mo flat, with no percentage of recovered revenue, connects in about 2 minutes, and starts with a 14-day trial, card upfront. On connect it also works your existing 90-day backlog of failed payments. Its guarantee is: "Recover $179 in 30 days, guaranteed — or Swipe Again is free the next 30 days". Judge any tool against the checklist above, not against promises.

The bottom line

Dunning is simply the organised attempt to save subscriptions failing by accident: retry intelligently, tell the customer plainly, make the fix easy, and stop cleanly if it cannot be saved. Most subscribers caught by a failed payment are not trying to leave. A calm, well-timed sequence gives them the chance to stay — and gives your business revenue it had already earned.

Frequently asked questions

What does dunning mean in simple terms?

Dunning means the retries and reminders after a subscription payment fails. The business tries the card again at sensible times, tells the customer what happened, and gives them an easy way to update their card, so the subscription continues instead of being cancelled by accident.

How long does a dunning sequence usually last?

About two weeks — long enough to cover a payday cycle and several reminders without dragging on. One common shape is up to 6 retry attempts over about 16 days, alongside emails and a text message, ending with a final notice if nothing succeeds.

Is dunning the same as debt collection?

No. Collections deals with money owed and not being paid, often after a dispute or a long overdue period. Dunning deals with a willing subscriber whose automatic payment failed by accident, for example because a card expired. The tone, tools, and goal are different.

What happens if dunning does not work?

If every retry fails and the customer never updates their card, the subscription is normally paused or cancelled at the end of the grace period. A good sequence ends with a clear final notice explaining what happened and how to restart.

Why not just retry the card every day until it works?

Because the reason decides whether a retry can help. Retrying a temporary problem at the right moment can succeed, but retrying an expired card changes nothing, and retrying a hard decline — a stolen or closed card — will never succeed and can harm your standing with payment networks.