Account Updaters and Card‑on‑File (COF)

Audience: Beginners learning payments

Version: v0.2 (2025‑10‑15)

Author’s note: This consolidates public knowledge.

Executive Summary

Account Updaters deliver updated card credentials (e.g., new PANs, expiries, closures) to acquirers/merchants holding stored credentials, reducing declines and involuntary churn.

• Why it matters
  • Higher approval rates; fewer “Expired/Lost‑Stolen/Closed” declines
  • Preserves subscription revenue; improves customer experience
  • Reduces operational burden of manual refresh campaigns
• Visa recommendation
  • Enable both Real Time VAU (in‑authorization) and Batch VAU (pre‑auth inquiry/response). They are complementary.
• Success requirements
  • Correct Stored‑Credential indicators (CIT/MIT; initial/subsequent) in authorizations
  • Secure, idempotent ingestion process; robust monitoring (coverage, hit rate, approval uplift)

Primer: COF, CIT/MIT, and Indicators

• Credential on File (COF): Merchant or provider stores a credential (PAN or network token) for future use.
• Transaction types
  • CIT: Cardholder‑initiated (payer present; e.g., online checkout)
  • MIT: Merchant‑initiated (payer not present; e.g., recurring, installment, unscheduled COF)
• Indicators matter
  • Networks require specific indicators for stored credentials (initial vs subsequent; initiator; purpose)
  • Real Time VAU eligibility and approval outcomes depend on correct indicators

Visa Account Updater (VAU)

• Purpose
  • Electronic exchange of updated account info among participating issuers, acquirers, and qualified COF merchants
• Solutions (use both)
  • Real Time VAU (RT): Operates within VisaNet; one‑step authorization + update for COF/recurring
  • Batch VAU: Operates outside VisaNet; acquirer submits pre‑authorization inquiry file; VAU returns updates