Payment Token Migration into Ordway Payments

Contents

• Overview
• How the Migration Process Works
  • Step 1: Notify Ordway
  • Step 2: Contact Your Current Payment Provider
  • Step 3: Existing Processor Coordinates with Adyen
  • Step 4: Adyen Imports the Tokens
• Recommended Preparation
• What Ordway Handles
• Migration File Requirements
• Card Migration Requirements
• Network Transaction References
• ACH Migration Requirements

Overview

Ordway Payments supports secure migration of stored payment credentials through our payment infrastructure partner, Adyen.

In most cases, token migration is performed directly between your current payment provider and Adyen using secure PCI-compliant transfer procedures.

This allows your customers saved payment methods to continue without requiring card re-entry.

How the Migration Process Works

Step 1: Notify Ordway

Inform the Ordway Payments onboarding team that you would like to migrate stored payment methods.

Ordway helps:

• Assess migration eligibility
• Identify supported payment methods
• Coordinate migration timelines
• Initiate the Adyen migration request

Step 2: Contact Your Current Payment Provider

Request a token migration export from your current processor or token vault provider.

Most providers have a formal:

• Vault migration
• Token portability
• Payment data transfer

Important Security Note

For PCI compliance reasons:

• Raw card data is usually not shared with Ordway.
• Migration is generally performed directly between your current processor and Adyen (Example: Stripe, Braintree etc.,)
• Adyen manages the secure token import process
• Ordway does not directly receive or process unencrypted PAN or card export files during migration.

Step 3: Existing Processor Coordinates with Adyen

Your existing payment provider will typically:

• Coordinate directly with Adyen’s migration team
• Securely transfer payment credentials
• Provide network token references where supported
• Transfer recurring payment metadata

This process may involve:

• PGP-encrypted files
• Secure SFTP transfer
• PCI-compliant exchange procedures

Step 4: Adyen Imports the Tokens

After the data transfer is completed:

• Adyen imports the recurring payment details.
• New recurring tokens are generated.
• Tokens become available within Ordway Payments.
• Subscription billing can continue uninterrupted.

Recommended Preparation

Before migration:

• Clean up inactive or expired payment methods.
• Remove duplicate customer records. if applicable.
• Standardize customer IDs.

What Ordway Handles

Ordway helps coordinate:

• Migration readiness reviews
• payment mapping
• Cutover planning
• Post-migration validation

Ordway also provides a stable shopper reference to map the received token details to the correct shopper reference.

Migration File Requirements

The migration of payment methods requires payment data in CSV format.

File Requirements

The files containing the data to be imported must meet the following requirements:

1. Create a file in CSV (Comma Separated Values) format as defined by RFC 4180, in accordance with the following requirements:
   • The first line must contain the field names. 
   • Field names do not need to follow the same order listed in this article.
   • Each subsequent line must contain fields for a single recurring contract. 
   • If a field does not apply to the recurring contract, leave the value empty.
   • Field names and values are case-sensitive.
   • Multi-line fields are not allowed.
   • The maximum file length is 1,000,000 lines.
   • The maximum file size is 1 GB.
2. Save the file in UTF-8 format (to support non-western characters).
3. Encrypt the file using the PGP public key provided to you by Adyen. For more information, see PGP encryption documentation.
4. Send the encrypted file to Adyen.

File Specification

Card Migration Requirements

The migration file typically includes the following fields

Example Migration File

Network Transaction References

Ordway Payment's backend processors strongly recommend including network transaction identifiers for Visa and Mastercard migrations.

These references help:

• Maintain stored credential continuity,
• Reduce soft declines,
• Improve recurring authorization success rates.

ACH Migration Requirements

When specifying ACH payment details, provide all the following fields.