Dunning Management: A Playbook to Win Back Failed Payments

Dunning management is the ongoing discipline of recovering failed subscription payments — not just sending a reminder email, but designing, measuring, and continuously improving the whole system that turns declined charges back into paid customers. If you have already read our primer on what dunning is, this is the next step: how to actually run it well.

Plenty of SaaS teams “have dunning” in the sense that Stripe sends a default email when a card fails. Very few treat dunning management as a system worth optimizing, even though it is one of the highest-leverage projects available. This playbook lays out the components, the sequence, the segmentation, and the metrics that separate a 35% recovery rate from a 65% one.

The Four Pillars of Dunning Management

Effective dunning management rests on four pillars that reinforce each other. Weakness in any one caps the performance of the rest.

1. Retry logic

The first line of defense is automated retries. A large share of failures are “soft” — a temporary hold, a momentary lack of funds, a bank hiccup — and clear on a later attempt. Stripe’s Smart Retries choose the timing statistically most likely to succeed rather than a rigid schedule. Get this working first, because every payment retries recovers is one you never have to email about.

2. Customer communication

Hard failures — expired, cancelled, or replaced cards — will never clear on retry. The customer must act. This is where a real email sequence earns its keep. Our Stripe dunning emails guide details the copy and cadence; below we cover how to structure the overall sequence.

3. Frictionless card updates

Every email should link straight to a payment form, not a login page or a settings menu. The Stripe Customer Portal gives customers a hosted page to update their card in seconds. Each extra click between “I want to fix this” and “it is fixed” costs you recoveries.

4. Measurement

Dunning management without measurement is guesswork. You need to know your recovery rate, your involuntary churn rate, and how both move when you change the sequence. We cover the specific metrics later in this playbook.

Designing the Dunning Sequence

A strong sequence escalates gradually over a 7–14 day window. The tone starts casual and grows more direct, but never becomes hostile — remember, most of these customers want to stay.

• Day 0 — Friendly heads-up. Sent within hours of the failure. Assume the customer simply has not noticed. One button: update payment method.
• Day 3 — Gentle reminder. Reference the specific plan and amount. Reassure them that access continues while you retry.
• Day 5 — Introduce a deadline. Tell them exactly when access will be paused if the payment is not resolved.
• Day 7–14 — Final notice. Clear about the consequence, warm about the offer to help. Include a real support address.

Two details matter more than founders expect. First, send from a person (“Sarah at Acme”) rather than a noreply address — it lifts open rates noticeably. Second, never blame the customer: “your payment didn’t go through” lands far better than “your card was declined.”

Segmenting Your Dunning Management

A flat, one-size-fits-all sequence leaves money on the table. Mature dunning management segments customers and treats them differently.

• By value. A $2,000/month enterprise account deserves a personal email from a human, maybe even a phone call. A $12/month self-serve user gets the automated sequence. Trigger manual outreach for high-value accounts using cancellation alerts.
• By failure type. An expired card needs a “please update” message; a temporary insufficient-funds decline might just need a well-timed retry and a lighter touch.
• By tenure. A three-year customer and a first-week trial converter warrant different tones. The loyal customer has earned patience and warmth.

Segmentation is where dunning management shifts from “a sequence” to “a strategy.” It reduces the risk of annoying good customers while concentrating human effort where the revenue is.

The Metrics That Prove It Is Working

You cannot manage what you cannot see. Track these five numbers continuously:

• Recovery rate. The share of failed payments eventually collected. Aim for 50–70%. This is the headline number.
• Involuntary churn rate. Customers lost purely to payment failures. Watch it as a distinct line from voluntary churn — see our breakdown of involuntary churn.
• Time to recovery. Days between the first failure and successful payment. Shorter means less revenue at risk and less customer confusion.
• Email open and click rates. Weak opens point to subject lines or sender name; weak clicks point to the copy or the call to action.
• Recovered MRR. The dollar impact. This is the figure to put in front of your board.

Recovery rate = Failed payments recovered ÷ Total failed payments

A recovery rate below 40% almost always means something in the sequence is broken — often emails going out too late, or an update link that dumps customers on a login screen. Because failed payments feed directly into your overall churn, improving recovery shows up in your churn rate tracking within a month or two.

Common Dunning Management Mistakes

• Starting too late. The first email should go out within hours, while the issue is fresh and the customer is most likely to act.
• Cancelling too fast. A 3-day window cuts off customers who would have paid on day 5. Give retries and emails room to work.
• Relying only on default emails. Stripe’s built-in emails are a floor, not a ceiling. Branded, human copy dramatically outperforms them.
• Treating every customer the same. No segmentation means either annoying small accounts or under-serving big ones.
• Never looking at the data. If nobody owns the recovery rate, it will quietly drift down and no one will notice until MRR does.

Where StripeReport Helps

StripeReport is not a billing platform — Stripe remains your engine for charges, retries, and the customer portal. What StripeReport adds is the visibility layer that dunning management depends on. Connect a read-only Stripe key and you get recovery rate, involuntary churn, and recovered MRR tracked automatically, pushed to your inbox and Slack every day. Instead of discovering a failed-payment spike at month-end close, you see it the morning it starts — which is exactly when a personal email to a big account still makes a difference.

Building a Dunning Management Cadence

Dunning management is not a set-it-and-forget-it project. The teams with the best recovery rates treat it as a recurring review, not a one-time build. A simple operating cadence keeps it healthy:

• Weekly. Scan for high-value accounts currently in the dunning window and decide which deserve a personal touch this week.
• Monthly. Review recovery rate and involuntary churn against the prior month. If recovery dipped, look at whether email timing, deliverability, or the update link changed.
• Quarterly. Run an A/B test on one variable — a subject line, a send time, the number of emails, or the length of the window — and keep what wins.

This rhythm turns dunning from a static workflow into a compounding one. Small, repeated improvements to a process that touches every failed payment add up to meaningful recovered MRR over a year.

Key Takeaways

• Dunning management is the ongoing discipline of recovering failed payments, built on retries, communication, frictionless card updates, and measurement.
• Design an escalating 7–14 day email sequence that starts friendly, sets a clear deadline, and never blames the customer.
• Segment by account value, failure type, and tenure so human effort goes where the revenue is.
• Track recovery rate, involuntary churn, time to recovery, email engagement, and recovered MRR — a recovery rate under 40% signals a broken sequence.
• Keep Stripe as the billing engine and use a reporting layer to prove the dunning system is actually working.