Skip to content

Platform modules

Credit Card Vault for PSPs: Tokens, Storage and Migration

A credit card vault keeps card numbers in one encrypted store and gives the rest of your platform a token in their place. Your merchants charge returning customers with that token, your routing passes it toward the acquirer, and the card number itself never leaves the vault's PCI DSS boundary until the payment goes out.

Our gateway platform has a credit card vault built in, with card tokenization, network tokens for stored cards and PCI DSS Level 1. Below, you'll see what the vault does, how a stored card gets charged, where PCI scope sits, and how a card book moves in from another provider or back out to you.

What the card vault does

At the moment of payment, the vault takes the card number and stores it in an end-to-end encrypted system. The merchant gets back a token that only works inside the platform, so a leaked token can't be used as a card somewhere else.

Merchants then put stored cards to work in a few ways, all on the same token.

  • One-click payments for returning customers, without typing the card again
  • Subscriptions on a flexible billing schedule, with retries when a charge fails
  • Repeat charges the merchant starts, such as account top-ups on a card on file

Stored cards are kept up to date automatically, so a card the bank reissues after expiry doesn't break the next subscription charge.

How a stored card gets charged

A card enters the vault on its first payment, and every later charge starts from the token. Here's the path a returning customer's payment takes.

  1. The shopper enters card details on the hosted payment page or in the SDK's embedded fields, served on your domain.
  2. The card number goes straight to the vault, which stores it encrypted and returns a token.
  3. The merchant saves the token against the customer record instead of the card number.
  4. For the next charge, the merchant sends the token and the amount through the API.
  5. The platform swaps the token for the card details only when it sends the payment to the acquirer your routing rules picked.

Since the swap happens at the last step, fraud filters, routing and reporting all run on tokens. Routing can also send a stored card to a different acquirer without asking the customer to type it again.

Network tokens for recurring payments

A network token is issued by the card scheme in place of the card number and belongs to the token requestor that asked for it. When the bank reissues a card, the scheme updates the network token, so recurring payments keep charging without new details from the customer.

Each payment on a network token also needs a fresh cryptogram, a single-use value that only the token requestor behind that token can issue. That's why network tokenization is the part of a card book that needs the most care when it moves between platforms, which the migration section below comes back to.

PCI DSS scope and where the vault runs

Where the vault runs decides who certifies it. The table shows the three deployment options and the PCI DSS split for each.

Where the vault runs Time to start PCI DSS for the vault
Our SaaS 5 business days on average Covered by our PCI DSS Level 1 certification
Your AWS, Azure, Google Cloud or Oracle Cloud account About 30 days You certify your environment, and we support the audit
Your own servers About 60 days You certify your environment, and we support the audit

Running the vault on your own infrastructure keeps stored cards in an account or data center you control. Licensed PSPs and banks in seven Middle East markets, Saudi Arabia, Qatar and the UAE among them, run the platform on-premises under supervisors such as SAMA and QCB.

Merchants keep their own PCI DSS obligations in every case. A merchant that takes cards only through the hosted page or the SDK fields keeps card numbers off its own servers, which is usually what keeps its PCI DSS assessment small.

Moving stored cards into the vault

Most PSPs already hold stored cards with another provider when they switch. What can move depends on the kind of token behind each card, as the table sets out.

Token type What has to move Why
Acquirer tokens The tokens and the MID data they were created under They're encrypted with the acquirer's keys and tied to one MID; recurring ones also reference the first transaction
Customer tokens The payer ID, the payer's data and the card number Providers such as Stripe and Adyen send this in bulk, encrypted with PGP keys
Network tokens The tokens and an integration with the token requestor Every payment needs a new cryptogram from the requestor that created the token

Records are half the job. The cards also need connectors to the acquirers and payment methods they were created against, or a recurring book arrives complete and still can't be charged. With 700+ connectors already built, that gap is usually small, and a missing connector takes about 14 days.

Mapping migrated tokens

Each migrated token is mapped in one of two ways. The platform either stores the acquirer tokens so the merchant submits them as they are, or it creates its own tokens linked to the acquirer tokens, and the merchant sends ours while the platform looks up the acquirer token at payment time. Subscriptions then get a billing schedule, so every migrated card keeps charging on its old cycle.

Getting your cards back

Your card data stays yours. If you leave, it's handed back via PGP or another encrypted method on request, and the transfer is checked against PCI DSS whichever way the cards move. Ask any credit card vault you compare the same question, and get the answer in writing before the first card goes in.

Who the card vault is for

A credit card vault on our platform suits PSPs and ISOs whose merchants sell subscriptions, store cards for one-click payments or charge cards on file. It also fits banks and licensed PSPs that need stored cards inside their own data center, and payment businesses moving a card book off another provider without asking customers to re-enter their cards.

Questions

What is a credit card vault?

It's a secure store that keeps card numbers encrypted and gives the rest of your systems tokens in their place. Merchants charge stored cards with the token, and only the vault can turn it back into card details when a payment goes to the acquirer.

What's the difference between card tokenization and a vault?

Card tokenization is the swap of a card number for a token. The vault is where the card numbers sit, so the swap can be reversed at payment time. Network tokenization is a separate layer, where the card scheme issues its own token, and the platform holds those for stored cards as well.

Can I migrate stored cards from Stripe or Adyen?

Customer tokens, yes. Both providers hand card data over in bulk, encrypted with PGP keys, and the cards are then mapped to new tokens. Acquirer tokens also need their MID data, and network tokens need an integration with the token requestor that created them.

Does the vault hold merchants' funds?

No. It stores card data, not money. Our platform is payment software and stays out of the funds flow, so settlement runs through your acquirers and banks.

See the vault on your own setup

Tell us how your merchants store and charge cards today, and we'll show tokenization, network tokens and a migration plan for your card book.