Token Migration from other PSP

Summary

Evonet support tokens migration from other Payment Services Providers. This documents provides a high level illustration on this token migration process.

Steps

The token migration process follows a structured five-step sequence involving the Merchant, the existing PSP, and Evonet.

Step	Phase	Description	Owner
1	Initiation	Merchant requests migration from their current PSP. You may specifying merchant name, m, merchant ID, token selection criteria, and Evonet as the receiving PSP. You may also copy the conversation with our destinations Solutions Engineer	Merchant
2	Coordination	The existing PSP may validate Evonet's PCI DSS compliance. Both PSPs agree on encryption (PGP), file formats, and sFTP upload locations.	Existing PSP
3	Export	The existing PSP exports, encrypts, and uploads the tokens to the agreed-upon location.	Existing PSP
4	Import	Evonet imports the tokens into the secure vault and generates a mapping output file.	Evonet
5	Handover	The final output file is shared with the merchant to update their internal database records.	Merchant

Fields Specification

2.1 Fields for Import (PSP to Evonet)

The following fields must be included in the migration file provided by the existing PSP.

PSP Gateway ID (Mandatory)
Primary Account Number (PAN) (Mandatory)
Expiry Date (Mandatory)
PAN Type (e.g., PAN, DPAN) (Mandatory)
Customer Details: Cardholder Name, Customer ID, Email, and Phone Number
Billing Information: Billing Address
Metadata: Recurring Reference

2.2 Fields for Export (Evonet to Merchant)

After a successful import, Evonet provides a mapping file with the following attributes:

PSP Gateway ID (Original identifier)
Evonet Gateway ID (New identifier)
PSP Customer ID
Evonet Recurring Reference

Security & Connectivity

3.1 Encryption Method: PGP

To maintain PCI compliance during transit, all files must be encrypted using PGP:

Key Length: 4096 bits or greater.
Key Hosting: The processor's PGP public key must be hosted over HTTPS on a domain referenced in their AOC or Visa Registry listing.

3.2 Connectivity: sFTP

Data transfer occurs via secure File Transfer Protocol (sFTP):

sFTP Push: The existing PSP uploads (pushes) token files directly to Evonet.
sFTP Pull: Evonet downloads (pulls) token files from the existing PSP’s server.

Setup: Requires configuration of sFTP credentials and authentication protocols.

3.3 Reference:

To locate Evonet is an acquirer of Mastercard, this link could be use.