Store payment credentials securely with NMI and use a customer reference for future eligible transactions.
NMI Customer Vault tokenizes eligible payment information and stores it within NMI’s payment infrastructure. The merchant’s application receives a unique Customer Vault ID that can be referenced for later transactions instead of storing or repeatedly collecting raw card details.
VCCP can help determine whether a vault-based workflow fits your business, then coordinate the compatible NMI gateway, processor, merchant account and integration requirements.
How Customer Vault Works
- Eligible payment information is captured through a compatible NMI payment flow.
- NMI tokenizes and stores the sensitive payment credentials within its infrastructure.
- The merchant receives a Customer Vault ID that identifies the stored customer record.
- For a permitted future charge, the merchant submits the Vault ID and required transaction details instead of raw payment credentials.
- NMI retrieves the stored information and routes the transaction through the configured processor and merchant account.
Common Customer Vault Uses
- Returning-customer and saved-payment experiences
- Subscription and recurring-billing workflows
- Merchant-initiated charges that follow applicable stored-credential requirements
- Future or scheduled payments
- Compatible invoicing, account-on-file and customer-management applications
Customer Token Vault and Network Tokens
NMI also offers Customer Token Vault, an enhanced option that may use payment-network tokens for eligible cards and configurations. Network tokens replace underlying card credentials with payment credentials issued through participating card networks. This can add lifecycle-management and security benefits, subject to card brand, processor, merchant and configuration support.
Standard Customer Vault records, Customer Token Vault and Automatic Card Updater are related but distinct tools. VCCP can help confirm which services are available and appropriate for the merchant’s recurring or card-on-file workflow.
Important Implementation Considerations
- Customer authorization: Merchants need appropriate permission and disclosures before storing or reusing payment credentials.
- Stored-credential rules: The application must correctly identify initial and subsequent customer- or merchant-initiated transactions when required.
- PCI responsibility: Tokenization can reduce exposure to sensitive payment data, but it does not eliminate the merchant’s PCI DSS responsibilities.
- Security and access: Vault IDs, API credentials and administrative access still require appropriate protection and controls.
- Compatibility: Available payment types, wallet support, network tokenization and update services depend on the gateway, processor, integration and merchant configuration.
Related NMI Tools
- Collect.js for compatible existing website tokenization integrations
- Collect Checkout for hosted checkout pages, links and buttons
- Automatic Card Updater for compatible card-on-file updates
- Electronic Invoicing for compatible invoice-payment workflows
- Webhooks for compatible vault and payment event notifications
NMI Customer Vault Frequently Asked Questions
What is NMI Customer Vault?
NMI Customer Vault is a tokenized storage service for eligible customer payment credentials. It returns a unique Vault ID that a compatible application can reference for authorized future transactions instead of storing raw card data.
Does Customer Vault store the actual card number?
NMI stores the underlying eligible payment credential within its payment infrastructure. The merchant normally works with a reference ID or token, helping reduce direct exposure to raw card data.
Can Customer Vault be used for recurring payments?
Yes, in an approved and correctly configured workflow. The merchant still needs customer authorization and must follow applicable stored-credential, recurring-billing, cancellation and card-network requirements.
Does tokenization eliminate PCI DSS requirements?
No. Tokenization can reduce exposure to payment data and may simplify parts of the environment, but the merchant and integration still have PCI DSS responsibilities.
Can a Vault ID be used with another payment gateway?
Usually not as a portable substitute for the original card credential. Vault records are tied to the gateway and configuration that created them, so migration options should be reviewed before changing providers.
What is the difference between Customer Vault and Customer Token Vault?
Customer Vault uses gateway tokenization and a stored customer reference. Customer Token Vault may add eligible payment-network tokens, which can provide additional lifecycle-management and security benefits when supported.
Can Customer Vault store ACH payment information?
Eligible bank-account information may be supported when the gateway and an approved electronic-check or ACH processor are configured accordingly. Availability and permitted uses depend on the merchant’s program.
Plan a Secure Card-on-File Workflow
Tell VCCP how customers pay today, whether charges are one-time or recurring and what software needs access to the stored-payment workflow. We can help evaluate Customer Vault and related NMI services while coordinating the compatible merchant-services setup.
Product availability, pricing, card-brand support, processor compatibility, integration options and approval depend on the business, gateway configuration, merchant account and underwriting. VCCP does not guarantee PCI scope, approval or availability of a particular configuration.