Vault
Customer Vault storage
The Customer Vault is a secure database that allows merchants to store sensitive billing details, including credit card and bank account information. These details are referenced using a token known as a Customer Vault ID.
Because the Vault ID contains no sensitive data, it can be safely stored in unsecured environments—such as non-SSL websites or desktop applications—without risk of exposing payment information.
Merchants can use Vault IDs to process both one-time and recurring transactions directly from their own software, eliminating the need to rely on ChargX built-in recurring billing module—a common approach for larger organizations.
FAQ
What is the difference between Recurring and the Customer Vault?
Both Recurring and the Customer Vault are storage-based systems, but they serve different purposes. The Recurring module is designed to automatically process transactions on a predefined schedule, while the Customer Vault is strictly a secure storage mechanism and does not initiate transactions on its own.
A Customer Vault ID can remain inactive indefinitely without being modified, deleted, or used. Vault IDs do not have an expiration date; however, the underlying payment details stored within them—such as a credit card—may expire over time.
Can merchants create their own Customer Vault IDs, or must they use system-generated ones?
Merchants must rely on system-generated values.
Can CVV numbers be stored in the Customer Vault?
No. Visa and other card networks prohibit merchants from storing CVV codes. Although CVV may be provided for the initial transaction, it is never stored in the Customer Vault.
How can a merchant store payment details in the Customer Vault if a CVV is required for the initial transaction?
Due to Visa regulations, merchants are not permitted to store CVV values in the Customer Vault. If a merchant account is configured to require CVV verification on the first transaction, the merchant must process an initial transaction that includes the CVV.
After the transaction is completed, the system records that the card has successfully passed CVV validation. At this point, the card can be stored without retaining the CVV, as future transactions will reference the verified Vault ID instead.
API integration
Refer to Create Vault API request documentation how to store customer card into Vault.