Reviewed October 17, 2026. This practical guide replaces an earlier general overview; the original publication date and URL are retained.
A payment-provider exit is incomplete when saved credentials and administrative access remain unaccounted for. A token deletion plan identifies what will be retained for a permitted purpose, what can be transferred through an approved process and what must be removed. Tokenization does not eliminate the need for a documented end-of-service process.
Identify each credential store
List the gateway, platform, vault and integrations that reference payment tokens. Record the purpose, owner and supported deletion method for each. Distinguish the payment credential from the order or accounting record; removing one should not silently destroy the other record the business must legitimately retain.
Resolve migration before deletion
Ask the old and new providers which transfer process is supported and what permissions or customer action are required. Test the approved process with a limited authorized set. Do not delete a source vault merely because a spreadsheet export completed, and do not retain uncontrolled copies as an improvised backup.
Define the closure evidence
Agree on the credential counts, exception handling and confirmation the provider can supply. Identify records retained under contract or applicable obligations and who can access them. A closed billing account is not automatically proof that every token, integration credential and support login has been removed.
Review downstream access after exit
Revoke or rotate the relevant integration secrets through approved procedures and remove staff access to obsolete systems. Check that scheduled jobs no longer call the former service. Keep the exit record with the vendor agreement so a future reviewer can distinguish a deliberate retention decision from an unfinished migration.
Sources and related reading
EMVCo provides background on payment tokenisation. The actual deletion and transfer rights must be verified with each provider and the appropriate security reviewer. Read EMVCo payment tokenisation overview.
Continue with Payment Tokenization: Ask What the Token Protects and Who Controls It and Payment Cybersecurity: Protect Access, Device Changes and Recovery.
Use the AMS New Jersey merchant reading path for the regional operating checklist. Explore related analysis in Eric Kuvykin’s topic guides.
