Skip to main content

Overview

Token migration transfers card numbers from your existing payment processor to Yuno’s secure vault, generating new vaulted_token values for each card. This ensures continuity for your customers. They can keep using their saved cards without re-entering payment information. The process involves three main steps:
  1. You request the data export from your current payment processor.
  2. Yuno collaborates with your provider to securely import card data.
  3. You use Yuno’s API to map provider tokens to Yuno vaulted_tokens.

What Can Be Migrated

Card token migration is the most critical component. It allows existing customers to continue using their saved cards without re-entering card details or going through a new enrollment flow.
Alternative payment methods such as Mercado Pago Wallet Connect or Bancolombia Tokenbox may have technical limitations that restrict migration. Contact Yuno support to assess eligibility before starting.

Step 1 & 2: Importing Cards from Your Gateway

Merchant Responsibilities

You are responsible for:
  • Contacting your current gateway and requesting a payment method data export.
  • Following your provider’s specified export protocols.
  • Managing all communication with the exporting gateway throughout the migration.
  • Obtaining customer subscription information directly from the exporting entity.

Secure Transfer Protocol

All migration data is encrypted using PGP keys and transferred via SFTP (Secure File Transfer Protocol).

Requirements You Must Provide

Generate your SSH key with:

Mandatory Fields in the Migration File

The data export file from your current provider must include these fields for each card:
Yuno does not validate expiration dates during credit card import. Ensure your exported data includes accurate expiry dates to avoid issues with future transactions.

PGP Encryption Key

All sensitive migration data must be encrypted with Yuno’s PGP public key before transfer.

Data Validation Before Import

Before Yuno begins the import, provide the following to Yuno Support:

Step 3: Client-Side Implementation

After Yuno imports the card data, you complete the migration via the Yuno API by adding customers and enrolling payment methods.

Required Data Parameters

Customer Import

Import customer records using the Customers API:

Enroll Migrated Payment Methods

Link migrated tokens to customers by enrolling the payment methods:

How Token Migration Works

Token Mapping File

After migration, Yuno provides a mapping file linking source tokens to Yuno tokens:
Update your database to replace source processor tokens with Yuno tokens using the mapping file. Transactions submitted with old source tokens will fail.

Subscription Migration

Active subscriptions must be recreated in Yuno with the migrated payment method tokens:
  1. Export active subscriptions from your current processor.
  2. Map each subscription’s payment token to the corresponding Yuno token.
  3. Create subscriptions in Yuno with matching billing schedules.
  4. Coordinate the cutover date to avoid duplicate charges.
Schedule subscription migration to occur just after a billing cycle completes at your current processor. This minimizes the risk of duplicate charges and provides a clean transition point.

Data Protection & PCI Compliance

Yuno tokenizes and encrypts all imported card data in compliance with PCI DSS standards. However, as the merchant you remain responsible for:
  • Managing customer data protection in accordance with local regulations.
  • Communicating any fees or issues to your customers during the migration process.
  • Ensuring sensitive data is encrypted before transfer using the provided PGP key.

Migration Timeline

Best Practices

  • Start early: Begin the migration assessment well before your planned go-live date.
  • Run in parallel: Process a percentage of transactions through Yuno while maintaining the old processor as a fallback.
  • Validate thoroughly: Test migrated tokens with real transactions before full cutover.
  • Communicate with customers: Inform customers that their payment experience will not change during the migration.
  • Keep the mapping file: Retain the token mapping file for reference during the transition period.
  • Pre-validate your data: Check for known gaps (missing names, expired cards) before submitting the migration file to reduce iteration cycles.

Exporting Tokens from Yuno

Yuno provides a secure, PCI DSS-compliant process for exporting tokenized card data from its vault to your systems or a third-party provider.

When to Request an Export

You may request a token export when:
  • Switching to a different payment processor or tokenization provider.
  • Managing tokens within your own PCI DSS-certified infrastructure.

Prerequisites

Three requirements must be satisfied sequentially:
1

Formal Request

Submit a written request to your primary Yuno contact and support@y.uno including:
  • Authorization from the third party receiving the data
  • Confirmation of the recipient (internal team or external provider)
  • Legal and compliance approval from your organization
2

PCI DSS Certification

The receiving entity must hold a current PCI DSS Attestation of Compliance (AOC), regardless of whether the recipient is an external provider or your own infrastructure.
3

Technical Requirements

The receiving entity must provide:

Export File Format

Exported files are PGP-encrypted and formatted as CSV with UTF-8 encoding.

Secure Delivery Process

  1. Yuno’s Security Team prepares and encrypts the export file, creates an SFTP user account, and uploads the file.
  2. Notification is sent confirming file readiness, SFTP access details, and the active access window.
  3. You access the SFTP using your SSH key and whitelisted IP, download the file within the defined time window. The file is automatically removed after the window expires.
The file is never sent by email or made publicly accessible. Access is strictly limited to the configured secure SFTP channel.

Security & Compliance

  • Yuno maintains PCI DSS Level 1 certification.
  • All exports are fully logged and monitored.
  • Only authorized personnel handle encrypted data.
  • Files are not stored beyond the required access window.