Token Migration Process

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

1. The merchant requests the token migration process to its current payment processor.
2. Yuno and the payment provider collaborate to securely import all card data into the Yuno Token Vault.
3. The merchant uses Yuno's Token Migration API to map the tokens from the payment provider to Yuno's vaulted_tokens.

Importing cards from a gateway account

The token migration process deals with confidential information. Therefore, a secure procedure needs to be followed. To import card data to Yuno from an existing gateway, you need to follow these steps:

1. First, you will communicate with your existing third-party vault/gateway, requesting an export of the payment method data. Follow their specified process and protocols.
2. Review the data format received from the third-party vault/gateway. The data provided to Yuno must follow a specific data format to perform the migration successfully.
3. Submit a formal request to Yuno, providing the environment key where the data will be imported following Yuno's data transfer procedures. The gateway's process and response to the export request will determine the data transfer process.
   • If the gateway requires SFTP setup for the transfer, our PGP key will be shared with them to obtain the necessary credentials. (Note: S/MIME encryption with an RSA key of at least 2048 bits will be used.)
   • If Yuno's SFTP is preferred, we will request the public PGP key of the third-party vault/gateway. The key will encrypt credentials for a Yuno-created SFTP server, where the gateway can drop the exported payment methods for us to retrieve. Ideally, the public PGP key of the gateway should be hosted on a publicly accessible page.

The last step is to execute the migration. At this point, you will provide the user's data (the buyers) and their existing payment methods. Before continuing, you need to choose how to migrate the tokens to Yuno.

Migration options

Currently, you can execute the token migration process using the Yuno API specifically designed for merchant use. As a merchant, you will use this API to:

1. Add customers: Create customers into the Yuno system.
2. Enroll payment methods: Enroll payment methods acquired from payment processors for each customer on the Yuno system.

Access the step-by-step guide on how to perform the token migration using the API using the button below:

Data format

Yuno defines a list of the required parameters for each customer and credit card to proceed with the migration process. The list of the required parameters is present below:

• Account ID
• Merchant customer ID
• First name
• Last name
• Email
• Country
• Document number
• Document type
• Payment method type
• Payment method ID
• Payment method token

You can use the Customer Object and Payment Method Object to find all the possible parameters that can be used when importing/creating customers or enrolling payment objects.

Different technical limitations associated with alternative payment methods may render them ineligible for migration between service providers. Contact the Yuno support team if you're contemplating the migration of alternative payment method tokens, such as Mercado Pago Wallet Connect, Bancolombia Tokenbox, etc., to the Yuno vault.

Data validation

To ensure efficient processing and prevent delays, please include the following information when communicating with Support:

• The external identifier name to be used for the import.
• An approximate count of the expected number of payment methods to be included (a rough estimate is acceptable).
• Any known data gaps, such as missing names or expiration dates.

Data protection

When making payments through Yuno, the platform connects to payment processors. Yuno tokenizes and encrypts the data to ensure data security, simplifying the PCI compliance process. However, you remain responsible for managing and protecting your customer's (the buyer's) data. In addition, you are responsible for communicating any additional fees or other issues to your customer.