SaaS Dunning: The Complete Guide to Recovering Failed Payments

TL;DR: Dunning is the process of recovering failed subscription payments by sending automated emails that prompt customers to update their payment method. Failed payments cause 20-40% of all SaaS churn, making dunning one of the highest-ROI retention activities. An effective dunning strategy uses a 3-email sequence over 7-14 days and typically recovers 30-50% of failed payments.

What is Dunning?

Dunning is the process of communicating with customers whose subscription payments have failed and prompting them to update their payment information. The term originates from the 17th-century verb "to dun," meaning to make persistent demands for payment. In the SaaS context, dunning is specifically about involuntary churn — customers who did not intend to cancel but whose subscriptions lapse because of a failed credit card charge.

Why Failed Payments Happen

Payment failures are rarely the customer's fault, and they almost never indicate intent to cancel. The most common causes are:

• Expired credit cards — Cards expire every 3-4 years. At any given time, a percentage of your customer base has cards approaching expiration.
• Insufficient funds — Temporary balance issues, particularly around billing dates that coincide with other large charges.
• Card issuer declines — Banks flag unusual charges, apply fraud filters, or impose temporary holds.
• Outdated billing information — Customers change banks, get new card numbers after a fraud incident, or move and forget to update addresses.
• Payment processor errors — Temporary issues with Stripe, the card network, or the issuing bank. The critical insight is that these customers still want your product. They just need to know their payment failed and an easy way to fix it.

The 3-Email Dunning Sequence

The most effective dunning strategies use a carefully timed email sequence with escalating urgency:

Email 1: The Friendly Reminder (24 hours after failure)

Tone: Helpful, not alarming Subject line: "Your payment didn't go through — quick update needed" Content: Let the customer know their payment failed, explain it's likely a card issue, and provide a direct link to update their payment method via Stripe's billing portal.

Email 2: The Nudge (72 hours after failure)

Tone: Slightly more urgent Subject line: "Action required: your payment is still failing" Content: Remind them this is their second notice. Emphasize that their subscription access may be affected. Include the same payment update link.

Email 3: The Final Notice (7 days after failure)

Tone: Direct and final Subject line: "Final notice: your subscription will be cancelled" Content: Let them know this is the last email before their subscription is cancelled. Create urgency without being aggressive. Include the payment update link one more time.

Dunning Email Best Practices

| Best Practice | Why It Matters | |---|---| | Include a direct payment update link | Reduces friction from 5+ clicks to 1 click | | Send from a recognizable address | noreply@yourdomain.com, not a random transactional service | | Keep the email short | Failed payment emails should be under 100 words | | Show the amount due | "Your payment of $49.00 failed" is clearer than "payment issue" | | Do not include marketing content | This is a service email, not a promotion | | Test your links | A broken payment update link means a lost customer |

Dunning Recovery Rates

Realistic recovery rates by email in the sequence: | Email | Timing | Typical Recovery Rate | |---|---|---| | Email 1 (Reminder) | 24 hours | 15-25% | | Email 2 (Nudge) | 72 hours | 10-15% | | Email 3 (Final) | 7 days | 5-10% | | Total | | 30-50% | Most recoveries happen after the first email. The second and third emails catch customers who missed the first one or needed time to find their new card.

Setting Up Dunning

DIY Approach

You can build dunning yourself using Stripe's webhook events. Listen for invoice.payment_failed, store the failed invoice details, and trigger an email sequence using a transactional email provider like Resend or Postmark. You will also need to handle retries, track email sends, and clean up when payment is recovered. Development time: 1-3 weeks, plus ongoing maintenance for edge cases.

Using a Dunning Tool

Tools like ChurnBack handle the full dunning pipeline: webhook reception, case creation, email sequencing, payment portal links, and automatic case closure when payment succeeds. Setup takes minutes because the tool connects to your Stripe account via OAuth. ChurnBack combines dunning with cancel flow management in a single platform, giving you both voluntary and involuntary churn recovery. Get started →

FAQ

What is dunning in SaaS?

Dunning is the automated process of contacting customers whose subscription payments have failed and prompting them to update their payment method. It prevents involuntary churn — customers who leave not by choice but because of a payment issue.

How many dunning emails should I send?

Three emails is the standard. Send the first 24 hours after the failure, the second at 72 hours, and a final notice at 7 days. More than three emails typically has diminishing returns and risks annoying the customer.

What is a good dunning recovery rate?

A good dunning recovery rate is 30-50% of failed payments recovered. Most of the recovery happens after the first email (15-25%), with the second and third emails catching additional customers.

Should I cancel the subscription after dunning fails?

Yes, but give it time. Most companies wait 14 days after the initial failure before cancelling. This gives all three emails time to be sent and gives the customer time to act. Some companies extend this to 21 or 30 days.

What is the difference between dunning and a cancel flow?

Dunning addresses involuntary churn (failed payments) through email sequences. Cancel flows address voluntary churn (active cancellation) through in-app retention offers. Both are components of a complete churn recovery strategy.