Dunning Checklist for Growth Leads

Why Dunning Matters for DTC Subscription Brands

Failed payments are the leading cause of involuntary churn in subscription businesses. Industry benchmarks show 15 - 30% of payment failures are recoverable with a second or third attempt. Without a dunning strategy, a brand loses 2 - 5% of MRR annually to preventable payment declines.

Dunning is not a one-time retry. It's a multi-touch workflow that accounts for card expiration, insufficient funds, fraud blocks, and temporary processing errors. The difference between a 1-attempt and 3-attempt dunning flow can recover $50K - $500K annually depending on scale.

Core Dunning Workflow: The Standard 3-Attempt Model

Most DTC brands use a 3-attempt dunning sequence with increasing intervals. The first retry happens within 1 - 3 days of the initial decline. The second retry occurs 5 - 7 days later. The third retry happens 10 - 14 days after the second failure.

Attempt 1: Day 1 - 3 (silent retry, no customer notification required)
Attempt 2: Day 5 - 7 (send payment failure email, link to update payment method)
Attempt 3: Day 10 - 14 (final notice email, offer pause/downgrade option)
Day 15+: Execute fallback action (pause, downgrade, or cancel based on policy)

Payment Recovery Thresholds and Decision Rules

Recovery rates vary by decline reason. Temporary declines (insufficient funds, fraud blocks) recover at 40 - 60% on retry. Permanent declines (expired card, account closed) recover at 5 - 15% unless the customer updates their payment method.

Set recovery targets based on customer segment. High-LTV customers (annual plans, $100+ MRR) warrant 4 - 5 retry attempts. Low-LTV customers ($10 - 30 MRR) should trigger cancellation after 2 attempts to minimize operational cost.

If recovery rate < 20% after 3 attempts: reduce retry count to 2 for that cohort
If customer LTV > $500: extend dunning window to 21 days with 4 attempts
If customer has updated payment method during dunning: reset retry counter to Attempt 1
If customer has paused subscription: do not run dunning; resume on unpause date

Customer Communication: Messaging and Timing

Silent retries (Attempt 1) should never trigger customer email. Sending a notification for a temporary processing error creates support tickets and erodes trust. Only email after the first failure is confirmed permanent or after Attempt 2 fails.

Dunning emails must include a direct link to update payment method. Generic 'contact support' CTAs reduce recovery by 30 - 40%. Include the last 4 digits of the declined card and the exact billing date.

Attempt 2 email subject: 'We couldn't process your payment - update now'
Attempt 3 email subject: 'Final notice: Your subscription will pause on [DATE]'
Include one-click payment update link (not a form, not a support ticket)
Offer pause or downgrade as alternative to cancellation in final notice
Do not mention the decline reason unless it's actionable (e.g., 'card expired')

Common Failure Modes and How to Avoid Them

Dunning fails when retry logic is too aggressive or too passive. Retrying the same declined card 10 times wastes processing fees and damages customer relationships. Retrying only once leaves money on the table.

Another failure mode: not segmenting by decline reason. A fraud block requires a different retry strategy than an expired card. Fraud blocks often resolve on the second attempt (customer calls bank). Expired cards need customer action.

Failure mode: Retrying without customer action - if Attempt 1 fails, Attempt 2 will fail 80% of the time unless customer updates payment method
Failure mode: Not pausing subscriptions - canceling immediately burns LTV; pause for 30 days and send win-back email instead
Failure mode: Dunning during promotional periods - if customer is on a trial or discount, pause dunning until full price billing begins
Failure mode: No retry cap - set max 3 - 4 attempts per billing cycle; after that, execute fallback action
Failure mode: Ignoring payment processor response codes - 'do not retry' codes (e.g., lost card, account closed) should skip to fallback immediately

Implementation Checklist

Before launching dunning, audit current payment failure rate and recovery rate. Measure baseline involuntary churn. Then implement the workflow in stages.

[ ] Define retry schedule: 3 attempts at days 1, 5, 10 (or custom based on LTV segment)
[ ] Map payment processor decline codes to retry logic (do not retry vs. retry)
[ ] Write and test Attempt 2 and Attempt 3 email templates with payment update links
[ ] Set fallback action: pause (30 days) or cancel (based on policy)
[ ] Exclude customers on trial, pause, or downgrade from dunning
[ ] Configure retry cap: max 3 - 4 attempts per billing cycle
[ ] Test with 10% of failed payments first; measure recovery rate before full rollout
[ ] Set up alerts: if recovery rate drops below 15%, pause and investigate
[ ] Document decline reason mapping in your payment processor (Stripe, Shopify Payments, etc.)
[ ] Review dunning performance monthly: recovery rate, email open rate, fallback action rate

Measuring Dunning Success

Track three metrics: recovery rate (% of failed payments recovered), dunning email open rate, and fallback action rate. Recovery rate is the primary KPI. Benchmark: 25 - 35% recovery on a 3-attempt model is healthy.

Recovery rate = (Successful retries / Total failed payments) × 100
Dunning email open rate should be 20 - 40%; if below 15%, test subject line and CTA
Fallback action rate = (Paused + Downgraded + Canceled) / Total dunning attempts; target 5 - 10%
Monitor involuntary churn month-over-month; dunning should reduce it by 1 - 3 percentage points

Questions

FAQ

Should we retry a declined card immediately or wait?

Wait 1 - 3 days before Attempt 1. Immediate retries fail 90% of the time because the underlying issue (insufficient funds, fraud block, processor timeout) hasn't resolved. A 24-hour delay allows temporary issues to clear and fraud blocks to be lifted by the customer's bank.

What's the difference between dunning and payment retry?

Payment retry is a single automated attempt to process a failed charge. Dunning is the entire workflow: multiple retries, customer communication, and fallback actions (pause, downgrade, cancel). Dunning is the strategy; retry is one tactic within it.

Should we pause or cancel after dunning fails?

Pause first. Pausing for 30 days preserves the customer relationship and allows time for a win-back email. Cancel only if the customer has been paused for 60+ days or explicitly requests cancellation. Pausing recovers 10 - 20% of customers; immediate cancellation recovers 0%.

How do we handle customers who update their payment method during dunning?

Reset the retry counter to Attempt 1 and retry immediately. A customer who proactively updates their payment method has high intent to stay. Retry within 24 hours; recovery rate on this cohort is typically 70 - 85%.

Want this on your account?

Thirty minutes. Bring the number that keeps you up.

Book a demo