Updated June 2026 · Templates included

Dunning Email Best Practices

Q: How many emails should a dunning sequence have?

Three to four core emails: Day 1 (within an hour of failure), Day 3, and Day 7, plus optional escalation after day 7. A single email recovers ~15%; a 3-4 email sequence recovers 35-45%. More than four rarely adds much and risks annoying customers.

Q: How soon should I send the first dunning email?

Within 60 minutes of the failure. Recovery decays fast: a same-day email opens at ~41% versus ~27% after a month. Waiting 24 hours costs roughly 15% of recovery. Speed is the single biggest lever you control.

Q: What's the difference between a generic and a failure-specific dunning email?

A generic email says 'your payment failed' to everyone. A failure-specific email matches the decline code: a card-update link for expired cards, a no-shame retry note for insufficient funds, a bank-call script for do_not_honor. Segmenting by failure reason adds 15-25% to recovery.

Q: Should dunning emails be plain text or HTML?

Plain or lightly styled text usually wins for dunning. It looks personal, lands in the inbox more reliably, and renders everywhere. Heavy HTML templates can trip spam filters and feel like marketing. Keep one clear button, minimal images, and your real branding light.

Q: Why should the sequence stop when payment succeeds?

Because emailing 'your payment failed' to someone who already paid destroys trust and floods support. A good system checks payment status before every send and halts the sequence the moment the charge clears, whether via retry, card update, or a delayed bank settlement.

Q: Do dunning emails hurt my sender reputation?

Not if done right. Dunning is transactional and expected, with high open rates that actually help reputation. Risk comes from sending to invalid addresses, heavy HTML, or an unauthenticated domain. Authenticate with SPF/DKIM/DMARC, keep volume clean, and stop on success.

Q: Is it worth automating dunning emails?

Almost always. Manual dunning fails on timing and consistency, the two things that matter most, and breaks entirely at volume. A tool sends within minutes, branches by decline code, stops on success, and sends from your domain. SubRevival does all of it from $19/mo flat.

Q: What open rate should I expect from dunning emails?

Dunning emails open at 40-60%, far above the ~20% typical of marketing email, because they're urgent and expected. Same-day sends hit ~41%; opens fall as the email ages. Personalizing the subject with a first name adds 10-15%.

Generic dunning recovers 25-35%. Failure-specific sequences recover 45-60%. This is the deepest dunning email guide on the web: per-decline-code templates, full Day 1/3/7 copy, timing data, and deliverability rules.

Automate My SequencesBy the SubRevival team · 18 min read

On this page

01Why generic dunning fails 02Old way vs new way 03Decline code reference 04Pre-dunning templates 05The Day 1/3/7 core 06Failure-specific copy 07Escalation after Day 7 08Response-time decay 09Deliverability rules 10Subject line formulas 11CTA best practices 1210 tools to automate 13Full comparison 14FAQ

The gap

Why generic dunning leaves money on the table

Most dunning emails say the same thing to everyone: "Your payment failed, update your card." It works, sort of. A generic, one-size-fits-all sequence recovers somewhere around 25-35% of failed payments. The problem is that a customer whose card expired, a customer who was $30 short for a day, and a customer whose bank flagged fraud need completely different messages, and sending all three the same email leaves the majority of recoverable revenue on the table.

Tailor the copy to the failure and recovery climbs to 45-60%. Segmenting by failure reason alone adds 15-25% to your recovery rate. Layer in correct timing (the first email inside an hour), proper deliverability (your own authenticated domain), and a sequence that stops the instant payment succeeds, and you reach the top of the band. This is recoverable revenue from customers who never wanted to leave, the cheapest growth there is. For the wider context, see what is involuntary churn.

This guide is the complete system, deeper than any competitor: an 8-code decline reference with the right email per code, three pre-dunning templates, the full Day 1/3/7 core with copy you can paste, five failure-specific sequences, post-day-7 escalation, a response-time decay table, deliverability rules most guides skip, and subject-line and CTA formulas. Everything below is paste-ready. If you would rather it just run itself, that is what SubRevival is for.

41%

same-day dunning open rate

vs ~20% for marketing email (Baremetrics)

47.6%

median recovery rate

Top performers hit 70-85% (Baremetrics)

+15-25%

