Library · Payment orchestration · Guide

Vault token migration checklist

GuidePayment orchestrationCalculator on its own page

GuideVault cutover partsBack to article

Tick a row when it is true in writing. Unchecked means re-collect. We invent no portability chip.

A Credential type named per stored cardNetwork token, processor token, or PAN under PCI — not “cards on file”B Written vault export from the leaving gatewayA format the receiving vault said it will ingestC Receiving gateway confirmed ingest in writingNot a sales slideD Live test bill on a migrated tokenBefore you cut traffic. Sandbox import is not a captureE Re-collect plan for tokens that will not moveEmail, checkout wall, or continuity pauseF New card starts a new original-sale chainShopper-present MIT rules still applyG PCI / SAQ change named if PAN movesUpdater on the new seat is not the migration

Missing from the cutover

Holes: Credential type named per stored card, Written vault export from the leaving gateway, Receiving gateway confirmed ingest in writing, Live test bill on a migrated token, Re-collect plan for tokens that will not move, New card starts a new original-sale chain, PCI / SAQ change named if PAN moves.

Tick a row when it is true in writing for this cutover. Unchecked is re-collect. We invent no portability chip.

Pairing procedure: Tokens do not all follow you off a gateway. Topic: Payment orchestration.

GuideTokens do not all follow you off a gateway · How to run thisOpen

Work with us — We run this job on your accounts. Services

Page	Type
Tokens do not all follow you off a gateway	How to run this
Payment orchestration	Topic
MIDs	Related topic
Chargebacks	Related topic
Traffic	Related topic
Subscriptions	Related topic
Payments	Related topic
Retry window headroom	Calculator

Vault token migration checklist

Related