Dunning Email Best Practices for Stripe: A 3-Step Sequence That Works

A customer's payment fails. You have about seven days to recover it before they're gone forever. The difference between losing that customer and keeping them usually comes down to three emails — the right message, at the right time, with the right tone.

This guide covers the full dunning email playbook for Stripe: what dunning emails are, the exact three-email sequence that recovers the most failed payments, subject line formulas that get opens, tone shifts that move people to action, and example copy you can adapt for your own product. We'll also cover how dunning emails work alongside smart retries — because the best recovery systems use both.

What Are Dunning Emails?

Dunning emails are automated messages sent to customers whose payments have failed, asking them to update their payment information. The term "dunning" comes from the verb "to dun" — to make persistent demands for payment. The word sounds aggressive, but good dunning emails are the opposite: they're helpful, clear, and empathetic.

The purpose of a dunning email isn't to demand payment. It's to solve a problem for the customer. Most of the time, the customer doesn't even know their payment failed. Their card expired, their bank flagged the charge, or they temporarily ran low on funds. They still want your product. They just need to update their payment method, and your dunning email makes that easy.

The mindset shift: Think of dunning emails as customer service, not debt collection. You're helping someone maintain access to something they've already chosen to pay for. The tone should reflect that.

Why Three Emails? The Escalation Framework

One email isn't enough. Data from payment recovery systems consistently shows that a multi-email sequence outperforms a single notification by 40-60%. The reason is simple: people are busy, they miss emails, and urgency increases action.

Three emails is the sweet spot. Fewer than three and you're leaving recoveries on the table. More than three and you risk annoying the customer — which actually decreases recovery rates because people unsubscribe or mark you as spam.

The three emails follow an escalation arc:

1. Email 1 (Day 0): Friendly notification — "this happened, here's how to fix it"
2. Email 2 (Day 3): Direct reminder — "we still need your updated info"
3. Email 3 (Day 7): Final warning — "your account will be paused/cancelled"

Each email shifts in tone, specificity, and urgency. Let's walk through each one in detail.

Email 1: The Friendly Heads-Up (Day 0)

This email goes out the same day the payment fails — ideally within an hour. The customer's experience is seamless: their payment failed, and they get an immediate, helpful notification. No disruption, no panic.

Tone

Warm and reassuring. The customer did nothing wrong. A payment failed — it happens to everyone. Your job is to inform them and make fixing it effortless.

What to Include

• What happened (their payment for [Product Name] didn't go through)
• Which card was affected (last four digits — e.g., "your Visa ending in 4242")
• Reassurance that their account is still active (if it is)
• A single, prominent button to update their payment method
• A note that you'll retry the charge automatically

Subject Line Options

• "Quick heads up about your [Product] payment"
• "Your recent payment didn't go through"
• "[Product]: Action needed on your account"
• "Heads up — we couldn't process your payment"

Example Copy

Notice what this email doesn't do: it doesn't use alarming language ("PAYMENT FAILED"), doesn't threaten account cancellation, and doesn't apologize excessively. It treats the situation as routine — because it is.

Email 2: The Clear Reminder (Day 3)

Three days have passed. You've already attempted one or two automatic retries. The payment still hasn't gone through. Now it's time to be more direct.

Tone

Helpful but direct. Less "just a heads up" and more "you need to take action." Still friendly — not demanding.

What to Include

• A reminder of what's happening (payment still hasn't been processed)
• What the customer stands to lose (be specific — name features, not just "your account")
• A clear deadline or timeframe ("we'll try one more time in the next few days")
• The update payment button — even more prominent than email 1
• An offer to help if they're having trouble

Subject Line Options

• "Action needed: Update your payment for [Product]"
• "Your [Product] payment is still pending"
• "Don't lose access to [Product] — update your card"
• "Reminder: Your payment for [Product] needs attention"

Example Copy

The key difference from Email 1: this email names what the customer will lose. "Your saved dashboards, custom reports, and team integrations" is far more motivating than "your account." People don't care about accounts. They care about the work and data inside them.

Email 3: The Final Notice (Day 7)