lift from segmenting by failure

Targeted beats one-size-fits-all

The one-sentence version

Send fast, from your own domain, with copy matched to the decline code, across a Day 1/3/7 sequence that stops on success. That is the difference between 25-35% and 45-60% recovery.

What changed

Generic blast vs modern dunning sequence

Dunning used to be a single afterthought email. Modern dunning is a targeted, authenticated, self-halting system. Here is the difference, line by line.

Dimension	Generic blast	Modern sequence
Targeting	One generic email for every failure	Copy tailored to the decline code
Timing	Sent whenever the batch job runs	First email within 60 minutes
Sequence	A single 'payment failed' email	Day 1 / 3 / 7 plus escalation
Prevention	None; wait for the failure	Pre-dunning expiry warnings (30/7 days)
Sender	no-reply@stripe / generic	Your domain, SPF/DKIM/DMARC aligned
Stop condition	Keeps emailing after they pay	Sequence halts the moment payment succeeds
Recovery rate	~25-35% (generic)	~45-60% (failure-specific)

Watch

Retention, dunning, and revenue recovery

Retention, Dunning and Revenue Recovery (Subscriptions Scaled Podcast)

Reference

The right email for each decline code

Stripe returns a decline codeon every failed charge, and it should drive which email the customer gets. Here are the eight you'll see most and the email approach for each.

Decline code	What it means	Email approach	Type
`insufficient_funds`	Account balance too low at charge time.	Tactful, no shame. Note the auto-retry date and offer an update-now option.	soft
`expired_card`	The card is past its expiration date.	Simple card-update request. Link front and center, nothing else.	hard
`card_declined (generic_decline)`	Bank declined without a stated reason.	Neutral update request plus a 'try a different card' option.	soft
`do_not_honor`	Generic issuer block, no reason given.	Tell them to call their bank; give a 30-second script.	soft
`incorrect_cvc`	The security code did not match.	Ask them to re-enter details on the update page; retries will keep failing.	hard
`processing_error`	Temporary issuer or network error.	Reassure: nothing needed, an automatic retry is underway.	soft
`lost_card / stolen_card`	Card reported lost or stolen.	Reassure and request a brand-new card; never retry the old one.	hard
`authentication_required`	SCA / 3D Secure challenge needed (EU/UK).	Route to an authentication link, not a silent retry.	hard

Prevent the failure

Pre-dunning email templates

The cheapest failure to recover is the one that never happens. These three proactive emails catch expiring cards and lapsing trials before the charge fails. A 30-day expiry reminder opens at ~47% on its own.

Pre-dunning · 30 days before expiry

Subject

Your card on file expires soon, [First Name]

Quick heads-up: the card we have on file for your [Product] subscription expires in [MM/YYYY], before your next renewal on [renewal date].

Take 30 seconds to update it now and nothing on your account changes. You stay exactly as you are, no interruption.

Update my card

Sent proactively. A 30-day expiry reminder earns ~47% open and ~14% recovery on its own (Baremetrics).

Pre-dunning · 7 days before expiry

Subject

Action needed: your card expires in 7 days

Your saved card expires this week, and your next [Product] charge is scheduled for [renewal date]. If the card lapses first, the payment fails and your access could pause.

Updating takes less than a minute, and it saves you the hassle of a failed charge later.

Update card now

Pre-dunning · 3 days before trial end

Subject

Your trial ends in 3 days, [First Name]

Your [Product] trial ends on [trial end date], and we'll start your [Plan] plan at [price]/[period]. Want to be sure it goes through smoothly? Confirm your payment method now.

Not ready to continue? You can cancel anytime before [trial end date] and you won't be charged.

Confirm payment method

The core

The 3-email core sequence (Day 1 / 3 / 7)

This three-email spine does the heavy lifting. For each, here is the purpose, timing, expected open rate, and full copy you can adapt. Personalize the subject with a first name for a 10-15% open lift.

Day 1⏱ Within 60 minutes of the failure📬 ~40-60% open

Purpose: Catch the failure while it is fresh. Recency drives the highest open rate of the whole sequence.

Day 1 email

Subject

Your payment didn't go through, [First Name]

We tried to charge [card last4] for your [Product] subscription ([amount]) and it didn't go through. No panic, your account is still active.

