Account Updater and the Card-on-File Lifecycle

Submitting stored credentials, resolving reissues at the network, and rebilling with fresh card data

Account Updater and the Card-on-File Lifecycle Submitting stored credentials, resolving reissues at the network, and rebilling with fresh card data submit CoF batch PANs, expiries, merchant id query updates new PAN / expiry closed / contact reason codes per credential update responses apply new PAN to vault retry billing authorized Submit batch Resolve updates Apply + rebill Merchant · biller / CoF vault · Sequence participant Merchant biller / CoF vault Updater · VAU / ABU service · Sequence participant Updater VAU / ABU service Network · scheme + issuer · Sequence participant Network scheme + issuer Legend request return security async trace

Why It Exists

  • • Reissued and expired cards silently break recurring charges
  • • Account Updater refreshes stored credentials before they fail
  • • Fewer declines means less involuntary subscription churn

Response Handling

  • • Updated: replace the PAN and expiry in the vault
  • • Closed: stop billing and drop the credential
  • • Contact cardholder: prompt the customer for a new card

The Alternative

  • • Network tokens auto-update without batch submissions
  • • The token stays stable while the underlying PAN rotates
  • • Updater and tokenization together cover more of the base