Quick Definition
Pre-dunning is the practice of proactively contacting customers before their payment method fails—typically when their credit card is approaching its expiration date.
Unlike traditional dunning (which happens after a payment fails), pre-dunning prevents the failure from happening in the first place.
The key insight: It's easier to get customers to update their card before they lose access than after.
Pre-Dunning vs Dunning
| Aspect | Pre-Dunning | Dunning |
|---|---|---|
| Timing | Before payment failure | After payment failure |
| Trigger | Card expiring soon | Payment declined |
| Customer status | Full access | May lose access |
| Success rate | 80-90% | 60-80% |
| Customer experience | Positive (helpful) | Neutral to negative |
| Urgency | Low pressure | Higher pressure |
Best practice: Use both. Pre-dunning catches most issues; dunning recovers the rest.
Read the full comparison: Pre-Dunning vs Dunning: Which is Better?
Why Pre-Dunning Matters
1. Higher Success Rates
Customers are more likely to update their payment method when:
- They still have full access to your product
- There's no urgency or pressure
- They haven't experienced any disruption
Pre-dunning emails see 80-90% update rates compared to 60-80% for post-failure dunning.
2. Better Customer Experience
Pre-dunning feels helpful, not demanding:
- "Hey, your card expires soon—here's an easy way to update it"
- vs. "Your payment failed—update now or lose access"
3. Prevents Involuntary Churn
Involuntary churn happens when customers lose access due to payment failures. Pre-dunning stops this at the source by preventing failures entirely.
4. Reduces Support Load
No failed payment = no "Why can't I log in?" tickets.
How Pre-Dunning Works
Step 1: Detect Expiring Cards
Monitor your payment processor for cards expiring in the next 30-60 days:
- Stripe: Use the
customer.source.expiringwebhook or query card data - Other processors: Similar APIs available
See our technical guide: How to Detect Expiring Cards in Stripe
Step 2: Send Proactive Reminders
Typical pre-dunning sequence:
| Days Before Expiry | Channel | Message Tone |
|---|---|---|
| 30 days | Friendly heads-up | |
| 14 days | Email + SMS | Helpful reminder |
| 7 days | Slightly urgent | |
| 3 days | SMS | Final reminder |
Get copy-paste templates: Card Expiration Email Templates
Step 3: Make Updates Easy
Every message should include:
- Pre-authenticated link (no login required)
- Mobile-friendly update page
- Clear instructions
Step 4: Automate Retries + Dunning Backup
If pre-dunning doesn't work and the card expires:
- Payment attempt fails
- Dunning sequence kicks in
- Smart retries attempt recovery
Pre-Dunning Best Practices
Timing
- Too early (60+ days): Customer forgets or ignores
- Too late (< 7 days): Not enough time to act
- Sweet spot: Start at 30 days, increase frequency as expiration approaches
Messaging
Do:
- Be helpful and friendly
- Explain what's happening clearly
- Provide one clear action (update card)
- Show what they'll lose if they don't act
Don't:
- Sound threatening
- Use technical jargon
- Require login to update
- Send too many messages
Channels
| Channel | Best For | Open Rate |
|---|---|---|
| Detailed info, links | 20-30% | |
| SMS | Urgency, quick action | 90%+ |
| In-app | Active users | Varies |
Multi-channel (email + SMS) gets best results.
Pre-Dunning + Card Updater Services
For even better results, combine pre-dunning with card updater services:
- Card Updater: Automatically updates card numbers when banks issue new cards
- Pre-Dunning: Catches cases card updater misses (new card entirely, user-initiated changes)
Together, they can prevent 90%+ of card-related payment failures.
Measuring Pre-Dunning Success
Track these metrics:
| Metric | Formula | Good Benchmark |
|---|---|---|
| Pre-dunning conversion rate | Cards updated / Expiring cards notified | > 70% |
| Payment failure rate (expiring cards) | Failed payments / Total payments from cards that were expiring | < 2% |
| Prevented churn | Customers who updated before failure | Track monthly |
Pre-Dunning ROI
Example calculation:
| Metric | Value |
|---|---|
| Cards expiring monthly | 100 |
| Average subscription value | $50/month |
| Without pre-dunning (20% fail, 30% churn) | 6 churned = $300/month lost |
| With pre-dunning (5% fail, 30% churn) | 1.5 churned = $75/month lost |
| Monthly savings | $225 |
| Annual savings | $2,700 |
Calculate your potential savings →
Key Takeaways
- Pre-dunning = before failure — Contact customers when cards are expiring, not after they fail
- Higher success than dunning — 80-90% vs 60-80%
- Better experience — Helpful, not demanding
- Use with dunning — Pre-dunning prevents; dunning recovers what slips through
- Automate everything — Detect, notify, and track automatically
Related Resources
- Card Expiration Email Templates — Copy-paste templates
- How to Prevent Failed Payments — Complete strategy guide
- Pre-Dunning vs Dunning — Detailed comparison
- What is Dunning? — Post-failure recovery
- What is Card Updater? — Automatic card updates
Automate Pre-Dunning with Rekko
Rekko automatically detects expiring cards and sends pre-dunning sequences before payments fail—plus full dunning recovery if they do.
- Automatic card expiration detection
- Multi-channel pre-dunning (email + SMS)
- Seamless transition to dunning if needed
- Track prevented churn in your dashboard