...

Excerpt
Importing Tokens refers to the process of moving tokenized credit card data

Follow this guide for the steps necessary to import your Merchants' tokens to mitigate any interruption to their payment processing

...

capabilities.

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

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

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

How to Import 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.

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

...

–
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).
–
Importing 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 imported tokens (user or merchant).
- Our Import process maps processor Token IDs to new Payrix Token IDs, customers, and custom fields.

.JSON Token Format Sample:

Code Block

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

Tip

You will be notified once the import has been 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.

Anchor

	submission
	submission

Submitting Token Transfers from your Existing Payment Processor

After your existing payment processor has exported your tokens, you’ll need to submit a request to Payrix to import your tokens detailing the merchant you’d like to have access to each token.

To do so, you’ll need to submit the following:

merchant name - the name of the merchant the token will be assigned to.
login ID - determines who will have access to the tokens (Referrer or Merchant).
merchant ID - determines which merchant will be using the tokens.
originProcessor - information about where the token came from, the existing payment processor.
importLevel - determines the level of import used for your custom mapped data, User or Merchant
fileName / fileLink / fileSource - attach, or link the existing token file.

Tip

This information is crucial to our import and custom mapping process. Submitting Login IDs and Merchant IDs, for instance, is important to saving time recalling those tokens in the future.

Without this information, as they will need to be specified per each individual transaction, requiring you to do so each time, where as with your Login and Merchant ID, we’re able to attach them at a Merchant or Referrer level in order to keep them associated for future transactions.

Doing so will provide a seamless integration of existing tokens and minimum downtime during the transfer so you can return to using your customer’s existing payment methods, newly imported to Payrix.

Sample Import Email

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

Info

Hello,

Please complete a token import 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:

Anchor

	pgp
	pgp

Code Block

...

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.

...

Child pages (Children Display)

Versions Compared

Old Version 11

New Version Current

Key

How to Import Your Existing Tokens:

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

3) Processor transfers token data to Payrix

Submitting Token Transfers from your Existing Payment Processor

Sample Import Email

Payrix Public PGP Encryption Key:

4) Payrix imports token data

5) Payrix communicates token import results

Page Comparison

Versions Compared

Old Version 11

New Version Current

Key

How to Import Your Existing Tokens:

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

3) Processor transfers token data to Payrix

Submitting Token Transfers from your Existing Payment Processor

Sample Import Email

Payrix Public PGP Encryption Key:

4) Payrix imports token data

5) Payrix communicates token import results