Do wallet tokens follow the same migration rules?

No. Apple Pay tokens, for example, are device-specific and generated by Apple, so they follow different rules from the card tokens a processor holds in its vault. For saved cards and recurring payments outside the wallet, operators rely on network tokenization. The Apple Pay integration article explains how wallet tokens work across several processors.

Wallet tokens are device tokens

When a customer adds a card to Apple Pay, Apple provisions a device-specific token with the issuer. Each payment generates a cryptogram that only works for that transaction. The merchant and the processor never hold a reusable token for the wallet card; they receive an encrypted payload and pass it on. There is nothing in the processor's vault to migrate.

What this means

• Switching processors for Apple Pay is a matter of certificates and decryption keys, not of moving stored data.
• Returning customers pay again from their wallet; no card re-entry is needed.
• For recurring payments set up through a wallet, the merchant-initiated flow depends on the wallet's and scheme's rules, which differ from stored cards.

Saved cards outside the wallet

For cards typed at checkout and saved for later, the migration rules in the checklist apply, and network tokenization is what makes them portable. Operators therefore handle two token families: device tokens managed with wallets and processors through certificates, and stored-card tokens managed in the vault. The Apple Pay integration article covers how the first family works across several processors behind one checkout.