You can migrate payment tokens from your current (origin) processor to Payrix Pro to maintain your merchants’ payment processing capabilities with minimal disruption. To ensure a smooth transition, coordinate with your existing processor and Worldpay for Platforms Partner Services to securely exchange token data between processors.
To migrate token data:
Contact your origin processor and Partner Experience Manager (PXM) to confirm any pre-migration requirements or documentation.
Request a formal token export from your origin processor.
Compile the token data into a single CSV file.
Encrypt the token file using our public PGP key, following PCI-DSS standards.
Attach the encrypted token file to a Partner Services ticket or provide SFTP credentials for retrieval.
Review the migrated tokens after confirmation from Worldpay for Platforms.
Request a Token Export
To migrate existing tokens, first submit a formal request to the Merchant’s origin processor to extract and transfer tokens to Payrix Pro. The Worldpay for Platforms PCI Attestation of Compliance (AOC) can be provided to your origin processor upon request.
Create a Token Data File
You must submit token data in CSV format, provided by your origin processor.
CSV Token Format Sample
Include the following data columns in your CSV file:
source_customer_id: A custom field used for mapping, if applicable.
source_token_id: A custom field used for mapping, if applicable.
card_number: The customer’s credit card number.
card_type: The type of credit card: Visa, Mastercard, Discover, or American Express.
bank_account_number: The customer’s bank account number.
bank_routing_number: The customer’s bank routing number.
token_expiration: The token expiration month and year (MMYY).
customer_first_name: The customer’s first name as it appears on the credit card.
customer_last_name: The customer’s last name as it appears on the credit card.
customer_email: The email address associated with the customer.
customer_phone: The phone number associated with the customer.
customer_address1: The street address portion of the customer’s billing address.
customer_address2: Additional street address information associated with the customer’s billing address.
customer_city: The city portion of the customer’s billing address.
customer_state: The state portion of the customer’s billing address.
customer_zip: The zip code of the customer’s billing address.
Encrypt Your Token File
Before submitting, encrypt the token file using our public PGP (Pretty Good Privacy) encryption key. If your origin processor hosts the file on an SFTP server, provide credentials to Worldpay for Platforms before submitting your Partner Services ticket to migrate the tokens.
Public PGP Encryption Key
We use a public PGP key to encrypt sensitive token data, ensuring secure, tamperproof transfer from external processors to Worldpay for Platforms.
Use the following public PGP key to encrypt your token file before submission:
-----BEGIN PGP PUBLIC KEY BLOCK-----
mQINBFtWLsQBEAC4fChHoRZWzaRZsbiaGOJuf1uw3WwddiMfuWEJkVhjfr3tdfjX
mCfpqiB78iI3soMTYUpby3Ge9L3WgNidyZ9QcnWnP+6JC1q04U8+lte+yjYzOdgw
fKWetk9lbjGlXQ/0ORVutV2f8VamrEJRQq0zehyqwCCMFjTfT0jSkmL9uG9cKvtI
a/bhbYz201s27NCogDDYxZ+Qj8o2mFm4CM/fvQ+pJPauLu/wtxRsJDrPzIBmgpKD
s8lk/aAt4mnUTLB+4iYwvE7YDG9G6g1V7Jj31J7KDImPEnVruIm5aTTVD/3HPExa
/U1Vk14gCfgR4/3mMaukhbolu0DqFlmXzuXplIo5CGEHWCL0fVg3KL/ocMtHPzEU
Dsk6zH28s7YqYVwnJOX0OogSwWNiTGjR7fCaPtEtPawbQHY5UPKJ+8NShv5abeWf
UZfB232ZPprT53wWYU5ELcgicAIvz7bfr5UOonr28KeLB86Cf6jgCHqsR4uqZDVf
bhh4GJ5fgJfv7DCJ7OMQSOWDfSzfVLJWz2mhvbMR0oELVzt90OEImhYHZda3So+2
ws3VmS4C8/72m1m5UPn5n592Jh1+eOnq7FiIa2roCMQafEwcpQHnk7qcNptMWfz8
1eormZ53UWj2IC1D9LxNMtHSpG8Cf9USGUWP5yzVpczmqCTPC7tTikI/uwARAQAB
tA1wYXlyaXhfc2VjdXJliQJOBBMBCAA4FiEE3nCWHaDvntpm4idFZTx1BjeCUZYF
AltWLsQCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AACgkQZTx1BjeCUZY9Bg/+
LWURdlIDQhl2F49RC21n1DDXcNlHEjS3PLul24BTkSaFBHpBd2othnLQ7KpC8HbV
F4K0uc5FlcV7qHXYXTkZsNki+IXTSC7dtf80uErlNvNxfzKjCuX+b8hLF9C2oaJk
ddIvpRg04YecSRoPUeFP8SnWVTC+wwDczE6hOdpMEL3W4fl/spwm6A6AaB0hjhIS
m6zNZl0vlWFlTnNwujVb24DQMr8GifIPCWcXVu+SY4i895JLWSCKNAd7FBXuGNk4
rm8wD8DY+yWh55zwwomYe/EkLgv98I/RG4A0hNK0r0aGFjJin6S74iZ+TT4TOTOc
edq9dzG6PTSwvAnwxIwF3ID8BsHHxtwzzdTArNUinM2exgYYpei7ttk/1pw7VIFO
dbnVqVdq2lIy9PBLMQxw0XArgesvFXpTjGcu/2+nykIoIcz/sTCU4Q79U0Hex/tJ
4rRu44M0UffnEtPyUl8Sd4fVXzFcHEio+SmjPTvvWvsg9Xs9/1TZaBLn/6y+hU1l
kjbCbF8BtPGvFgirGlNkwQxdzkZ9SUp+V7l1vC9DA1oa535gA/nuQHDKoZpPuymz
nTPETilFbjw1ZEpndZtnxE4wT4zcnQ5ZUi74/fT7HhBfzOj38i+IoKb3Ltjb2vnI
x1B9+K+TTLr5XYWXDOJDBjeOI1ri3C2Psl0zyCchrta5Ag0EW1YuxAEQAM1WL6EW
vJyWzGN8iwzW6vGEyZGAVToGicBTOaMHv5g2fCZz/lyb8mxAE9s5cvk+/w0CMjaT
IS/mfcYdkISjJZVRdLWP/bXv+MgIL4sVTPiNNT4RSWedPDfiUQ2Fks+QWV3NgvND
V8ojMSg17wxO2JXNX489GElcsJ20XUNlzrgfimtyPcNhvOBg21BJ68xwfPT7aoF5
ZHQrT2lzT8M55y0XcHgyih3SiasWTZ+EMZKbmb35MnLcgaMvn3ayfvhKrbladghH
2DpvyRFZPVgF26Z/cKeuns7adGbrzjOFszuFAyVVbzyYn5v34wASjD7F+qm5ykSO
SE2L0EPAtztIrdgGWskeLcFbG0nKHXz96oj5xlYcuMXs0vrtM7SBKPB9v/qegY2d
X1+JXB5vJTcOB3zOOeb3CtoH958W1yImvfQKx/MsnO6h2YFXk9NMJT5OV5DjmWdF
yrlohTCsBbAk0xevgCMZa3mSC7E+fo0sp2BpJ0Hp+U55wYtpzDN1NJR0qdWZWa/n
vA07kGBCFRA7UkC5rvj27LtyUSib8wkh9XSkxJLELjwbgCzG1eH3OIrGtsGXgbtn
4K/4Bh23se7XVjqEFnkN6DUFyhgioeftJ1Wx+TphfjVznUCMaSkDjeAa7AIQ3Fgz
WQ3wJgk7Qz7BMtyO2dqBi0YheHVum6t+4FAfABEBAAGJAjYEGAEIACAWIQTecJYd
oO+e2mbiJ0VlPHUGN4JRlgUCW1YuxAIbDAAKCRBlPHUGN4JRlitzEACK+JGMWaZ3
1w9Aq3x+pWDztnQn8WZnAFiNzNdL8zTZCOT3Ty1Bl5INisz1SDZGnyPRJSjmZRWp
CLHZrkTRhUpxq/2sapcMTT6DnC9X5JcPnomGudBhhOsA0KH7BhgY0G8PTIz91Nbq
Ystt97qb3heobl+x+TyLFiLyHyVfW4QR5cc/SNE+H2y43VFnWhhqlRIUGW0JpUbg
blEmOAOTK8OyjDwM/BwgISAl96ucaDWIhMhFIFnxdnNM3fZ2jjfLKeMGDQzofzhp
iPdV01TfPQ2QVEkrOKZQi1FVSyQrlAZyvoMRdYXe/NZFv1bi8poJ5gO8ceq93CbZ
+fmoaflifZjHs8LqT45MIgn3Lm4+MoIdVuPYiM8qvMr0ZmHp7XkMt8Rm8OjXPlvT
YIMM9dzycff0sjJ7Fwv0L9icGO+3T3plFrOkaHIw2JPoJhhknlfcD5m2meFg9ARd
jdRMnRrBgDEkgnKZ9f3/fYsFJU7EGOkh858oLwUWoVFDML11fH4oUXeAmbE0TJnK
CNgbcsk1Jc8fTgcLMzSRd4gz5moJ0QnmW8U241PfxW0X/2cmMXuaHefCdHkrs7k5
5ISnY9T/u4PUh93evaarUiw8CdHyO2uGJgEMKP8B4wThV/gGdhi7uKEBGi6+RZHk
tx/bUvZN0mR+RQkpkyiGmAAB82wUPpQFEg==
=Y0mE
-----END PGP PUBLIC KEY BLOCK-----Submit Your Token Migration Request
After your origin processor exports the tokens, submit a Partner Services ticket to begin the migration. Include all required details for importing and data mapping.
To initiate a token migration from another payment processor, use the following Zendesk flow:
For Please choose your issue below, select Partner Services.
For Service Requests, select Tokenization Support.
For What type of token request is this?, select Import From Another Payment Processor.
For the Description, provide the following information for each token data file:
Merchant Name: The name of the merchant the token will be assigned to.
Login ID: The Payrix Pro Login ID used to determine which user can access the tokens.
Merchant ID: The Payrix Pro Merchant ID used to determine which merchant can process future transactions with the tokens.
Origin Processor: Information about where the token came from, in other words, the existing payment processor.
Import Level: Defines token access scope: Referrer or Merchant
Referrer: Users with Referrer roles can access the tokens. Use this level to enable token access across multiple merchant accounts.
Merchant: Users with Merchant roles can access the tokens, based on assigned permissions.
File Name / File Link / File Source: The attached or hosted link to the token file.
Provide any other information or documentation as needed.
Click Submit when completed to send your request.
Result: Your token migration request begins processing with Payrix Pro Partner Services, which will contact you with questions or notify you when migration is complete.
Caution
Omitting the Payrix Pro Login ID and Merchant ID can cause migration delays and downtime. If not provided, these IDs must be included with each future API transaction.
Sample Zendesk Migration Request
Use the following format to submit a Partner Services ticket after you receive and encrypt the exported token file from your origin processor:
Subject: Token Migration Request
Description:
Please complete a token migration request for this merchant. See the following token transfer information:
Merchant Name:
Login ID:
Merchant ID:
Origin Processor:
Import Level: Merchant Level
File Name / File Link / File Source:
Data Mapping
After we receive the token file, Worldpay for Platforms processes, imports, and maps the data. We’ll work with you to define the access scope and import level, Referrer or Merchant, for the migrated tokens. During migration, your origin processor’s token IDs are mapped to new Payrix Pro Token IDs, customers, and any custom fields.
Note
Upon request, Worldpay for Platforms can provide a custom mapping file showing how existing processor data maps to new Payrix Pro values.
Review Migrated Tokens
After being notified that your migration is complete, you can use the Payrix Pro portal to review your tokens and identify the new Payrix Pro token values associated with your origin processor’s values.
Locate Customer ID from Origin Processor
To locate the customer ID from your origin processor on the Payrix Pro portal:
Select Customers from the left navigation panel.
Select the relevant customer to open their Customer Profile page.
Review the Custom Description field to view the origin processor’s customer ID.
Locate Token ID from Origin Processor
To locate the token ID from your origin processor on the Payrix Pro portal:
Select Customers from the left navigation panel.
Select the relevant Customer to open the Customer Profile page.
Select Payment Methods from the left profile menu.
Select the relevant token to review the Payment Method details.
Review the Custom Description field to view the origin processor’s token ID.
Use the Payrix Pro API
You can also use the Payrix Pro API to retrieve your migrated tokens by submitting a GET /tokens request.
The token.custom field contains your origin processor’s token ID. The customer.custom field contains your origin processor’s customer ID.
For details on using the Payrix Pro API, access the Worldpay Developer Hub.