Pre-Dunning: How to Prevent Failed Payments Before They Happen
A practical guide to pre-dunning, card-expiry prevention, and proactive billing hygiene that reduces failed payments before retry logic starts.
Most dunning programs start after a payment fails. Pre-dunning starts earlier. It identifies customers who are likely to hit billing trouble and asks them to fix the issue before the renewal attempt breaks.
That matters because once a payment fails, you are already in recovery mode. You are coordinating retries, messaging, and support expectations under time pressure. Stripe’s revenue recovery tooling includes expiring-card notifications and automatic card updates precisely because prevention is part of revenue recovery, not separate from it (Stripe Revenue Recovery, Stripe Customer Emails, Stripe Cards Overview).
If your team has only focused on post-failure dunning so far, this is the missing upstream layer.
What pre-dunning actually means
Pre-dunning is proactive communication and workflow logic triggered before a scheduled renewal fails. The most common use case is card expiration. Stripe documents that it can automatically send expiring-card notifications one month before expiry when the card on file is the default payment method (Stripe Customer Emails).
In practice, pre-dunning can be triggered by:
- card expiring soon
- payment method recently replaced
- prior failed renewal history
- high-value account with stale billing credentials
- upcoming annual renewal where failure would be expensive
You can think of it as preventive maintenance for subscription revenue.
Why pre-dunning works
Pre-dunning works because it removes avoidable failure modes before your retry engine has to deal with them.
Stripe explains that saved card details can sometimes be updated automatically through the network when issuers replace a card, but participation varies and you cannot assume every card will update successfully (Stripe Cards Overview). Mastercard’s Automatic Billing Updater program is built around the same problem: when a stored payment card expires or is renewed, Mastercard can provide updated credentials to merchants in participating scenarios (Mastercard Automatic Billing Updater).
These network services help, but they do not eliminate the need for merchant-side prevention. There will always be cards and situations that require direct customer action.
Pre-dunning versus regular dunning
The difference is timing and customer psychology.
Regular dunning says, “Your payment failed. Please fix this now.”
Pre-dunning says, “Your payment method may need attention before your next renewal.”
The second message usually feels less urgent and less punitive, which means customers are more likely to act before access is at risk. It also gives your team more room to keep the renewal flow clean instead of running an avoidable recovery sequence.
For teams already using a post-failure sequence, pre-dunning is usually additive rather than disruptive.
The highest-value pre-dunning triggers
1. Expiring cards
This is the easiest starting point because the signal is concrete. Stripe supports card-expiration reminders and network-based automatic updates, which means the platform itself treats expiry management as a core revenue-recovery lever (Stripe Customer Emails, Stripe Cards Overview).
If you want a quick operational input, run the card expiry scanner.
2. High-value upcoming renewals
An annual renewal or large account invoice deserves more proactive handling than a low-value monthly plan. The logic is simple: the cost of failure is higher, so the prevention threshold should be lower.
3. Recent recovery history
If a customer had a failed payment last cycle, they are a strong candidate for preventive reminders before the next renewal.
4. Accounts with authentication friction
Stripe notes that some off-session payment attempts fail because customer authentication is required (Stripe Card Declines, Stripe Decline Codes). If your system detects recurring authentication-related issues, pre-dunning can direct those users to update payment details or prepare for a required action.
What a strong pre-dunning sequence looks like
For most SaaS teams, a simple sequence is enough:
30 days before expiry
Send a calm reminder that the saved card is expiring soon and include one primary CTA to update billing details.
7 to 14 days before renewal
Send a second reminder if the card is still unchanged. Make the date explicit and keep the CTA identical to avoid confusion.
1 to 3 days before renewal
For high-value customers or annual plans, send a short final reminder or trigger a customer-success task.
You do not need to over-message. The goal is to prevent failure, not create inbox fatigue.
Copy principles for pre-dunning
Good pre-dunning copy is closer to account maintenance than collections copy. It should:
- name the issue plainly
- mention the renewal date
- explain that updating now avoids interruption
- provide one clear action link
- avoid false urgency
If you need examples, the dunning email templates are useful even for pre-dunning because the best structural habits are similar.
Pre-dunning and network-level automation are complements
Visa positions network tokenization as a way to create seamless checkout flows and increase authorization rates, while reducing reliance on raw PAN storage (Visa Token Service, Visa Tokenization Overview). Mastercard similarly positions tokenization as a way to improve security and approval outcomes in digital commerce (Mastercard Tokenization).
That does not mean tokenization or account updaters replace pre-dunning. It means they improve the baseline. Your job is still to handle the accounts that remain at risk.
This is especially important for:
- merchants with mixed issuer participation
- international card portfolios
- high-value annual contracts
- customers who ignore passive reminders
Metrics that tell you pre-dunning is working
Track these before and after rollout:
- renewal failure rate for accounts with expiring cards
- percentage of at-risk cards updated before renewal
- support tickets related to expired or outdated payment methods
- recovery-rate improvement for cohorts receiving pre-dunning
- involuntary churn from expiration-related declines
You can pair those numbers with the failed payment calculator to estimate the MRR effect.
Common mistakes
Pre-dunning tends to underperform for the same reasons regular dunning does:
- the message is too vague
- the update page is hard to complete on mobile
- the date is unclear
- the CTA is buried below explanatory text
- the sequence is not limited to the actually at-risk cohort
The operational fix is straightforward: narrow the trigger, simplify the message, and remove friction from the update path.
Where pre-dunning fits in the billing stack
Think of billing recovery as four layers:
- prevention
- retry timing
- customer communication
- measurement
Pre-dunning belongs in the prevention layer. Smart retries sit one step later. If you only invest in retries, you are solving a downstream symptom while leaving cheap upstream wins untouched.
That is also why pre-dunning deserves a place in your broader subscription billing health guide, not just your email calendar.
When you need more than basic platform settings
Stripe’s built-in reminders are a good baseline, and many teams should enable them first (Stripe Customer Emails). But if you want segmentation by plan type, annual-renewal workflows, branded message sequencing, or custom suppression logic, you may need more than default settings.
That is the layer where teams start evaluating specialized approaches such as RevGuard vs Recurly Dunning or RevGuard vs ProfitWell Retain, depending on current tooling and operating model.
Final takeaway
Pre-dunning is one of the easiest ways to reduce failed payments because it addresses predictable risk before revenue enters recovery mode. Expiring-card reminders, high-value renewal alerts, and targeted billing-maintenance prompts will not eliminate failures, but they reduce how often your retry and dunning systems need to work in the first place.
For subscription businesses with meaningful MRR, that makes pre-dunning one of the highest-leverage preventive controls in the stack.