Migrating Cards on File to VGS
Overview
The following document describes best practices for creating card objects in VGS when the customer currently has access to the card information, either in raw or VGS-aliased format.
Delivering Cards to VGS
VGS will set up an SFTP Server and provide access credentials to the existing provider's point of contact.
The vault provider will export the card data in CSV format.
VGS can support receiving card data in any common file format. Most payment service and vault providers have a pre-defined format for exporting card details. However, if there is no existing format for the source of the file, VGS provides a sample file that includes all the data that is required to import the cards into a VGS Card Management account. You can download this a sample of this file here.
In the case that card PANs are included in the file, the existing provider will encrypt the file using VGS’s PGP key.
The customer will upload the encrypted file to VGS’s SFTP Server.
Importing Card Records
VGS will decrypt the file and create a “Card ID” for each record.
VGS will deliver a “Results File” to the SFTP Server that contains the columns below. A sample of this file can be found here
original_token
card_id
card_fingerprint
pan_alias
expiry_year
expiry_month
token_type
job_trace_id
file_name
error
Enabling Card Services
VGS can enable the desired services for individual cards.
VGS can either enroll all cards in the system, or you can specify which cards should be included in which services. If this is the case, please coordinate the limiting criteria with VGS before the service is enabled on the account. For example, you may only desire cards newer than 12 or 18 months to be included in certain services.
Reviewing Results
VGS will inform the customer when the enrollment process is complete.
The customer can see the full list of cards and associated services using the VGS Card Management Dashboard. See below for an example.
Last updated