Resources

Expired Cards: Payments That Fail on Schedule

Every card in your subscriber base has a printed expiry date, which means every expired-card payment failure in your business was knowable in advance — in many cases, months in advance. No other failure class works like this. Insufficient funds depends on the customer's bank balance on a given day. An expired card is a date on a calendar, sitting in your own database. This guide covers the warning window that date creates, how network account updater services quietly fix a share of expiries before they fail, the pre-dunning notices that handle the rest, the card-update ask itself, and the full recovery sequence for the charges that fire anyway.

The expiry math in a subscriber base

Cards are typically issued with multi-year validity, and a subscriber base holds a spread of issue dates. The practical consequence: in any given month, a slice of your subscribers' cards on file reach their expiry month. If those subscribers' renewal dates fall after the card stops working — and no one has refreshed the details — those renewals fail. Not randomly. On schedule.

Three properties make this failure class worth its own system:

• It is predictable. You can list, today, every subscriber whose card expires before their next two renewals. Almost no other churn cause hands you a named list in advance.
• It signals nothing about intent. The customer did not cancel and probably does not know the card on file is the old one. Their bank mailed a replacement; your system just never got it.
• It is fully preventable or quickly fixable. Either the details get refreshed automatically by an updater service, or the customer updates them in under a minute when asked properly and early.

Expired cards also intersect with a second group: replaced cards. When a card is lost, compromised, or reissued, the number changes and the old details die the same way an expired card's do. The customer's intent is identical — none — and the fix is identical: new details on file. Treat the two as one family.

The warning window: act before the date, not after

The window opens as soon as a card's expiry month is visible on the horizon of a renewal. A disciplined operator works it in stages:

1. Inventory. Pull every card on file expiring in the next 60 days, matched against each subscriber's next renewal date. Cards expiring after the next renewal but before the one following belong on the list too — the second renewal is the one that will fail.
2. Let automation try first. Account updater services, covered below, refresh many of these silently. Run them before you spend customer attention.
3. Notify the remainder. Subscribers whose details did not update get a pre-expiry notice — calm, specific, and early enough to act before any service interruption is possible.
4. Verify. After each renewal cycle, check which flagged cards actually updated and which are heading into a failure you can now predict to the day.

This is pre-dunning in its purest form: solving the failure before it exists. Our explainer on pre-dunning covers the broader discipline — expiry warnings, pre-renewal reminders, and other before-the-failure touches — and expired cards are its highest-certainty use case.

Network account updater services: the silent fix

Card networks and processors operate account updater services that share refreshed card details with merchants who hold the old ones. When a customer's bank issues a replacement card — new expiry date, sometimes a new number — the updater service can pass those new details to your billing system automatically, and the next renewal charges the new card as if nothing happened. The customer never sees a message and never lifts a finger.

At capability level, what matters for an operator:

• Coverage is partial, not total. Not every issuing bank participates, and not every card type is covered. Updaters fix a meaningful share of expiries and replacements; they do not eliminate the class. Plan for a remainder that still needs the customer.
• It runs in the background. Where your processor supports it, updater services work without changing your checkout or asking subscribers to re-enter details — which is exactly why they should run before any notice campaign.
• It pairs with, not replaces, pre-dunning. Updater first, notice second, recovery third. Each layer catches what the previous one missed.

Our dedicated guide to card updater services goes deeper on how the network services work, where coverage comes from, and what to ask your processor.

The pre-expiry notice: the highest-converting email in dunning

When the updater cannot fix a card, the ask goes to the customer — and this ask is unlike every other dunning message, because nothing has gone wrong yet. The service still works. There is no failed charge, no deadline pressure, no embarrassment. The notice should be built accordingly:

• Name the card, not the problem. "The card on file for your subscription expires this month" — with the brand and last digits where your system supports it — reads as account housekeeping, not a collections notice.
• One link, one minute. The notice points to a secure card-update page and nothing else. Every extra element in the message competes with the single action that matters.
• Say what happens if they do nothing. Plainly and without threat: when the card expires, the next payment will fail and the subscription will pause or cancel after a recovery window. Customers act on consequences they understand.
• Time it with slack. Send early enough that a customer who reads email weekly still acts before the renewal, and follow up once for non-responders as the date closes in.

