Network Token Migration Process - Yuno API Documentation

Network Token migration is the process of transferring network_tokens from an existing provider to Yuno’s secure vault. During this process, a new token is generated for each network_token, ensuring seamless continuity and security for payment processing. The network_token migration process consists of three main steps:

The merchant requests the network_token migration process from their current payment processor.
Yuno and the payment provider collaborate to securely import all network_token data into the Yuno vault.
The merchant uses Yuno’s token migration API to map the network_tokens from the payment provider to the network_vaulted_tokens of Yuno.

First stepTo initiate the network_token migration process, contact your business advisor at Yuno to assess the viability and schedule of the procedure.

Importing network token from a gateway account (steps 1 and 2)

Importing network_token data from a gateway account involves handling sensitive information, so strict security protocols must be followed. To import network_token data into Yuno from an existing gateway, complete the following steps:

Coordinate with the current gateway: Contact your current third-party vault or gateway and request an export of the payment method data. Ensure you follow their specified protocols.
Complete the formal request: Submit a formal request to Yuno, ensuring all required details and processes are documented. The gateway’s response time and procedures will determine the data transfer process.

Your responsibilities when migrating tokensYou are responsible for managing communication with your gateway provider throughout the migration process. The Yuno team will support and collaborate directly with the third-party vault/gateway to facilitate the importing process. Additionally, the customer subscription information, including amounts, dates, etc., must be obtained directly from the exporting entity, as Yuno will not extract this data from encrypted files.

Data transfer securityAll data throughout the migration process is encrypted using PGP keys and transferred using SFTP (Secure File Transfer Protocol).

Client-side requirements (step 3)

To successfully complete the token migration process, it is essential to fulfill the client-side requirements outlined in step 3. This involves providing the necessary user data, including the buyers and their existing payment methods. You can execute the token migration process using the Yuno API, which is specifically designed for merchants. As a merchant, you will use this API to:

Add customers: Register customers in the Yuno system.
Enroll payment methods: Register payment methods obtained from payment processors for each customer in the Yuno system.

For a detailed guide on performing token migration using the API, click the button below:

Token migration via API

Gateway and payment provider requirements

To proceed with the migration process, you will need to provide the following:

A public SSH key (you can provide one for production and another for testing). You can use the following command to generate it: ssh-keygen -t rsa -b 4096 -C your_email@example.com
The outbound IPs that will be used during the migration.
A template file of the data to be migrated to understand its structure. It must include the following mandatory data:
- Cardholder name: The full name of the cardholder as stored by the current provider.
- Expiration date: The expiry date of the token.
- Network token number: The complete network token number that will be tokenized by Yuno.
- FPAN/Card LDF: Last four digits from the FPAN associated to the card linked to the network token.
- Network token transaction ID: Unique identifier assigned by the card network to a specific transaction made using a network token.
- Parent payment method type: The underlying funding instrument from which a network token originates (such as Apple Pay, Google Pay).
- Provider network token: Unique identifier assigned to each network token by the current provider, used by the client for referencing that network token during transactions.

Important noticeIn case of migration of multiple parent payment method types it is mandatory to send their corresponding network_tokens in different files.

PGP public key

Use our public key to encrypt the PCI-sensitive files you send to Yuno. Email: security-migrations@y.uno Comment: For encrypting sensitive data. Environment: production Created: 22 Nov 2024 Expires: 22 Nov 2026 Key ID: 73D3D88A Length: 4096 Algorithm: RSA Fingerprint: 5160 7134 4C00 D270 93FB C450 19ED AACD 73D3 D88A

Public PGP Key

Production Key

Data Migration Processes

​Importing network token from a gateway account (steps 1 and 2)

​Client-side requirements (step 3)

Token migration via API

​Gateway and payment provider requirements

​PGP public key

Public PGP Key

Importing network token from a gateway account (steps 1 and 2)

Client-side requirements (step 3)

Gateway and payment provider requirements

PGP public key