Eric Kuvykin

By Eric Kuvykin. Reviewed October 17, 2026. This operational guide replaces a general overview; the original publication date and URL are retained.

Separate the credential from the business record

A tokenized credential is not an order-management system. When a customer replaces a phone or adds a wallet to another device, the merchant still needs a stable order reference, customer-service record and refund route. Treat the device change as a test of these connections rather than assuming a familiar last-four display identifies every payment consistently.

Ask the provider what its references mean

Confirm which identifier belongs to the order, transaction, wallet or stored-payment record. Different systems may expose different masked values. Document the supported lookup method without collecting unnecessary credential data. Payment tokenisation can constrain how substituted payment credentials are used, but it does not make every token portable between unrelated processors or eliminate the need to follow provider instructions.

Build a small replacement-device test

Using an approved test environment, create an order, record its merchant reference and inspect the receipt. Then follow the supported device-change scenario and check whether customer service can still find the original purchase. Test the documented refund workflow against the original transaction. Do not try to manufacture a refund by charging or crediting a newly entered credential outside the provider’s process.

Keep the operating evidence

Record expected and observed results, supported limitations and the escalation contact. A Florida business handling repeat visitors should ensure that staff can resolve an older purchase without demanding that the customer present a retired phone. Review the procedure after a wallet, gateway or checkout update. The goal is consistent service and traceable records, not a promise that every device migration will behave identically.

Sources and next steps

The workflow above is an operational method. Consult the current primary resource: EMVCo payment tokenisation overview. It does not establish compliance, guarantee acceptance or replace the provider’s instructions for a live case.

Continue through the AMS Florida merchant reading path. For working-capital decisions, use the alternative-financing cost and cash-flow guide. Explore Eric Kuvykin’s fintech, payments, financing and AI topic guides.