Customer Token Vault provisioning
Understand network tokenization, legacy vault IDs and card updater behavior.
Network tokens and vault identifiers
Customer Token Vault uses network tokenization for Visa and Mastercard in the reviewed source. A Customer Vault ID identifies the saved customer record for later transactions; it is not raw card data. Tokenization does not remove every merchant PCI responsibility.
Provisioning and existing records
The documented onboarding period is 1–3 business days after enablement. Once provisioned, network tokenization applies to eligible transactions, including one-time transactions and recurring activity. Upgrading from legacy Customer Vault preserves existing records and Customer Vault IDs.
Lifecycle and notifications
Network tokens handle tokenized-card updates; Automatic Card Updater can cover non-tokenized vault and recurring records. Network-token creation and update notifications are configured under Settings → Webhooks. The overview does not publish their exact event names or payload schemas; do not invent names from the separate ACU event catalog.