Replace eligible stored card numbers with card-network-issued tokens designed for safer, more resilient repeat payments.
NMI Customer Token Vault builds on the familiar Customer Vault by using network tokens issued through supported card networks. The token can stand in for the primary account number during eligible transactions and can receive lifecycle updates when a participating card is replaced or reissued.
VCCP can help confirm processor and card-brand support, enablement requirements and how Customer Token Vault works alongside recurring billing and Automatic Card Updater.
Customer Vault ID vs. Network Token
A Customer Vault ID is the merchant-facing reference used to call a saved payment record without storing the card number in the merchant’s application. A network token is a payment credential generated through a participating card network and restricted to an authorized payment context.
Customer Token Vault lets existing integrations continue using their Customer Vault IDs while NMI manages supported network-token activity behind the gateway workflow.
Potential Benefits
- Reduced card-number exposure: Eligible transactions use a network token instead of the underlying primary account number.
- Lifecycle continuity: Participating networks can update token credentials when a card is renewed or replaced.
- Payment resilience: Current token credentials may help reduce avoidable failures in repeat-payment relationships.
- Issuer recognition: Supported issuers may treat properly used network tokens as a lower-risk credential.
- Existing integration continuity: Merchants upgrading from legacy Customer Vault can retain their current Customer Vault IDs and workflows.
How Network Tokenization Works
- An eligible payment credential enters a supported NMI gateway flow.
- NMI requests a merchant-specific token through the participating card network.
- The network token is associated with the applicable NMI customer or payment record.
- Future eligible transactions use the token through the configured processor.
- Supported network lifecycle events can update the token when the underlying card changes.
Current Card-Network Scope
NMI currently identifies Visa Token Service and Mastercard Digital Enablement Service as supported Customer Token Vault network-token paths. Additional brands may be added over time. A merchant should not assume that every card, processor, region or transaction type will produce or use a network token.
Activation and Configuration
- Confirm that the merchant’s processor supports Customer Token Vault network tokens.
- Allow approximately one to three business days for supported card-network provisioning after enablement.
- Review which supported transaction sources—such as Customer Vault, recurring or subscription activity—are configured for tokenization.
- If multiple processors are configured, select a supported processor where required.
- Test token creation, repeat billing, refunds, reporting and failure handling before relying on the workflow.
Works Alongside Automatic Card Updater
Network-token lifecycle management and Automatic Card Updater are complementary. Network tokens can manage supported tokenized credentials, while Automatic Card Updater can continue working with eligible non-tokenized cards in Customer Vault or recurring systems.
Network-Token Webhooks
Compatible NMI Webhooks can notify an integration when supported network tokens are created or updated. Developers should verify signatures, handle duplicates and design monitoring around the current NMI event schema.
Important Limitations
- Network tokens do not eliminate PCI DSS, privacy, security or card-on-file responsibilities.
- Approval-rate, interchange, fraud and chargeback improvements are not guaranteed.
- Availability depends on card brand, issuer, processor, region, integration and transaction type.
- Some credentials will remain non-tokenized and may still require Automatic Card Updater or customer outreach.
- Merchants must preserve proper stored-credential indicators, customer authorization and recurring-payment records.
Related NMI Tools
- Customer Vault for merchant-facing customer payment references
- Automatic Card Updater for eligible non-tokenized card updates
- Webhooks for supported token lifecycle events
- Fraud Prevention for gateway screening controls
Customer Token Vault Frequently Asked Questions
What is a payment network token?
A payment network token is a substitute credential issued through a participating card network for an authorized payment context. It can be used in eligible transactions without exposing the underlying primary account number.
How is a network token different from an NMI Customer Vault ID?
The Customer Vault ID is the reference a merchant or application uses to identify a stored customer record. The network token is the payment credential managed behind that record for eligible card-network transactions.
Which card networks support NMI Customer Token Vault?
NMI currently identifies Visa Token Service and Mastercard Digital Enablement Service as supported paths. Individual cards, issuers, processors, regions and transaction types may still be ineligible.
Can network tokens update when a customer receives a new card?
Participating networks can provide lifecycle updates for supported tokenized credentials when an underlying card is renewed or replaced. Updates are not guaranteed for every card or account change.
Will Customer Token Vault improve approval rates?
Network tokens may provide security and credential-continuity benefits, and some issuers may recognize them as lower-risk credentials. VCCP and NMI cannot guarantee higher approvals, lower interchange, fewer chargebacks or specific savings.
Does Customer Token Vault replace Automatic Card Updater?
No. Network-token lifecycle management can cover eligible tokenized credentials, while Automatic Card Updater may remain useful for compatible non-tokenized cards. Many merchants may use both services together.
Do merchants need to rebuild their Customer Vault integration?
Existing integrations may continue referencing the same Customer Vault IDs while NMI manages supported network tokens behind the workflow. Enablement, processor support and testing should be confirmed before relying on that approach.
Modernize Stored Credentials Without Rebuilding the Checkout
Tell VCCP which processor, Customer Vault workflow and recurring system you use. We can help determine whether Customer Token Vault can be enabled without changing the merchant-facing integration.
Network-token availability, provisioning, lifecycle updates, pricing and transaction treatment depend on the card network, issuer, processor, integration and NMI configuration. VCCP does not guarantee approvals, savings or fraud outcomes.