What Are Backup Cards and Account Updaters?
Stored cards do not last forever. Cards expire, banks reissue them after fraud or loss, and account numbers change — and every one of those events silently breaks a recurring billing agreement that depends on the stored details. Backup cards and account updater services exist to keep subscriptions running through these changes without asking the customer to re-enter their details.
For subscription businesses, stale card details are one of the biggest sources of involuntary churn, alongside insufficient funds. Unlike insufficient funds, retrying does not help: a charge against an expired card will fail every time until the stored details are fixed.
Why do stored card details go stale?
- Expiry — every card has an expiry date, and charges after it decline.
- Reissue — banks replace cards after fraud, loss or a scheme migration, often changing the card number.
- Account changes — the customer switches banks or closes the account.
The customer usually does not think of their subscriptions when this happens, so the first sign of trouble is a failed billing charge.
What is a card account updater?
Account updater services are run by the card schemes. When an issuing bank replaces or renews a card, the scheme records the link between the old and new details. Merchants and platforms that bill stored cards can then receive updated card numbers and expiry dates for their stored credentials, so recurring charges continue against the new card without the customer doing anything.
Network tokens achieve a similar outcome by design: because the token is maintained by the card scheme rather than being a copy of the card number, it can stay valid when the underlying card is reissued. See card tokenisation and network tokens.
Coverage is not universal — it depends on the issuing bank and scheme participating and on the type of change — so updaters reduce stale-card failures rather than eliminating them.
What is a backup payment method?
A backup payment method is a second stored method the billing system can fall back to when the primary one fails:
- A second card on file, charged when the primary card declines.
- A different method entirely — for example, a debit order mandate as a fallback for card billing, or the reverse.
Fallbacks should be part of the agreed billing terms: the customer should know at sign-up that the backup method may be charged if the primary fails, and each method needs its own valid authority — a card consent for cards, a mandate for debit orders. See minimum mandate requirements.
How do these fit into a recovery strategy?
Account updaters, backup methods and retries solve different failure types:
| Failure | Best response |
|---|---|
| Insufficient funds | Salary-aware retries, or debit order tracking |
| Expired or reissued card | Account updater or network token; otherwise ask the customer to update |
| Hard decline on primary card | Charge the backup method, then contact the customer |
| Closed bank account | Ask the customer for a new account and capture a new mandate |
Debit orders are naturally less exposed to this problem: bank accounts change far less often than cards, and a DebiCheck mandate stays valid until it is cancelled or amended. This is one reason many South African subscription businesses use debit orders as the primary rail and cards as the secondary. See dunning and payment recovery for the full recovery picture.
What should you ask customers to do?
Even with updaters and backups, some failures need the customer:
- Make it easy to update card or bank details from any failed-payment notice.
- Prompt for updated details when a stored card is approaching expiry.
- Offer a once-off payment link to settle the missed amount while the stored method is being fixed.
Related topics
Plan Changes and Proration
What happens to billing when a customer upgrades, downgrades, pauses or cancels a subscription, and how proration and mandate amendments are handled.
Disputes and Compliance
Refunds, chargebacks, debit order disputes, payment fraud, PCI DSS Level 1, KYC, AML and POPIA explained, plus how to respond to payment incidents.