Updating your payment details takes about a minute and we'll retry right away.

Update payment details

Day 3⏱ 72 hours after the failure📬 ~30-45% open

Purpose: A large share of customers simply missed the first email. This catches the busy, not the unwilling.

Day 3 email

Subject

Reminder: your payment is still pending, [First Name]

Just a follow-up, your [Product] payment of [amount] still needs updating. We'll keep your account active a little longer, but the charge has not cleared yet.

One tap and you're sorted.

Update your card

Day 7⏱ 7 days after the failure📬 ~25-40% open

Purpose: Last recovery touch before the subscription lapses. Soft urgency: clear about consequences, never threatening.

Day 7 email

Subject

Final notice: your [Product] subscription is at risk

This is the last reminder before your [Product] subscription is paused. Your payment of [amount] hasn't gone through after several attempts.

Update your card now to keep everything exactly as it is, no re-setup, no lost data.

Keep my subscription active

Stop on success: every email in the sequence must check payment status first. The instant the charge clears, via retry, card update, or delayed settlement, the rest of the sequence cancels. Read more in how to recover failed Stripe payments.

The depth

Failure-specific email copy

This is where targeted dunning earns its 15-25% lift. Swap the core copy for messaging matched to the decline code. Five of the most common, with paste-ready copy.

Expired card

Subject

Your card expired, [First Name]

The card on file expired, so your [Product] renewal didn't go through. Pop in a new one and you're all set, it takes under a minute.

Add a new card

Insufficient funds

Subject

Your payment didn't clear this time, [First Name]

Your payment didn't go through, no problem, it happens. We'll automatically retry on [retry date], or you can update your card now to sort it immediately. Either way, your account stays active in the meantime.

Update or retry now

Bank decline / do_not_honor

Subject

Your bank declined the charge, [First Name]

Your bank blocked the payment without giving a reason, which is common for recurring charges they don't recognize.

A 30-second call usually fixes it. Try: "Hi, I'd like to approve a recurring charge from [Company]. Can you remove the block?" Or just use a different card below.

Use a different card

Fraud flag

Subject

Quick check on your payment, [First Name]

Your card issuer flagged our charge as suspicious, even though it's a legitimate [Product] renewal you signed up for.

Call the number on the back of your card and confirm the charge from [Company] is expected. Once you do, hit the button below and we'll retry.

Retry my payment

Network error

Subject

We hit a snag, nothing you need to do

A temporary network error stopped your [Product] payment. You don't need to do anything, we'll automatically retry within [X hours]. We'll only email again if it still doesn't go through.

No CTA on purpose. Asking for action when none is needed erodes trust and trains customers to ignore you.

Beyond Day 7

Escalation after the core sequence

If the core sequence ends without recovery, escalate, but stay humane. The goal is to recover, not punish. Pause and restrict rather than delete, so reactivation is always one click away.

Day 10

Service-impact warning

If the sequence ended without recovery, warn that access is about to change. Be specific about what they'll lose: 'Your team's projects will become read-only on [date].' Concrete loss motivates more than vague threats.

Day 14

Account restriction notice

Restrict, don't delete. Move the account to a limited or paused state and tell them exactly how to restore it in one click. Data intact, full access one card-update away.

Day 21+

Reactivation offer

Weeks later, re-engage with a fresh angle: what they're missing, a short win-back incentive, or a simple 'still want this?' Pausing instead of hard-cancelling is what makes this stage work at all.

Timing is everything

Response-time decay: how fast recovery falls off

The longer you wait to send the first email, the less you recover. Same-day dunning emails open at around 41%, versus 27% after a month. Here is the decay relative to sending within the first hour.

First email sent	Recovery vs baseline
Under 1 hour	Baseline (best)
Within 24 hours	-5%
Next day	-15%
2-3 days later	-25%
A week or more	-50%

⚠️ This is why manual dunning loses: a human has to notice the failure before anyone can send. By the time someone checks the dashboard, you're already down the decay curve. Automation sends within minutes, every time.

Land in the inbox

Deliverability rules most guides skip

The best dunning copy in the world recovers nothing if it lands in spam. This is the layer competitors ignore, and it is the difference between a 41% open rate and silence.

Send from your own authenticated domain

