What dunning does and why it matters

Dunning is the process of automatically retrying a failed payment and notifying the customer that something went wrong. Instead of letting a payment failure sit and watching the customer churn, dunning systems catch the problem, try again on a schedule, and send reminders. The goal is straightforward: recover the payment before the customer cancels out of frustration or because they forgot the charge was pending.

A failed payment doesn't mean the customer wants to leave. It usually means their card expired, they hit a temporary limit, they switched banks, or the payment processor had a glitch. Dunning gives you a second, third, or fourth chance to collect before the relationship ends. Without it, you lose recurring revenue customers over something that wasn't their fault.

The churn reduction comes from two places: recovering payments that would otherwise be lost, and keeping the customer experience smooth enough that they don't cancel in anger or embarrassment.

Key Takeaways

  • Dunning retries failed payments on a schedule—typically 3 to 5 attempts over 7 to 14 days—rather than giving up after the first failure.
  • Each retry attempt should be spaced days apart and paired with a notification, so the customer has time to fix the problem and knows what happened.
  • Dunning reduces churn by recovering 20 to 40 percent of failed payments that would otherwise be lost, depending on your customer base and retry schedule.
  • The notification itself matters as much as the retry: customers who know about the failure are less likely to cancel than those who discover it later.
  • Dunning works best when combined with a way for customers to update their payment method themselves, rather than forcing them to contact support.

How the retry schedule affects recovery and churn

The timing of your retries directly shapes how many payments you recover. A common pattern is: first retry 3 days after the initial failure, second retry 5 days later, third retry 2 days after that. Some systems add a fourth or fifth attempt, but the law of diminishing returns kicks in—each additional retry recovers fewer payments and risks annoying the customer.

The spacing matters because it gives the customer time to notice the notification, fix the underlying problem (update their card, move money into their account), and have the retry succeed. A retry that happens the same day as the failure, before the customer has even seen the notification, wastes an attempt. A retry that happens 30 days later, after the customer has already decided to cancel, comes too late.

The total window—from first failure to final retry—typically runs 7 to 14 days. Longer windows recover more payments but also delay the moment you know whether the customer is staying or leaving. Shorter windows get you an answer faster but leave money on the table. Most subscription and SaaS businesses land somewhere in the middle: 10 to 12 days total, with 3 to 4 retry attempts.

Why notification is as important as the retry itself

A retry without a notification is a silent failure. The customer doesn't know their payment failed, doesn't know you're trying again, and doesn't know they need to update their card. When the final retry fails and you suspend their service, they're confused and frustrated—and they churn.

A notification—sent by email, SMS, or in-app message—tells the customer what happened, why it happened, and what they can do about it. The best notifications include a direct link to update their payment method, so the customer can fix it in 30 seconds without calling support. This self-service path is critical: customers who can update their card themselves are far more likely to stay than those who have to open a support ticket.

The tone of the notification matters too. A message that sounds like a bill collector ("Your payment has failed. Update when ready or your service will be suspended.") triggers defensiveness and cancellations. A message that sounds like a helpful reminder ("We tried to charge your card on [date], but it was declined. This usually means your card expired or hit a limit. You can update it here: [link]. We'll try again on [date].") keeps the relationship intact.

What percentage of failed payments dunning actually recovers

The recovery rate depends on your customer base, your notification quality, and your retry schedule. Across subscription businesses, dunning typically recovers 20 to 40 percent of failed payments. Some businesses see higher rates—50 percent or more—if their customers are engaged and responsive. Others see lower rates if their customer base is less attentive or if the underlying failure was intentional (a customer testing whether you'd notice a bad card, or quietly trying to cancel).

The first retry usually recovers the most—often 50 to 60 percent of the recoverable payments. The second retry picks up another 20 to 30 percent. By the third or fourth retry, you're recovering single-digit percentages. This is why most systems stop at 3 or 4 attempts: the cost of the retry (payment processor fees, customer support load, risk of annoying the customer) outweighs the revenue recovered.

For a business with 1,000 monthly recurring customers and a 5 percent monthly failure rate (50 failed payments), dunning might recover 10 to 20 of those payments. That's 10 to 20 customers who stay instead of churn—which compounds month after month. Over a year, that's 120 to 240 customer-months of retained revenue.

How dunning fits into your broader payment strategy

Dunning is one piece of a payment retention system, not the whole thing. It works best alongside other tools: a clear billing calendar so customers know when charges are coming, the ability to update payment methods without contacting support, and a grace period before you suspend service (usually 7 to 14 days after the final retry fails).

Some businesses also use soft declines—a retry logic that catches certain types of failures (like temporary limits) and retries them when ready, before sending a notification. Others use payment method tokenization, which stores the customer's card securely so they don't have to re-enter it every time. These are complementary to dunning, not replacements for it.

The goal across all of these is the same: make it as straightforward as possible for the customer to stay, and as hard as possible for them to accidentally churn over a payment problem that wasn't really their fault.

Common mistakes that undermine dunning effectiveness

The most common mistake is too few retries or too short a window. A single retry 1 day after the failure recovers almost nothing, because the customer hasn't had time to notice or fix the problem. A 3-day window is also too short for most customers. You need at least 7 to 10 days and at least 3 retries to see meaningful recovery.

The second mistake is notifications that don't include a way to update the payment method. If your email says "Your payment failed" but doesn't include a link to fix it, you've told the customer about the problem without giving them a path to solve it. They have to hunt through your website or call support, and many will just cancel instead.

The third mistake is retrying too aggressively—multiple times per day, or continuing to retry after the customer has explicitly cancelled. This triggers fraud alerts, violates payment processor rules, and damages your reputation. Stick to the schedule, respect the customer's cancellation request, and let the process run its course.

Frequently Asked Questions

Does dunning work for one-time purchases, or only subscriptions?

Dunning works best for subscriptions and recurring charges, where the customer expects regular billing and a failed payment is usually a mistake. For one-time purchases, a single retry 2 to 3 days later can recover some failed orders, but the window is shorter and the recovery rate is lower. Most one-time purchase businesses focus on preventing failures in the first place (asking for confirmation, offering multiple payment methods) rather than retrying.

What happens if a customer's payment fails after I've already sent them a notification?

Send another notification for the retry attempt. Each notification should include the new retry date, so the customer knows when to expect the next charge. If you're on retry 3 of 4, say so—it helps the customer understand the urgency without sounding like a threat. Keep the tone consistent: helpful, not punitive.

Can I retry a payment without the customer's permission?

Yes, within limits. Payment processors and card networks allow retry attempts on failed charges, and most customer agreements include language permitting this. However, you must notify the customer, and you must respect their explicit cancellation request. If a customer tells you to stop trying, you stop. If they just haven't responded to a notification, you can retry.

What's the difference between dunning and collections?

Dunning is automated, happens within days, and focuses on technical failures and honest mistakes. Collections is manual, happens weeks or months later, and focuses on customers who are deliberately avoiding payment. Dunning is customer-friendly; collections is adversarial. Most businesses never need collections if dunning is working well.

Should I charge a fee if a payment fails?

No. Charging a fee for a failed payment—even a small one—increases churn and damages trust. The customer didn't fail on purpose; their card expired or they hit a limit. A fee feels like punishment. Instead, focus on making the retry and notification process smooth. If the customer eventually cancels after multiple failed retries, that's different—but don't penalize the first failure.