This is the last email before the subscription is cancelled or paused. It needs to communicate urgency without crossing into aggressive territory. The tone should feel like a friend giving a final warning, not a collections agency.

Tone

Urgent and clear. There's a specific deadline. The consequences are stated plainly. But the underlying message is still "we want to keep you as a customer."

What to Include

• A specific deadline ("your subscription will be cancelled on [date]")
• What will happen to their account and data
• The update payment button — largest and most prominent of all three emails
• A line expressing that you'd genuinely like to keep them
• Contact information if they need help

Subject Line Options

• "Your [Product] subscription will be cancelled tomorrow"
• "Final notice: Update your payment to keep [Product]"
• "We don't want to lose you — please update your card"
• "Last chance to keep your [Product] account active"

Example Copy

This email works because it is specific and honest. "Your dashboards and saved reports will no longer be accessible" creates more urgency than "your account will be cancelled" because it connects the consequence to something the customer values.

Timing the Sequence: Day 0, Day 3, Day 7

The 0-3-7 timing isn't arbitrary. Here's the logic behind each interval:

Day 0 (Immediate)

Send within one hour of the failed payment. The customer is most likely to take action immediately after being notified. Open rates for day-0 dunning emails average 50-65% — significantly higher than marketing email benchmarks. This is because the email is relevant, time-sensitive, and personally addressed.

Day 3 (First Follow-Up)

By day 3, two things have happened: the first email may have been missed or ignored, and your automatic retry system has had time to attempt one or two retries. If the retries succeeded, you don't send Email 2 (this is important — always check payment status before sending). If the retries failed, Email 2 goes out. The 3-day gap also aligns roughly with weekly pay cycles, so customers who were short on funds may now have money in their account.

Day 7 (Final Warning)

Seven days is the standard grace period for most SaaS products. It's long enough to give the customer reasonable time, and short enough that you're not hemorrhaging free service. The final email goes out 24-48 hours before actual cancellation, giving the customer one last window to act.

Subject Lines That Get Opens

Dunning email subject lines need to do two things: get opened, and set the right expectation. Here are the patterns that consistently perform best:

High-Performing Patterns

Patterns to Avoid

• "PAYMENT FAILED" (all caps) — Triggers spam filters and creates anxiety instead of action
• "Billing issue with your account" — Too vague; sounds like a phishing email
• "You owe $49.00" — Debt collection framing; puts customers on the defensive
• No product name — Customers with multiple subscriptions won't know which one this is about

The Update-Payment-Method Link

Every dunning email has one primary call to action: update the payment method. The link needs to go directly to a page where the customer can enter new card details. Any extra steps — login screens, navigation, confirmation pages — reduce conversion.

Best Practices for the Update Link

• Use Stripe's Customer Portal. Stripe offers a hosted billing page (billing_portal) that lets customers update their payment method without logging into your app. Use it. It's faster to implement than a custom page and it's PCI-compliant by default.
• Pre-authenticate the link. Include a time-limited token in the URL so the customer doesn't need to log in. Having to remember a password adds friction that kills conversion — especially for a customer who might not have logged in recently.
• Make the button obvious. Use a large, high-contrast button. In plain-text email fallbacks, use a short, clean URL. The button should be visible without scrolling on mobile devices.
• One button per email. Don't include multiple CTAs. Every additional link dilutes the primary action. The email has one job: get the customer to update their card.

Conversion data: Dunning emails with pre-authenticated, direct-to-billing links see 25-40% higher click-through rates than emails that require the customer to log in first. Remove every barrier between "I should update my card" and "my card is updated."

Combining Dunning Emails with Smart Retries

Dunning emails and automatic retries are complementary, not competing strategies. Retries attempt to process the existing payment method silently. Dunning emails ask the customer to provide a new one. Together, they cover both scenarios: the card that works on the second try, and the card that needs to be replaced.

The Combined Timeline

Critical rule: always check payment status before sending the next dunning email. If a retry succeeded on day 2, you don't want to send Email 2 on day 3 asking the customer to update their card — that's confusing and makes you look careless. Your dunning system needs to be aware of retry outcomes in real-time.