Authenticate with SPF, DKIM, and DMARC so recovery mail ties to your reputation, not a shared one. SubRevival's Growth plan sends from your verified domain. This single change can lift inbox placement dramatically.

Prefer plain or lightly styled text

Dunning is transactional, not marketing. A simple, personal-looking message lands more reliably and feels trustworthy. Heavy, image-heavy HTML trips spam filters and reads like a campaign. One button, minimal images.

Use a real reply-to, not no-reply

A monitored, human reply-to address improves both deliverability and trust. Customers occasionally reply with a question, and a no-reply black hole costs you the recovery and annoys them.

Send timezone-aware, and skip Saturdays

Schedule for the customer's local business hours, not your server's midnight. Weekend sends, Saturday especially, see lower open and click rates; if a step lands on Saturday, shift it.

Keep the list clean and stop on success

Mailing dead addresses or someone who already paid both hurt reputation. Re-check payment status before every send and halt the sequence the moment the charge clears.

Get the open

6 subject line formulas that get opened

Clarity beats cleverness in transactional email. Each of these states the situation plainly; a first name lifts opens another 10-15%.

“Your payment didn't go through, [First Name]”

Directness + personalizationStates the problem immediately and uses the name. Clarity beats cleverness in transactional email, and a first name lifts opens 10-15%.

“Action needed: update your payment details”

Action prefix + task clarity'Action needed' signals urgency without alarm and sets a clear expectation of what the click does.

“Your card expired, here's the 60-second fix”

Problem + effort-anchorNaming the tiny effort ('60-second') lowers the perceived cost of acting, which raises click-through.

“Final notice: your [Product] subscription is at risk”

Stakes + specificityNames the product and the consequence. Specificity makes the stakes feel real, not generic.

“Quick question about your [Product] account”

Curiosity + low threatSoft, human framing for later-stage or fraud-flag emails where a hard 'failed payment' line would scare.

“We'll retry your payment on [date], [First Name]”

Reassurance + timelineFor soft declines: tells them exactly what happens next so they don't panic-cancel. Sets a date anchor.

Get the click

CTA best practices

One button, above the fold, describing the outcome in the customer's voice. Here is what works versus what doesn't.

Use this

Not this

Why

Update payment details

Click here

Describes the outcome, not the mechanic.

Keep my subscription active

Submit

Frames the benefit in the customer's voice.

Add a new card

Resolve issue

Concrete action beats vague problem-language.

Use a different card

Manage billing

Tells them the exact next step, no hunting.

Landing page requirements

One-step, Stripe-secure card form

Shows the plan, price, and what's at stake

Instant retry the moment the card is saved

Mobile-first, fixable from a phone in seconds

No login wall between email and update

Clear success confirmation after saving

Every best practice here, running automatically.

SubRevival sends a branded Day 1/3/7 sequence from your domain, branches by decline code, and stops on payment success. $19/mo flat, 5-minute Stripe OAuth, no code.

Start Recovering Revenue$19/mo flat. 5-minute Stripe OAuth. 21-day guarantee.

Automate it

10 tools to automate dunning emails

You can hand-build every template above, or use a tool that runs them automatically with correct timing and deliverability. These ten are ranked for Stripe-native SaaS on price-to-value, setup friction, and how much of this playbook each delivers out of the box.

SubRevival

★ Best for Automated branded dunning on Stripe ★

SubRevival runs the entire sequence in this guide automatically. Connect Stripe via OAuth in five minutes and a branded Day 1/3/7 sequence sends from your own domain, stops the instant payment succeeds, and links to a hosted card update page, no code.

Key features

Branded Day 1/3/7 auto-sequence

Sends from your domain (SPF/DKIM) on Growth

Stops automatically on payment success

Hosted card update page with instant retry

Pre-dunning expiry + renewal reminders

Trial-ending reminders

Real-time recovery dashboard

Flat $19/mo, no revenue share

Pros

Every best practice here, on by default
Your-domain sending lifts deliverability
Flat price never scales with MRR

Cons

Stripe-only by design
Not a full cancel-flow platform

Why it ranks here

It is the only tool here that ships this exact playbook, your-domain sending, segmented timing, stop-on-success, at a flat $19/mo. For Stripe SaaS it turns the guide into a five-minute setup.

