X-Pays (Apple / Google / Samsung Pay)
The big-tech wallets. Getting cards into them requires token-requestor integration with the schemes' token services (Visa VTS, Mastercard MDES).
X-Pays provisioning replaces the card number with a device token via the schemes' tokenization services. Users expect it from day one, so every card programme needs a provider that handles VTS/MDES integration, push provisioning and lifecycle.
The trade-off: the wallet UX (and data) belongs to Apple/Google. The European alternative is the issuer wallet (HCE) - your own app as the wallet - which the EEA's iOS NFC access makes uniquely viable in Europe.
Primary source: EMVCo - EMV Payment Tokenisation
In the verified data
- 18 live providers handle Apple Pay, Google Pay and Samsung Pay provisioning; 12 are EU-core firms and 10 keep data in the EEA.
- Two other token routes are tracked separately: Click to Pay for online checkout (6 providers) and the issuer's own wallet via HCE (7 with iPhone HCE in the EEA).
Recomputed from the catalogue and the official EBA, ESMA and FCA registers on every build — how we verify.
Questions to ask a provider
- Which wallets do you provision - Apple Pay, Google Pay, Samsung Pay - and is push provisioning from my app included?
- Do you integrate both Visa VTS and Mastercard MDES?
- How do token lifecycle events - card replaced, suspended, expired - reach my systems?