# Card Account Updater: saved cards that update themselves

Orchestrapay keeps saved cards current when banks reissue them. Cards in your
vault are checked with Visa Account Updater (VAU) and Mastercard Automatic
Billing Updater (ABU), and new numbers and expiry dates are stored before the
next charge.

Page: https://www.orchestrapay.com/products/card-account-updater

## What it does

- **New expiry dates** are written to the vault ahead of the next charge.
- **Replacement numbers** for lost, stolen or upgraded cards are stored against
  the same saved card.
- **Closed accounts are flagged** so you ask the customer instead of retrying.
- **Updated in your vault**, not in one processor's copy, so every processor you
  route to gets the current card.
- **No integration work.** Saved cards and API calls stay the same.

## What the updater can tell you

1. New expiry date: stored, the next charge goes through.
2. New card number: vaulted against the same saved card and customer.
3. Account closed: flagged, stop retrying and ask for a new card.
4. Contact the cardholder: the issuer has no update; you know before the renewal.

## FAQ

**Do I need the updater if I use network tokens?** They work together. Tokens
follow reissued cards automatically; the updater covers cards that are not
tokenised and reports closed accounts.

**Does my customer need to do anything?** No.

## Related

- [Network Tokens](https://www.orchestrapay.com/products/network-tokens.md)
- [Card Vault](https://www.orchestrapay.com/products/card-vault.md)
- [Recover renewals & reduce churn](https://www.orchestrapay.com/solutions/recover-renewals.md)
- [Talk to sales](https://www.orchestrapay.com/contact)