The whole point of dunning email best practices is to run them automatically and consistently. That is exactly what SubRevival does.

💰 $19/mo flatConnect Stripe in 5 min

Churnkey ↗

★ Best for Dunning + cancel-flow at scale ★

Churnkey pairs precision dunning with cancel-flow deflection and segmented, value-based messaging. The most complete platform here, priced for funded teams.

Key features

ML-timed dunning sequences

Segmented messaging by LTV

Cancel-flow deflection

Reactivation campaigns

Multi-processor support

Deep analytics

In-app SDK flows

Enterprise onboarding

Pros

Sophisticated segmentation
Covers voluntary + involuntary churn
Strong analytics

Cons

Hard to justify under ~$30K MRR
Cancel flows need SDK work

Why it ranks here

Its value-based segmentation takes email targeting beyond decline codes into customer worth, the next level of personalization once you have the basics down.

When you want to segment dunning by customer value, not just failure type, Churnkey is built for it.

💰 Custom (from ~$199/mo)

Stunning ↗

★ Best for Established Stripe email dunning ★

One of the oldest Stripe dunning tools, with solid branded emails and pre-dunning. Pricing scales with your MRR.

Key features

Branded failed-payment emails

Pre-dunning expiry reminders

Hosted card update pages

Email scheduling controls

Stripe-native

Recovery reporting

Webhook setup

Long track record

Pros

Mature and dependable
Good pre-dunning
Complete Stripe feature set

Cons

MRR-scaled pricing
Webhook configuration in setup

Why it ranks here

A proven email-dunning workhorse; the trade-off is a bill that grows with your revenue.

Dependable email dunning if MRR-scaled pricing doesn't bother you.

💰 From ~$50/mo, MRR-scaled

Churn Buster ↗

★ Best for High-volume, multi-channel recovery ★

Built for high-volume DTC and subscriptions, strong on deliverability and multi-channel (email + SMS) recovery across Stripe and Recharge.

Key features

Email + SMS sequences

Deliverability engineering

Stripe and Recharge

A/B testing on flows

Retry optimization

Customer-friendly copy

Reporting

Concierge onboarding

Pros

Excellent deliverability
True multi-channel
Scales to high volume

Cons

Aimed at larger merchants
More than small SaaS needs

Why it ranks here

Adds SMS to the email playbook, the highest-open channel for late-stage recovery, where email engagement falls off.

When email alone isn't enough, Churn Buster's SMS layer catches the rest.

💰 From ~$99/mo

Baremetrics Recover ↗

★ Best for Dunning next to your metrics ★

The dunning add-on to Baremetrics analytics. If you already track MRR there, recovery lives in the same dashboard.

Key features

Automated dunning emails

Customizable timing

Native to Baremetrics

Unified metrics + recovery

Stripe integration

Churn reporting

Reactivation tracking

One login

Pros

No context-switching for users
Recovery beside churn metrics
Trusted brand

Cons

Needs a paid Baremetrics plan
Add-on, not standalone

Why it ranks here

Consolidation: your dunning performance sits right next to the metrics it moves.

Best as an add-on for existing Baremetrics users.

💰 Add-on to Baremetrics

Stripe (native emails) ↗

★ Best for A free baseline ★

Stripe Billing can send basic failed-payment emails and run Smart Retries for free. Minimal and unbranded, but a fine starting point.

Key features

Free with Stripe Billing

Smart Retries included

Basic failed-payment emails

Hosted update links

No extra tool

ML retry timing

Configurable retries

Zero maintenance

Pros

Free
Built in
Retries plus basic email

Cons

Generic, unbranded templates
No real sequence or segmentation

Why it ranks here

Free and instant, but the templates are generic and there's no true sequence, exactly the gap this guide exists to close.

Turn it on, then layer real branded sequences on top to capture what the defaults miss.

💰 Free (built into Stripe)

FlyCode ↗

★ Best for AI retries + backup methods ★

Uses AI to optimize retry timing and can route to backup payment methods, lifting recovery beyond what email alone achieves.

Key features

AI retry scheduling

Backup payment routing

Automated dunning

Stripe integration

Recovery analytics

Card network insights

A/B testing

Performance pricing

Pros

Modern AI retry logic
Backup-method fallback
Pay on recovery

Cons

