Eric Kuvykin

By Eric Kuvykin. Substantially revised October 17, 2026. The original publication date and URL are retained.

Define two jobs for the migration

A payment-vault change must address future charges and service for earlier transactions. Those are separate jobs. A merchant may successfully move an eligible saved credential while still depending on the former provider to locate or refund an old sale.

Begin with a transaction map showing the current vault, payment provider, order system and proposed replacement. Ask both providers which token types and historical references they can support. EMVCo’s tokenisation resources provide technical background; the actual migration plan must come from the parties implementing it.

Create a historical-service inventory

List the records required for refunds, disputes, receipts and customer inquiries. Identify where each remains after cutover and how authorized staff can access it. Do not assume an exported token ID lets a new provider act on an old transaction.

Include open orders, future appointments and active recurring instructions. Record which system will own each after the change. Keep cancellation and credential-removal requests connected to the correct system so an unresolved handoff does not lead to a later unwanted billing attempt.

Test the awkward timing cases

Use approved sample cases for a sale before cutover and a refund after cutover, an order adjusted during migration and a customer updating a saved method. Inspect both the customer confirmation and accounting entries. Mark unsupported cases explicitly.

For a Florida service business with seasonal staffing, ensure the post-cutover team can find the old transaction reference without borrowing a former employee’s account. Use controlled access and a short escalation guide. The scenario addresses continuity rather than a special state token requirement.

Set a closure condition for the old relationship

Ask which obligations, reports and service needs remain after new sales move elsewhere. Review retention, access and termination terms with appropriate advisers. Do not close an account solely because the new checkout has processed one successful test.

Keep a cutover log identifying the event, responsible provider, result and unresolved exception. Reconcile the transition period before declaring the project complete. A migration is easier to supervise when every unfinished case has an owner and the business can still explain a historical payment.

Review the log after the first full reporting cycle. The successful outcome is continuity for customers and staff, with clear boundaries around what moved and what still depends on the former provider.

Sources and related guides

Primary resources checked for this review: EMVCo’s payment tokenisation resources. Confirm requirements and implementation for the actual arrangement with the responsible provider or appropriate adviser.

Continue with Payment Tokenization: Ask What the Token Protects and Who Controls It and Saved Payment Tokens: Build a Lifecycle and Portability Inventory.

For state and local resources alongside this operating analysis, use the Florida business operations guide on All State Merchants.