Preserve Payment History Across a Processor Migration

Use an immutable association from a transaction to its provider

Store the provider, account, and environment on each old transaction before switching checkout. New orders can use a new configuration while refunds and disputes on existing transactions continue to reference the provider that handled them. Avoid looking up an old order using only the gateway currently selected for the storefront.

Create a migration record and exceptions list

List any open authorizations, pending refunds, disputes, subscriptions, or unmatched deposits. Record who owns each item and what should happen after the cutoff. Reconcile the old and new systems using references and date ranges before assuming all transactions have moved.

Give support one reliable starting point

Add a payment history view or documented lookup that identifies the correct provider for each attempt. Keep access to settlement records and statements for the team responsible for historical reconciliation. Confirm retention periods and access with the relevant provider before canceling the prior relationship.

Test old and new records together

• Look up an old refund and a new checkout transaction from the same storefront.
• Check one open dispute and one pending authorization after the cutoff.
• Find a provider-specific record from a finance export using its original reference.