% pricing scales with success
Newer track record

Why it ranks here

Pairs the email layer with backup-method routing, recovering charges email alone can't.

Worth a look if you want AI retry optimization alongside your sequences.

💰 % of recovered revenue

Paddle Retain ↗

★ Best for Data-driven, localized dunning ★

Formerly ProfitWell Retain. Combines dunning with analytics and strong localization, informed by a large subscription dataset.

Key features

Data-driven campaigns

Localized messaging

Works with Stripe

Subscription analytics

Term optimization

Reactivation flows

Benchmark data

Performance reporting

Pros

Big dataset behind defaults
Excellent localization
Bundled analytics

Cons

% pricing on recovery
Best inside Paddle

Why it ranks here

Localized, benchmark-tuned templates out of the box for global audiences.

Strong if you sell internationally and want localized dunning by default.

💰 % of recovered revenue

Gravy ↗

★ Best for Done-for-you human outreach ★

A managed service where real people handle recovery and win-back outreach, the high-touch end beyond automated email.

Key features

Human-led outreach

Failed-payment recovery

Win-back

Personalized contact

Managed service

Multi-channel

Dedicated specialists

Hands-off

Pros

Genuinely hands-off
Human touch on hard cases
Win-back included

Cons

Highest cost model
Less cadence control

Why it ranks here

When automated email plateaus, human conversations recover a stubborn tail.

For teams that want recovery handled by people, not just templates.

💰 Custom / managed service

Butter Payments ↗

★ Best for Enterprise retry optimization ★

Focuses on ML retry optimization at enterprise scale, complementing the email layer with backend recovery gains.

Key features

ML retry optimization

Enterprise scale

Issuer insights

Multi-processor

Recovery analytics

Automated decisioning

Performance pricing

Dedicated support

Pros

Built for huge volume
Sophisticated decisioning
Multi-processor

Cons

Overkill for small SaaS
Enterprise sales motion

Why it ranks here

At enterprise volume, backend retry gains compound on top of your email recovery.

Reserve for enterprise volumes where fractions of a percent matter.

💰 % of recovered revenue

Watch

A SaaS dunning strategy in practice

How to Recover 89% of Failed Payments: SaaS Dunning Strategy (Churnkey)

The playbook

Roll out dunning email in 5 phases

Build it in this order, each phase makes the next one worth more.

Send from your own domain

Before copy or timing, fix deliverability. Authenticate your sending domain with SPF, DKIM, and DMARC so dunning emails land in the inbox, not spam. A recovered payment you never delivered the email for is a contradiction.

Add pre-dunning warnings

Catch expiring cards 30 and 7 days out and trials 3 days before they convert. Preventing the failure is cheaper than recovering it, and pre-dunning emails open at ~47%.

Run the Day 1/3/7 core

First email inside 60 minutes, follow-ups at day 3 and day 7. This three-email spine is responsible for the bulk of recovered revenue.

Branch by decline code

Swap in failure-specific copy: gentle for insufficient funds, a bank-call script for do_not_honor, reassurance for fraud flags, silence-with-auto-retry for network errors. This is the 15-25% lift.

Escalate, then stop on success

After day 7, warn, restrict, then offer reactivation, but wire every step to halt the instant the charge clears. Nobody should get a 'payment failed' email after they've paid.

Side by side

All 10 tools compared

Tool	Best for	Key feature	Ease of use	Agency friendly	Price
SubRevival	Branded Stripe dunning	Your-domain Day 1/3/7, stop-on-success	★★★★★	✅	$19/mo flat
Churnkey	Dunning + cancel-flow	Value-based segmentation	★★★★★	⚠️	From ~$199/mo
Stunning	Established email dunning	Mature pre-dunning	★★★★★	✅	MRR-scaled
Churn Buster	High-volume + SMS	Multi-channel recovery	★★★★★	✅	From ~$99/mo
Baremetrics Recover	Metrics + recovery	Dunning beside analytics	★★★★★	⚠️	Add-on
Stripe native	Free baseline	Smart Retries + basic email	★★★★★	✅	Free
FlyCode	AI + backup methods	Backup payment routing	★★★★★	⚠️	% of recovery
Paddle Retain	Localized dunning	Data-driven campaigns	★★★★★	⚠️	% of recovery
Gravy	Done-for-you	Human outreach	★★★★★	⚠️	Custom
Butter Payments	Enterprise	Retry optimization	★★★★★	⚠️	% of recovery