Why Decline Code Matters for Email Content

The most sophisticated dunning systems customize email content based on the decline code. Here's why:

• insufficient_funds: Don't mention the decline reason explicitly (it's sensitive). Just say the payment didn't go through and that you'll retry. There's a good chance the retry will succeed, so keep the tone relaxed.
• expired_card: Mention that the card on file has expired and they need to provide a new one. This is actionable, non-embarrassing information.
• generic_decline: Keep it vague — "your bank declined the charge." Suggest they try a different card or contact their bank.
• stolen_card / lost_card: Be especially careful. Don't mention the reason. Simply say the payment couldn't be processed and offer a link to update their method.

Measuring Dunning Email Performance

Track these four metrics to know if your dunning sequence is working:

1. Open rate by email position. Email 1 should be 50%+, Email 2 should be 40%+, Email 3 should be 35%+. If Email 1 is below 40%, your subject line or sender name needs work.
2. Click-through rate (CTR) on the update link. Target 15-25% CTR for Email 1, 10-20% for Email 2, 15-25% for Email 3 (the deadline creates urgency). If CTR is low but open rate is high, your email copy or button placement needs optimization.
3. Recovery rate by email. Track which email drove the recovery. If Email 1 is recovering most customers but Email 3 recovers almost none, consider shortening the sequence or making Email 2 more urgent.
4. Overall dunning recovery rate. Of all customers who entered the dunning sequence, what percentage recovered? A good target is 25-40% recovery from dunning emails alone (on top of what retries recover).

Common Mistakes That Kill Recovery Rates

These patterns consistently reduce dunning email effectiveness:

• Sending from a no-reply address. Customers who reply to dunning emails with questions or issues represent a significant recovery opportunity. If they can't reply, you lose them. Use a monitored email address.
• Burying the CTA. The update payment button should be above the fold — visible without scrolling, especially on mobile. Long preambles before the button reduce clicks.
• Generic messaging. "Your account has a billing issue" is less effective than "Your $49/month Acme Analytics subscription payment failed." Specificity builds trust and urgency.
• Too many emails. Four or more dunning emails show diminishing returns. After the third email, additional messages are more likely to generate spam complaints than recoveries.
• Not stopping when recovered. Sending a dunning email after the payment has already been recovered is one of the fastest ways to frustrate a customer. Integrate your dunning system with your payment status in real-time.
• Same tone throughout. If all three emails sound the same, customers who ignored Email 1 will ignore Emails 2 and 3. The tone must escalate — friendly, then direct, then urgent.

How RecoverStripe Handles Dunning Automatically

RecoverStripe runs this entire dunning sequence automatically when you connect your Stripe account. It sends the 3-email sequence with timing and content optimized by decline code, checks payment status before every email to avoid sending after recovery, pre-authenticates the update link so customers don't need to log in, and tracks recovery metrics per email so you can see exactly which messages are driving results.

The emails are sent from your domain and can be customized with your brand. Setup takes under two minutes — connect Stripe, and the dunning sequence is live.

Key Takeaways

Dunning emails are one of the highest-ROI things you can implement for your SaaS business. Here's the summary:

• Send three emails: Day 0 (friendly), Day 3 (direct), Day 7 (urgent). Each email escalates in tone and specificity.
• Always include the product name in the subject line. Include the card's last four digits in the body.
• One CTA per email: Update payment method. Make it a big, obvious button with a pre-authenticated link.
• Name what they'll lose — specific features, data, and workflows, not just "your account."
• Combine with smart retries. Retries recover the cards that just need a second chance. Dunning recovers the cards that need to be replaced.
• Always check status before sending. Never send a dunning email for an already-recovered payment.
• Measure per-email performance. Track open rate, CTR, and recovery rate for each email in the sequence.

The SaaS companies that take dunning seriously recover 25-40% of failed payments through email alone. Combined with smart retries, total recovery rates of 50-70% are realistic. That's revenue that was already earned — customers who already said yes. All you're doing is keeping the door open for them.