About UsStatus Page
Documentation
Start typing to search…

Token Migration Process

The process for a merchant to migrate their tokens to Stax from a previous payment processor.

Stax can import tokens from a merchant’s previous processor following the steps outlined below. This document provides an overview of the SLA, preparation, and required actions for a successful migration.

SLA

The SLA for token migrations is 7–14 business days from when Stax receives the files, following the steps outlined below.

Preparing for Token Migration

Prerequisites

  1. The merchant must be fully approved and active with Stax.
  2. Submit a separate token file and support ticket for each merchant.

Information to Include in the Support Ticket

  • Processor Information: What processor is the token file coming from?
  • File Transfer Method: Are the tokens sent to Stax’s SFTP or retrieved from the previous processor’s SFTP?
  • Schedule Import Details: Are schedules being imported into Stax Pay or the partner’s payment software?

Key Notes

  1. Submission Requirements:
    • A ticket can only be submitted to the Stax Partner Support team after one of the following:
      • A user instance and Public Key are created (Step 5).
      • Tokens are uploaded to Stax’s SFTP or the previous processor’s SFTP server (Step 6).
  2. Best Practices:
    • Ensure the token file is the most up-to-date version from the previous processor to minimize declines.
    • Merchants processing 50+ transactions per day should request rate limit adjustments to prevent interruptions during migration.
  3. AVS Settings:
    • Stax will match AVS (Address Verification System) settings from the previous processor to minimize declines.
  4. Export Confirmation:
    • Stax provides an export file once the token migration is complete, including separate files for schedule data.
  5. Order of Import:
    • Customer data and payment methods must be imported before schedules and invoices.

Understanding the Previous Processor’s Migration Policies

Partners or merchants should confirm the following with the previous processor:

  • Contractual limitations or restrictions.
  • Payment token migrations allowed? PAN
  • Token migration permissions and associated costs.
  • Data availability, timing, or transfer method limitations.
  • Merchant account access during migration.

Migration Process

Steps

  1. Merchant Tokens:

    • If the merchant holds their tokens (not with the previous processor), skip to Step 4.

  2. Request Export:

    • Contact the previous processor to request a token export (PAN).
    • Files are typically encrypted (PGP) and in JSON or CSV format.

  3. PCI Compliance:

    • Stax’s AOC may be required. Partners can sign an NDA on behalf of the merchant via a support ticket.

  4. Encrypt Files:

    • Use Stax’s Public Key for encryption.
    • Separate ACH and card files.
    • Encrypt files containing payment data (not required for customer-only data).

  5. File Transfer Options:

    • Upload to Stax'sSFTP :
      • Request login credentials through a support ticket, including a Public Key.
      • Use WinSCP for file transfer:
        • Disable timestamp settings in WinSCP.
        • Connect to transfer.staxpayments.com via SFTP.
        • Perform the transfer.
    • Retrieve from Previous Processor’s SFTP :
      • Confirm requirements with the processor.
      • Submit a support ticket with retrieval details.

  6. Support Ticket Submission:

    • Include:
      • Subject: [Token Migration - DBA - PMID].
      • Retrieval method and processor details.
      • Separate tickets/files for each merchant.

  7. Completion:

    • Stax will confirm completion and provide:
      • Customer information.
      • Payment methods.
      • Schedules (if imported).
      • Scheduled payments will continue as normal.
    • An output file will be provided for partner software population.

Resources


Updated 5 days ago