Migrate Tokens from Another Processor to Payrix

To ensure a smooth transition and prevent any disruption in your Merchants' payment processing capabilities, please follow this comprehensive guide outlining the necessary steps to migrate their tokens.

Token Migration requires coordination with the existing processor and Payrix operational teams.

Merchant Token Data Migration Requirements

Here’s what we need from you to migrate Merchant token data:

A formal request has been submitted to your existing payment processor to extract and transfer tokens to Payrix
Set up a token data transfer/export (in .JSON format) with your existing payment processor.
The entity level(s) for each of your existing tokens (user or merchant).

Migrate Your Existing Tokens

Token Transfer Request:
A formal request must be submitted to the Merchant’s existing processor to extract and transfer tokens to Payrix.

Existing processors often request the Payrix PCI Attestation of Compliance (AOC), which can be provided at the time of the request.
–
Formatting Tokens for Transfer:
Your existing token information should be submitted to Payrix in .JSON format (right) from your existing payment processor.
–
Submission of Existing Tokens:
Submit token and card data to Payrix using our public PGP encryption key (below).
–
Migrate and Mapping Data with Payrix:
Upon receiving the token data, Payrix processes, imports, and custom maps the token data.
- Payrix will work with you to determine the access scope of your newly migrated tokens (user or merchant).
- Our migration process maps processor Token IDs to new Payrix Token IDs, customers, and custom fields.

.JSON Token Format Sample:

CODE

{
	"customers": [{
		"cards": [{
			"address_city": null,
			"address_country": null,
			"address_line1": null,
			"address_line2": null,
			"address_state": null,
			"address_zip": null,
			"exp_month": 12,
			"exp_year": 2021,
			"id": "card_CardTokenIDValue",
			"name": null,
			"number": "4111111111111111"
		}],
		"default_source": "card_CardTokenIDValue",
		"description": "",
		"email": "customer@gmail.com",
		"id": "cus_CustomerIDValue",
		"metadata": {}
	}]
}

You will receive a notification once the migration is complete. After that, you can query our API to retrieve the existing tokens and identify their new equivalent Payrix tokens.

Payrix’s token.custom field will store the token ID of the existing processor, whereas Payrix’s customer.custom field will hold the customer ID associated with the existing processor.

By request, Payrix can provide a custom mapping file with the existing processor data mapped to the new Payrix values.

Submitting Token Transfers from your Existing Payment Processor

Once your current payment processor has exported your tokens, the next step is to submit a request to Payrix for token migration. In this request, you should specify the merchant associated with each token you wish to access.

To proceed, please ensure that you provide the following information:

Required Information
Merchant Name	The name of the merchant the token will be assigned to.
Login ID	Payrix User ID. Determines who will have access to the tokens (Referrer or Merchant).
Merchant ID	Payrix Merchant ID. Determines which merchant will be using the tokens in future transactions.
Origin Processor	Information about where the token came from, the existing payment processor.
Import Level	determines the level of import used for your custom mapped data, User, or Merchant
File Name / File Link / File Source	Attached or linked existing processor token file.

This information is vital for our import and mapping process. Submitting your Login and Merchant IDs upfront saves time when recalling these tokens later. If not provided, you'll need to specify them for each transaction, which is time-consuming. Using your Login and Merchant ID allows us to link this information at the Merchant or Referrer level, streamlining future transactions. This approach facilitates the integration of existing tokens and minimizes downtime during the transfer, enabling quick use of your customers' payment methods now migrated to Payrix.

Sample Migration Email

Please see the sample email attached. We recommend using this email format to submit tokens from your existing processor to Payrix.

Hello,
Please complete a token migration request for this merchant. Token transfer information is below.
merchant name:
login ID:
merchant ID:
origin Processor:
import Level: Merchant Level
file Name / file link / file source:

Payrix Public PGP Encryption Key:

To ensure the secure transfer of merchant payment tokens from an external payment processor to Payrix, we utilize a Public PGP (Pretty Good Privacy) encryption key. This key is used to encrypt sensitive data, ensuring that it remains confidential and tamper-proof during the migration process.

CODE