Vault token import

A token import allows you to migrate your payment data from your current payment provider into the vault. Cards (raw PAN and PSP tokens), digital wallets (Apple Pay and Google Pay), non-card tokens, bank accounts, and gift cards are all supported. To start this process, contact the team. This guide helps you understand the basic principles of the token import process. This process may not be supported by all providers in which case a custom process can be established. The token import process is comprised of the following steps and involves you (the merchant), your original payment service (the PSP), either of which can be the Token holder.

• Token holder creates a token file using the file template and definitions.
• Token holder encrypts the token file created using the public PGP encryption key.
• Token holder uploads the encrypted token file to a cloud-signed storage URL provided.
• The tokens are processed and imported into your instance. Additionally, new buyers and payment methods are created from the token import file.
• A Merchant Advice file is provided that provides you with a log of all the succeeded and failed imports.

​

Before you migrate

• Ask the token holder to include the latest network transaction ID for each card in the token file, as payment_method.scheme_transaction_id. Without it, merchant-initiated transactions on imported cards can’t reference the previous transaction. See Token import file.
• Gr4vy only records refunds, chargebacks, and other updates for transactions that it processed. Updates from your payment service about transactions made before the migration aren’t recorded, so keep handling those at your payment service.

​

Migrating through the API

As an alternative to a token file, the vault that holds the cards can forward each card’s details to the Create payment method endpoint. This creates a stored card for each request. Digital wallet tokens, such as Apple Pay and Google Pay, can’t be created through the API, so import them with a token file.