How do I transfer tokens from my old processor to Payrix?

The general process for extracting tokens from another processor (“processor”), importing them into Payrix, and instructing partners on how to utilize newly imported tokens.

1) Initiate token migration with your previous processor

A formal request must be submitted to your old processor for tokens to be extracted and transferred to Payrix. Often processors will request the Payrix PCI Attestation of Compliance to confirm that the destination for the token migration is PCI compliant.

{
	"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": "0",
		"email": "customer@gmail.com",
		"id": "cus_CustomerIDValue",
		"metadata": {}
	}]
}

2) Payrix works with 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 using industry standard, PCI compliant encryption and transfer protocols.

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 old processor tokens to determine the new equivalent Payrix tokens. Payrix’s token.custom field will contain the old processor’s token ID, while Payrix’s customer.custom field will contain the old processor's customer ID.

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