Batch File

On this page, you will find a walk-through guide on migrating tokens using batch files. After completing the guide steps, you will have a list of customers with enrolled payment methods in their accounts.

Requirements

Before starting following the steps described in this guide, you need to:

Have concluded the three steps related to the importing cards from a gateway account process.

Ensure to have concluded the steps before following the guide.

Migrate tokens via batch file

Step 1: Share the customer data

To initiate the process, you will need to provide Yuno's team with customers' data in CSV format. These files should include customers' personal information and the external token used by the current payment provider. The table below outlines all the essential standard parameters that should be included in the CSV files and their respective descriptions.

Parameter	Description
`account_id`	The unique identifier of the account.
`merchant_customer_id`	The unique identifier of the customer in the external merchant.
`first_name`	The customer's first name.
`last_name`	The customer's last name.
`email`	The customer's e-mail.
`country`	The customer's country.
`document_number`	The customer's document number.
`document_type`	The customer's document type.
`type`	The payment method type.
`id`	The unique identifier of the payment provider. For example, dLocal.
`payment_method_token`	The payment method token for the provider specified in id.

Step 2: Tokenize the customer information

Yuno is responsible for executing this step. After receiving the CSV file, Yuno will asynchronously tokenize the card data from the third-party payment providers through the batch process. As a result, customers will be created, and payment methods will be enrolled in their accounts. In addition, Yuno will generate a GPG-encrypted CSV file with all generated data.

Step 3: Receive the migration results

After tokenizing the payment methods and enrolling the respective customers' accounts, Yuno will return a CSV file containing all the process resulting information. The file will provide the information received in Step 1, along with a unique customer_id assigned by Yuno and a token_ID (payment_method_id) for each payment_method_token provided.

The Yuno shared data enables unique identification and referencing of customers and payment methods for future transactions. The data description and parameters in Yuno's CSV are listed below.

Parameter	Description
`merchant_customer_id`	The unique identifier of the customer in the external merchant.
`first_name`	The customer's first name.
`last_name`	The customer's last name.
`email`	The customer's e-mail.
`country`	The customer's country.
`document_number`	The customer's document number.
`document_type`	The customer's document type.
`type`	The payment method type.
`id`	The unique identifier of the payment provider. For example, dLocal.
`payment_method_token`	The payment method token for the provider specified in id.
`customer_id`	The customer's unique identifier.
`payment_method_id`	The unique identifier of the `payment_method`.