4 Card Expiry Reminder Email Templates That Prevent Failed Payments (2026)
Expired cards cause 25-30% of all SaaS payment failures. A proactive reminder sequence starting 30 days before expiry prevents the failure from ever happening. SaaS companies that send card expiry reminders see 15-20% lower involuntary churn than those that wait for the payment to fail. These 4 templates cover the full pre-expiry window.
Template 1: 30-Day Advance Notice
Subject lines (A/B/C)
Email body
Why this works
Framing this as preventing future annoyance ("skip all that") rather than preventing a consequence makes it feel helpful, not threatening. Including the specific expiry date and next billing date lets the customer judge urgency themselves. 30 days is early enough to be casual; this email should feel like a thoughtful reminder, not an emergency. The 20-second estimate lowers perceived effort.
Template 2: 14-Day Follow-Up
Subject lines (A/B/C)
Email body
Why this works
Adding the practical detail about the replacement card helps customers who think "but I haven't gotten a new card yet". They may have already received it and just need to enter the new details. Connecting the expiry date to the specific billing date creates concrete urgency ("will this actually affect me?"). The slightly more direct tone than email 1 reflects the narrowing window.
Template 3: 7-Day Urgent Reminder
Subject lines (A/B/C)
Email body
Why this works
Acknowledging previous emails ("I've sent a couple of reminders") shows self-awareness instead of robotic repetition. Listing the cascade of consequences (failure → emails → access interruption) makes inaction feel like choosing hassle. The note about bank auto-updaters is crucial. Stripe and Visa/Mastercard's Account Updater service automatically refreshes ~40-60% of expiring cards. This caveat prevents customers who are already covered from feeling nagged.
Template 4: Day-Of Expiry. Last Chance
Subject lines (A/B/C)
Email body
Why this works
Shortest, most direct email in the sequence. "Almost certainly fail" is honest and specific. more credible than "may fail." Flagging that a separate recovery sequence will follow creates a preview of annoyance that motivates action now. "Last reminder I'll send before the expiry" respects inbox space and creates a natural deadline. Day-of emails convert at the highest per-email rate in pre-dunning because the deadline is no longer abstract.
The Math Behind Pre-Dunning Card Expiry Emails
Expired cards account for 25-30% of all recurring payment failures in SaaS. For a $20K MRR company with a 3% monthly failure rate, that's $150-$180/mo in failures caused exclusively by expired cards. A pre-dunning email sequence that converts 50-70% of those customers to update before expiry saves $75-$126/mo. or $900-$1,500/year. From a 4-email sequence that costs nothing to send.
Card network auto-updaters (Visa Account Updater, Mastercard Automatic Billing Updater) silently refresh 40-60% of expiring cards. This means your pre-dunning emails are only targeting the 40-60% of customers whose cards won't auto-update. That subset is the highest-risk group. without your emails, nearly all of them will experience a payment failure.
Stripe fires the customer.source.expiring webhook approximately 30 days before a card's expiration month. This webhook is the trigger for your entire pre-dunning sequence. Most SaaS founders don't listen for this webhook, which is why pre-dunning is one of the most under-utilized retention tactics in the industry. One webhook listener and 4 timed emails can eliminate an entire category of involuntary churn.
How SaveMRR Automates Card Expiry Alerts
Setting up card expiry reminders manually requires listening for Stripe's customer.source.expiring webhook, building suppression logic (don't email if the card auto-updated), scheduling the 4-email cadence, and generating card update links. Here's what SaveMRR does instead:
- •Automatically listens for customer.source.expiring webhooks. No code or webhook endpoint needed
- •Sends the full 4-email pre-dunning sequence with smart suppression (stops if the card is updated mid-sequence)
- •Generates one-click card update links for each customer. No login required
- •Tracks which customers updated proactively vs; which ones failed, so you can measure the ROI of pre-dunning
- •Works alongside Visa/Mastercard auto-updaters. only emails customers whose cards won't auto-refresh
- •Part of the $19/mo Starter plan. No extra cost. No per-email charges.
Card expiry reminders are a form of pre-payment recovery. catching failures before they happen. The involuntary churn benchmark shows that 25-30% of all payment failures trace back to expired cards. Use the failed payment recovery calculator to see how much pre-dunning saves, and check the failed payment recovery benchmark for the full data. For the complete lifecycle after a failure occurs, see the credit card failure churn playbook.
Frequently asked questions
When should I send the first card expiry reminder email?
30 days before the card expires. This gives the customer maximum time to update while the issue is still low-stakes. Sending earlier than 30 days feels premature ("my card doesn't expire for 2 months, why are you emailing me?"). Sending later than 30 days misses the casual-reminder window and jumps straight to urgency.
Do I need card expiry emails if Stripe has auto-updating?
Yes. Stripe and card networks auto-update 40-60% of expiring cards, but that leaves 40-60% un-updated. Those customers will experience a payment failure, trigger your dunning sequence, and some will churn. Pre-dunning emails catch the customers that auto-updaters miss, which is the highest-risk group.
How do I know when a customer's card is about to expire?
Stripe fires a customer.source.expiring webhook approximately 30 days before a card's expiration month. This webhook includes the customer ID, card last4, and expiry date. You can build a listener for this webhook or use a tool like SaveMRR that monitors it automatically and triggers the email sequence.
Should I include the card's last 4 digits in the email?
Absolutely. Including the last 4 digits (e.g., "card ending in 4242") helps customers immediately identify which card needs updating, especially if they have multiple cards across services. It also adds credibility; the email clearly knows which specific card is expiring, which makes it feel like a personalized alert rather than spam.
How many card expiry reminder emails is too many?
4 emails over 30 days is the sweet spot: day 30, day 16, day 7, and day 0. Sending fewer than 3 leaves recoveries on the table. Sending more than 5 risks spam complaints and unsubscribes. Always suppress future emails once the customer updates their card. sending "please update" after they already did is the fastest way to erode trust.