Dunning Automation: How to Set It Up Step by Step

Dunning automation is the system that recovers a subscription payment after it fails — automatically retrying the charge and emailing the customer to update their card, with no manual work from your team. For most SaaS businesses, a large share of cancelled subscriptions are not customers who chose to leave; they are payments that failed and were never recovered. Automated dunning is the most direct way to fix that. This guide walks through how it works and how to set it up correctly.

What Is Dunning Automation?

Dunning is the process of following up on a failed or overdue payment. Dunning automation puts that process on autopilot: when a recurring charge is declined, the system retries the payment on an optimized schedule and sends a sequence of recovery emails prompting the customer to update their payment method. The goal is to recover the revenue before the subscription is cancelled — without anyone on your team touching it.

The difference between manual and automated dunning is consistency. A person might chase a failed payment once and forget the rest; an automated system retries and follows up every single time, at the times most likely to succeed. That consistency is where the recovered revenue comes from. See our dunning automation overview for how a fully managed sequence is structured.

Why Failed Payments Happen

Before automating recovery, it helps to understand what you are recovering from. Most recurring-payment failures fall into a few buckets:

• Insufficient funds: A temporary issue that usually resolves itself within a few days — ideal for retries.
• Expired or reissued cards: The card on file is no longer valid and the customer must update it.
• Bank fraud blocks: The bank flagged the charge; the customer often needs to approve it.
• Processor or network errors: Transient failures that frequently succeed on an immediate retry.

Soft failures (funds, transient errors) are recovered mostly through retries. Hard failures (expired cards, fraud blocks) need the customer to act, which is what the email sequence is for. A good dunning system handles both paths.

The Core of Automated Dunning: Retries + Emails

Effective automated dunning runs two coordinated tracks at the same time.

1. Smart payment retries

Rather than retrying on a fixed daily schedule, time retries around when funds are most likely to be available. A practical pattern: retry a few hours after the failure (to catch transient declines), then again after one to two days, then space the remaining attempts across the next week — favoring early-morning and payday windows. Spreading three to four attempts over roughly seven days recovers the bulk of soft failures with no customer involvement at all.

2. Recovery email sequence

In parallel with retries, send a short sequence of recovery emails for failures that need the customer to update their card. The widely used pattern is three emails over seven days: a friendly heads-up on day 0, an urgency reminder on day 3, and a final notice on day 7 before cancellation. Each email needs one clear call to action — a direct, no-login link to update the payment method. For the copy, timing, and subject lines in detail, see our guide to dunning email best practices.

How to Set Up Dunning Automation (Step by Step)

1. Connect your billing data. Link the system to your payment processor (such as Stripe) so failed-payment events flow in automatically. This is what triggers the entire sequence.
2. Configure your retry schedule. Define when and how often to retry. Spread three to four attempts over about a week and bias toward payday and morning windows rather than uniform 24-hour intervals.
3. Build the email sequence. Set up the day 0 / day 3 / day 7 emails, each with a single update-payment button and your own branding so customers recognize and trust them.
4. Add a hosted update page. Email links should point to a tokenized page where the customer can update their card without logging in — every extra step lowers recovery.
5. Set a grace period and stop rule. Keep service active during recovery (typically 7–14 days), then downgrade rather than instantly cancel. Stop the sequence the moment a payment succeeds so customers never get chased after they have paid.
6. Measure and tune. Track recovery rate, email open and click rates, and time to recovery, then adjust timing and copy from the data.

Build It Yourself or Use Dunning Automation Software?

You can build dunning automation in-house using your processor's webhooks and a transactional email provider. It is achievable, but it means owning retry scheduling, email deliverability, tokenized update links, sequence-stop logic, and reporting — and maintaining all of it as your billing edge cases grow.

Dedicated dunning automation software handles those pieces out of the box and connects to your processor in minutes, which is why most teams reach for it once recovery becomes a priority. The right choice depends on engineering capacity: if you have spare cycles and unusual billing logic, building may make sense; if you want recovery running this week, software is faster. To estimate the revenue at stake either way, try the recovery calculator. For the broader step-by-step process around the dunning sequence, see how to recover failed payments.

Frequently Asked Questions

What is dunning automation?

Dunning automation is software that automatically recovers failed subscription payments by retrying the charge on an optimized schedule and emailing the customer to update their payment method, without manual follow-up from your team.

How does automated dunning recover failed payments?

It runs two tracks in parallel: smart retries catch temporary failures like insufficient funds, while a timed email sequence prompts customers with expired or invalid cards to update their details through a no-login link before the subscription is cancelled.

Do I need dunning automation software, or can I build it myself?

You can build it with processor webhooks and an email provider, but you take on retry scheduling, deliverability, tokenized update pages, and reporting. Dunning automation software handles those out of the box and connects to your processor in minutes.

How many dunning emails should I send?

Three emails over about seven days is the standard pattern — a heads-up, an urgency reminder, and a final notice. Sending more crosses into harassment and hurts trust without adding meaningful recovery.