Importing tokens from another processor to Payrix

Payrix makes it easy to migrate your Merchants from existing old processor to Payrix. Follow this guide for the steps necessary to import your Merchants' tokens to mitigate any interruption to their payment processing capacity.

1) Initiate token migration with your previous processor

A formal request must be submitted to Merchant’s existing processor for tokens to be extracted and transferred to Payrix. Often processors will request the Payrix PCI Attestation of Compliance (AOC) to confirm that the destination for the token migration is PCI compliant which can be provided at the time of the request.

Note: Payrix prefers the following JSON format for token data extract files.

{
	"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": {}
	}]
}

2) Payrix works with the previous processor to coordinate token data transfer

Payrix will work with the previous processor to determine or agree upon a format in which the token data will be extracted, and a process and protocol which will be used to securely transfer the data.

3) Processor transfers token data to Payrix

The token and card data will be transferred to Payrix via industry-standard, PCI compliant transfer protocols by using our public PGP encryption key. This PGP encryption key should be used for all incoming token imports to Payrix:

Payrix public PGP encryption key

4) Payrix imports token data

Upon receiving the token data, Payrix processes, imports, and maps the data.

Payrix will work with you to determine the access scope of your newly imported tokens (user or merchant to which the imported tokens will be associated).
Import process maps processor token IDs to new Payrix token IDs, customers, and custom fields.

5) Payrix communicates token import results

You will be notified once the import has completed, then you can query our API for the existing processor tokens to determine the new equivalent Payrix tokens. Payrix’s token.custom field will contain the existing processor’s token ID, while Payrix’s customer.custom field will contain the existing processor's customer ID.

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