The destination matters as much as the message. A card-update page should be branded, mobile-clean, free of login walls where a secure token link can do the job, and explicit that updating the card does not charge anything today. Our card update page guide covers the design and trust details that decide whether customers complete the form or abandon it.

When the charge fires anyway: the recovery sequence

Some expired-card renewals will still fail — the notice went to spam, the customer meant to act, life intervened. At that point the failure has a known cause and a known cure, and the sequence should reflect both:

1. Do not retry the dead details. An expired card will decline identically on every attempt. This is the routing discipline that separates decline-aware systems from fixed schedules — and it is why expired cards are classified alongside the failures that need customer action rather than patience. Our comparison of hard declines vs soft declines explains where expired cards sit in that taxonomy and why the response differs.
2. Run the updater check again. Details sometimes refresh after the failure. If new details arrive, charge them promptly — once — and restore the subscription without the customer ever knowing there was a problem.
3. Send the update request immediately. Not at the next scheduled dunning step — now, while the customer still expects the product and the missed renewal is a surprise rather than a settled fact. The message names the expired card, links the update page, and states the window before cancellation.
4. Charge the moment new details land. When a customer updates their card mid-sequence, attempt the renewal right away. Making a cooperative customer wait for a scheduled retry is how goodwill leaks out of a recovery system.
5. Close cleanly if nothing arrives. At the end of the window, cancel or pause per your policy, leave the door open with an easy reactivation path, and record the churn as involuntary and card-caused — because it was, and your reporting should say so. According to Recurly research, 20–40% of subscriber churn is involuntary; expired cards are the most preventable slice of that range.

Operational habits that keep expiries boring

• Sweep monthly, not quarterly. A monthly expiry inventory keeps every warning window comfortably ahead of the failure.
• Watch the annual-plan cliff. Annual subscribers give you one charge a year; if that charge is the one that meets an expired card, a full year of revenue rides on the update request. Flag annual renewals with expiring cards first in every sweep.
• Measure the class separately. Track expired-card failures as their own line. If the number is not falling after updater coverage and pre-expiry notices, the problem is your notice or your update page — both fixable — not your customers.
• Never surprise-charge a stale card. Customers who updated details for one product and get charged on an old subscription they forgot will dispute first and ask later. Clarity in every message is cheaper than chargebacks.

The bottom line

Expired cards are the failure class with a printed schedule and a willing customer. Work the warning window: inventory expiries monthly, let account updater services refresh what they can, send a clear pre-expiry notice to the rest, and when a charge still fails, skip the useless retries and run a fast, specific update sequence. Do this well and an entire category of involuntary churn simply stops appearing in your numbers. Swipe Again builds this into its recovery layer across the nine platforms it supports — branded update pages, pre-failure and dunning outreach with SMS in the sequence, decline-aware retries for the failures that do need them — at $179/mo flat, with no percentage of recovered revenue.

Frequently asked questions

How far in advance should I warn customers about an expiring card?

Start with an inventory of cards expiring in the next 60 days and send the pre-expiry notice early enough that the customer can act before the first at-risk renewal — with a follow-up for non-responders as the date approaches. The notice works best while nothing has failed yet, when it reads as routine account housekeeping rather than a dunning message.

What is an account updater service?

It is a service operated through the card networks and processors that automatically refreshes stored card details when a bank issues a replacement — a new expiry date or a new card number. Merchants receive the updated details in the background, so the next renewal charges the new card without the customer doing anything. Coverage is partial: not every bank participates, so updater services reduce expired-card failures rather than eliminating them.

Should I retry a payment that failed because the card expired?

No. Retrying the same expired details will produce the same decline every time, wasting attempts and fees. First check whether updater services have refreshed the details; if they have, charge the new card once, promptly. Otherwise, send the customer a card-update request and charge as soon as new details arrive.

What should a card-update page include?

Your branding, so the customer trusts it; a clear statement of which subscription and card are being updated; a secure card form that works well on mobile; access through a secure link without forcing a password reset; and a plain note that updating the card does not charge anything immediately. The page's only job is completion, so remove everything that does not serve it.

Are expired-card failures really a big deal?

Yes, because of their volume and preventability. Every card in your base expires on a known date, so a steady slice of renewals meets a dead card every month if nobody acts. Unlike most churn causes, you can identify the exact subscribers at risk in advance and fix most cases automatically or with one clear message, which makes this the highest-return maintenance routine in subscription billing.