Solution blueprint

Add cards to Apple / Google Pay

Tokenise existing cards into mobile wallets. Below is the product stack you need, with verified European providers for each layer - compare by EEA data residency, licence and regulator.

The stack at a glance · 2 layers, 1 required · select a layer to jump to its providers
  1. 1Wallet provisioning (X-Pays)Tokenization – X-Pays18 verifiedrequired
  2. 2Or your own in-app walletTokenization – Non-X-Pays10 verifiedoptional

How the stack fits together

Getting cards into phones has two routes. The common one is X-Pay provisioning: a token requestor connects your cards to Visa VTS and Mastercard MDES so they can live in Apple Pay, Google Pay or Samsung Pay. The second is your own wallet: host card emulation (HCE) lets your app make contactless payments itself - long possible on Android, and on iPhone only in the EEA, since iOS 17.4. Details: iPhone NFC for European issuers.

Step 1 — Wallet provisioning (X-Pays) required

Push cards into Apple/Google/Samsung Pay (token requestor).

What to check: Check push provisioning from your app, support for both schemes' token services, and how token lifecycle events reach your systems.

In the catalogue — Tokenization – X-Pays: 18 live providers, 10 with data in the EEA; 12 EU-core.

Browse all: Tokenization – X-Pays

Step 2 — Or your own in-app wallet optional

Issuer wallet (HCE) - tokens in your own app instead of big-tech wallets.

What to check: Ask for live references of HCE on iPhone in the EEA, and what the issuer must hold - EEA establishment, PCI DSS, Apple entitlement.

In the catalogue — Tokenization – Non-X-Pays: 10 live providers, 6 with data in the EEA; 7 documenting iPhone HCE in the EEA.

Browse all: Tokenization – Non-X-Pays

Sovereignty notes

Want a hand-picked shortlist for this exact build? Request a match - free, neutral, zero pay-to-rank. Or explore interactively: the catalogue assistant builds this blueprint live from your own description.