Competitor pricing reflects publicly listed models as of June 2026 and may have changed; check each vendor for current rates.

Common questions

Dunning email FAQ

How many emails should a dunning sequence have?

Three to four core emails. Send Day 1 within an hour of the failure, then Day 3 and Day 7, with optional escalation (service warning, restriction, reactivation) after that. A single email recovers around 15%; a 3-4 email sequence recovers 35-45%. Beyond four, returns drop fast and you risk fatigue. The bigger lever is targeting the copy to the decline code, which the templates above cover. For the full step-by-step, see how to recover failed Stripe payments.

How soon should I send the first dunning email?

Within the first hour. Recovery decays quickly, a same-day dunning email opens at about 41% versus 27% after a month, and waiting a full day costs roughly 15% of your recovery. Most manual setups fail here because a human has to notice the failure first; automation sends in minutes. The response-time decay table above shows the full curve.

What's the difference between a generic and a failure-specific dunning email?

A generic email sends the same 'your payment failed, update your card' to everyone. A failure-specific email matches the decline code: a simple update link for an expired card, a no-shame retry note for insufficient funds, a bank-call script for a do_not_honor decline, and reassurance for a fraud flag. That targeting is the difference between a 25-35% recovery rate and 45-60%, segmenting by failure reason alone adds 15-25%.

Should dunning emails be plain text or HTML?

Lean toward plain or lightly styled text. Dunning is transactional, not marketing, and a simple message that looks like it came from a person tends to land in the inbox and feel trustworthy. Heavy, image-stuffed HTML can trip spam filters and reads as a campaign. Keep one clear CTA button, minimal images, and light branding. Pair that with proper domain authentication (see the deliverability section) for the best results, and read Baremetrics on dunning copy.

Why should the sequence stop when payment succeeds?

Because nothing erodes trust faster than a 'your payment failed' email arriving after the customer has already paid. It looks broken and floods your support inbox. A proper system re-checks payment status before every send and halts the moment the charge clears, whether it recovered via a Smart Retry, a card update, or a delayed bank settlement. SubRevival does this automatically, so the sequence can never out-run reality.

Do dunning emails hurt my sender reputation?

Done right, they help more than hurt, dunning is expected, transactional mail with 40-60% open rates, and engagement like that builds sender reputation. The risks are sending from an unauthenticated domain, blasting heavy HTML, or mailing dead addresses. Authenticate with SPF, DKIM, and DMARC, keep your list clean, and stop the sequence on success. Sending from your own verified domain (available on SubRevival's Growth plan) also keeps recovery mail tied to your reputation, not a shared one.

Is it worth automating dunning emails?

For any real volume, yes. Manual dunning fails at exactly the things that drive recovery, sending within the hour, every time, branching by decline code, and stopping on success, and it collapses as you grow. A tool handles all of it. SubRevival runs the entire playbook from this guide automatically, from your domain, for $19/mo flat. Compare the options first in the best dunning software guide.

What open rate should I expect from dunning emails?

Expect 40-60%, well above the ~20% of marketing email, because dunning is urgent and expected. Benchmarksput same-day opens around 41%, declining as the message ages, which is why timing matters so much. Personalizing the subject line with the customer's first name adds 10-15%. If your opens are far below this band, suspect a deliverability problem, check domain authentication before rewriting copy. Our benchmark guide has more.

Stop hand-sending dunning emails. Run the whole playbook on autopilot.

SubRevival sends a branded Day 1/3/7 sequence from your own domain, branches by decline code, and stops the instant payment succeeds. $19/mo flat, no revenue share, 21-day guarantee.

Start Recovering Revenue$19/mo flat. 5-minute Stripe OAuth. 21-day guarantee.

Keep reading

How to Recover Failed Stripe Payments

The full 2026 playbook: decline codes, Smart Retries, the sequence, and the recovery math.

Read guide

What Is Involuntary Churn?

Why failed payments quietly drain MRR, with benchmarks by company stage.

Read guide

Best Dunning Software (2026)

A ranked comparison of the tools that automate everything in this guide.

Read guide