Skip to main content
Token Migration Guide

Migrating payment tokens from your current payment processor to Valpay.

Kristian Clinton avatar
Written by Kristian Clinton
Updated over a month ago

Migrating payment tokens from your current payment processor to Valpay is a critical process that ensures the continuity of recurring payments and enhances customer experience. Below is a step-by-step guide to facilitate this migration:

1. Preparation

  • Data Compilation: Gather all necessary payment data from your existing processor. This typically includes customer identifiers, payment tokens, card details (masked PANs), expiration dates, and any associated metadata.

  • Data Format: Ensure that the data is structured in a CSV (Comma Separated Values) format, adhering to RFC 4180 standards. The first row should contain the field names, followed by rows representing each recurring contract.

2. CSV File Structure

Your CSV file should include the following fields:

  • recurringReference: Unique identifier for the recurring contract.

  • shopperReference: Unique identifier for the customer.

  • shopperEmail: Customer's email address.

  • cardBin: First six digits of the card number.

  • cardSummary: Last four digits of the card number.

  • expiryDate: Card's expiration date in MM/YYYY format.

  • contractType: Type of recurring contract (e.g., "RECURRING", "ONECLICK").

  • currency: Transaction currency code (e.g., "USD", "EUR").

  • creationDate: Date when the recurring contract was created.

  • name: Cardholder's name.

  • variant: Payment method variant (e.g., "visa", "mc").

  • additionalData: Any extra information relevant to the contract.

3. Data Security

  • Encryption: Before transmitting the CSV file, encrypt it using PGP (Pretty Good Privacy) to ensure data security during transfer.

  • Compliance: Ensure that the migration process complies with PCI DSS (Payment Card Industry Data Security Standard) requirements to protect cardholder data.

4. Submission to Valpay

  • Contact Valpay: Reach out to Valpay's migration team via [email protected] to inform us of your intent to migrate and to receive specific instructions or requirements we may have.

  • File Transfer: Use a secure method, as advised by us, to transmit the encrypted CSV file. This could be through a secure FTP server or another secure file transfer protocol.

5. Validation and Testing

  • Confirmation: After submission, we will process the migration file and provide an output file detailing the results, including any errors or issues encountered.

  • Testing: Conduct thorough testing to ensure that the migrated tokens function correctly within Valpay's system. This includes processing test transactions and verifying successful authorization and settlement.

6. Go-Live

  • Monitoring: Once the migration is complete and tested, monitor the transactions closely during the initial phase to promptly address any anomalies.

Additional Considerations

  • Communication: Keep your customers informed about the migration, especially if there are any actions required on their part or if they might notice changes in their billing statements.

  • Support: Ensure that your customer support team is prepared to handle any inquiries related to the migration.

By following these steps and collaborating closely with our support team, you can achieve a seamless transition of payment tokens, ensuring uninterrupted service for your customers.

Did this answer your question?