Export existing tokenized payment information from Payrix if you are migrating to a new payment processing platform.
You can easily submit a request to Support@payrix.com to initiate the process of exporting Merchant tokens to another processing platform. This guide includes what information we need to send token data and what data we will send to the new processor. This process generally takes 1-2 weeks to complete, but this may vary for larger data sets.
Because of the sensitivity of cardholder data, tokens can only be exported directly to a PCI certified payment processor.
Here’s what we need from you to export Merchant token data:
The name of the new processor
A copy of the new processor’s PCI Attestation of Compliance (PCI AoC) which they will provide to you upon request
A PGP encryption key (provided by the new processor) so that we can safely send them the sensitive payment data
We will transfer the data to the processor via a secure FTP server or secure email which the new processor will provide to you upon request
The Payrix Customer ID of the cardholders associated with the tokens being exported. This information helps us track and ensure we are sending the correct tokens to the new processor
Once you’ve sent an export request to Support@payrix.com and included this information, we will encrypt the data using the PGP key provided by the new processor and send it directly to the new processor in .CSV format.
Here’s the data we will send to the new processor:
The Payrix Customer ID of the cardholder associated with the token being exported. This will help the new processor track and map incoming token data.
The Payrix Token ID (the numerical identifier of a token within the Payrix API & platform). This will help the new processor track and map incoming token data.
The actual token, i.e. numerical string with the cardholder’s saved payment data encrypted within.
The first name of the cardholder (i.e. Customer) associated with the token.
The last name of the cardholder (i.e. Customer) associated with the token.
The street address associated with the tokenized payment method.
Line 2 of the street address associated with the tokenized payment method, if applicable.
The (address) city associated with the token.
The (address) province associated with the token.
The postal code associated with the token.
The (address) country associated with the token. By default, this field will always populate with “CAN.”
The cardholder’s (i.e. Customer) phone number, if applicable.
The cardholder’s (i.e. Customer) email address, if applicable.
The saved payment card number associated with the token.
The expiration date for the saved payment card associated with the token.
Here is a sample export file that we will send to the new processor:
The version that is sent will be encrypted.