Stripe Dunning Emails: Recover Failed Payments

Failed payments are one of the most overlooked revenue leaks in SaaS. On average, 5–10% of recurring payment attempts fail each month due to expired cards, insufficient funds, or bank declines. Without a recovery process, those customers silently churn — not because they wanted to leave, but because nobody told them their payment failed.

That recovery process is called dunning. This guide walks through everything you need to build an effective Stripe dunning email system: what to send, when to send it, how to write it, and how to measure whether it’s working.

What Are Dunning Emails?

Dunning emails are automated messages sent to customers when their payment fails. The goal is simple: get the customer to update their payment method or resolve the issue before their subscription is canceled. The term “dunning” comes from the centuries-old practice of making persistent demands for payment.

In the Stripe context, dunning typically involves two components working together:

• Automatic retries — Stripe retries the failed charge on a configurable schedule (Smart Retries or custom retry logic).
• Email notifications — messages sent to the customer prompting them to take action, usually by updating their card on file.

For a deeper look at the full recovery workflow beyond just emails, see our Stripe failed payment recovery guide.

Stripe’s Built-In Dunning Tools

Stripe provides several native tools for handling failed payments:

Smart Retries

Stripe’s Smart Retries use machine learning to determine the optimal time to retry a failed payment. Instead of retrying on a fixed schedule, Stripe analyzes patterns across its network to pick the moment most likely to succeed. This is enabled by default for most accounts and recovers a meaningful percentage of failures without any customer interaction.

Stripe-Hosted Emails

Stripe can send basic payment failure emails on your behalf. You can enable these in the Stripe Dashboard under Settings > Subscriptions and emails. These are functional but limited — you can’t customize the content, design, or sending logic.

Customer Portal

The Stripe Customer Portal gives customers a self-service page to update their payment method. Including a link to this portal in your dunning emails makes recovery frictionless.

The Ideal Dunning Email Sequence

A well-structured dunning sequence escalates gradually in urgency. Here’s a proven timing framework:

Email 1: Day 1 — Friendly Heads-Up

Send immediately after the first payment failure. The tone should be helpful, not alarming. Many customers don’t even know their card has expired.

• Subject line: “Quick update needed on your payment method”
• Tone: Casual, helpful. Assume the customer wants to stay.
• Content: Explain what happened (payment failed), what they need to do (update their card), and give them a direct link to do it.
• CTA button: “Update Payment Method”

Email 2: Day 3 — Gentle Reminder

If the first email didn’t result in action, send a follow-up. Mention the specific amount and subscription plan to add context.

• Subject line: “Your [Product Name] subscription needs attention”
• Tone: Still friendly, slightly more direct.
• Content: Remind them of the failed payment, mention the invoice amount, and note that their access will continue while you retry.
• CTA button: “Update Your Card”

Email 3: Day 5 — Urgency Builds

Now introduce a timeline. Let the customer know when their subscription will be affected if the payment isn’t resolved.

• Subject line: “Action required: your subscription will be paused in 48 hours”
• Tone: Direct but empathetic. You’re trying to help them avoid losing access.
• Content: State the deadline clearly. List what they’ll lose access to. Provide the update link prominently.
• CTA button: “Keep My Subscription Active”

Email 4: Day 7 — Final Notice

This is the last email before cancellation. Be clear about the consequence without being threatening.

• Subject line: “Final notice: your [Product Name] subscription”
• Tone: Serious but not punitive. Offer help if they’re having trouble.
• Content: State that the subscription will be canceled today unless payment is updated. Include a support email for customers who need assistance.
• CTA button: “Update Payment Now”

Writing Effective Dunning Emails

The difference between a dunning sequence that recovers 30% of failed payments and one that recovers 60% often comes down to the writing. Here are the principles that matter most:

• Don’t blame the customer. Say “your payment didn’t go through” not “your payment was declined.” Declined feels personal and embarrassing.
• Be specific. Include the amount, the plan name, and the date. Vague emails get ignored.
• One CTA per email. The only action you want is “update payment method.” Don’t distract with product updates or cross-sells.
• Make it easy. The update link should go directly to a payment form — not to a login page, not to a dashboard, not to a settings menu.
• Send from a person. Emails from “Sarah at [Company]” perform better than emails from “noreply@company.com.”

Measuring Recovery Rates

You need to track how well your dunning process is performing. The key metrics are:

• Recovery rate — percentage of failed payments that are eventually collected. A good benchmark is 50–70%.
• Time to recovery — how many days between initial failure and successful payment. Shorter is better.
• Email open rate — if customers aren’t opening your dunning emails, the subject lines or sender name need work.
• Click-through rate — the percentage of recipients who click the update payment link.
• Involuntary churn rate — the percentage of customers lost specifically to payment failures. Track this alongside your overall churn rate to see the impact of dunning improvements.

Beyond Email: In-App and SMS

Email isn’t the only channel for dunning. Consider supplementing your email sequence with:

• In-app banners. When a customer with a failed payment logs in, show a prominent banner with a one-click path to update their card. This is highly effective because the customer is already engaged.
• SMS notifications. For customers who opt in, a brief text message on day 3 or day 5 can cut through inbox noise. Keep it short: “Your payment for [Product] failed. Update your card here: [link]”
• Push notifications. If you have a mobile app, push notifications are another high-visibility channel for payment reminders.

Common Dunning Mistakes

Avoid these pitfalls that reduce recovery rates:

• Waiting too long to start. The first email should go out within hours of the failure, not days. Customers are most likely to act when the issue is fresh.
• Canceling too quickly. Giving customers only 3 days before cancellation is too aggressive. A 7–14 day window with retries is standard.
• Using generic emails. Stripe’s default payment failure emails are better than nothing, but custom emails with your branding and voice perform significantly better.
• Ignoring the data. If your recovery rate is below 40%, something in your sequence isn’t working. A/B test subject lines, sending times, and email copy.

To stay ahead of payment issues, set up cancellation alerts that notify you in real time when subscriptions are at risk, so you can combine automated dunning with manual outreach for your highest-value accounts.

Getting Started

If you don’t have a dunning system yet, start simple. Enable Stripe’s Smart Retries, turn on their built-in email notifications, and track your involuntary churn rate for a month to establish a baseline. Then layer in custom emails, optimize your sequence timing, and expand to additional channels.

The revenue you recover through dunning drops straight to your bottom line — no acquisition cost, no onboarding, no sales cycle. For most SaaS companies, building a proper dunning system is the single highest-ROI project you can do for revenue retention.