We help you with a smooth migration from your current payment processor, ensuring uninterrupted business operations.

​
Performing the Import Data Process

  1. Merchant initiates a request to our team for data import
  2. We will share our PCI Attestation of Compliance (AoC) certificate to the merchant
  3. Merchant requests a data export (for both customer records and associated payment data) from their current payment processor, by providing vaultera switch’s PCI AoC certificate
  4. We will provide our public PGP key for the merchant’s current payment processor to encrypt their export data
  5. An encrypted CSV file containing all the export data needs to be sent through SFTP by the merchant’s current payment processor
  6. We will import the data
  7. Post migration of data, we will send updated customer-payment method reference IDs to the merchant

​
Import File Format

The CSV file for import should be formatted in accordance with the following requirements:
  • The first line contains the names of the fields
  • Each subsequent line should contain the fields for a single record
  • Delimit rows by a single newline character \n (not \r\n)
  • Delimit columns by ,
  • Leave empty fields entirely empty (no character in between delimiters). You must not denote a missing field with NULL, N/A, or any other value
  • Fields can’t contain commas or newline characters (\r or \n or ,) within a field
    • Example of what to avoid: 1st Ave\nApt 1
  • All rows must have the same number of columns
  • Field names and values are case-sensitive
  • Multi-line fields are not allowed
  • Save the file in UTF-8 format (to support non-western characters)
  • Encrypt the file using the public PGP key provided by vaultera switch

​
To Import Card Data

​
Required Fields

FieldDescription
card_numberPrimary Account Number (PAN) of the customer card
card_expiry_monthCard expiry month
card_expiry_yearCard expiry year
payment_instrument_idUnique reference ID of payment method saved (PSP token)

Note: This is required for mapping to vaultera switch payment_method_id
original_network_transaction_idOriginal Transaction ID of the first transaction where the customer signed up for recurring payments. For example: Visa - Visa Transaction ID, Mastercard - Mastercard Trace ID.

Note: This is only required for connector agnostic MIT

​
Optional Fields

Note: Billing details are mandatorily required if AVS (Address Verification Service) check is enabled.
FieldDescription
nameName of the customer
emailEmail ID of the customer
payment_methodPayment method used by customer (e.g., card - for cards import)
payment_method_typePayment method type used by the customer (e.g., credit/debit)
card_schemeCard network (e.g., Visa, Mastercard, American Express)
phoneCustomer mobile number
phone_country_codeCountry code of customer mobile number
billing_address_first_nameCustomer first name for billing address
billing_address_last_nameCustomer last name for billing address
billing_emailBilling email ID of the customer
billing_address_line1Street name/Address Line 1 of the billing address
billing_address_line2Locality name/Address Line 2 of the billing address
billing_address_cityCity of the billing address
billing_address_stateState of the billing address
billing_address_zipPostal code of the billing address
billing_address_countryCountry of the billing address

​
Other Payment Methods

To import other payment methods like SEPA, ACH, PayPal, Klarna, kindly reach out to Vaultera Switch@vaultera.in.