Apple Pay and Google Pay with a Crypto Card
The interesting part is not that it works. It is that the shop never receives your card number at all.
When a card is added to a phone wallet, the wallet does not store the number. It asks the card network for a substitute — a token tied to that card, that device and nothing else.
From then on the shop receives the token, never the number. A shop that gets breached leaks a token that works nowhere else. This is the single strongest argument for paying by phone rather than by plastic, and it has nothing to do with convenience. It is also what lets a card with no plastic at all work at a shop counter — see virtual card vs physical card.
What happens when you pay
- The terminal asks for a card Your phone answers with the token, not the number.
- The phone signs the amount A one-time code is generated for this payment only. Copying it buys an attacker nothing — it is already spent.
- The network translates The card network maps the token back to the real card and routes the charge.
- The issuer decides The card is checked for balance and limits, and the payment is approved or declined.
What it protects, and what it does not
It protects the number. A leaked token cannot be used elsewhere, and it can be revoked without reissuing the card.
It does not hide the payment from anyone in the chain. The shop knows what you bought, the issuer knows where you paid, and the amount is on your statement either way. Tokenisation is protection against theft, not against being seen.
It also does not protect the physical card. If your card details are stolen from a website where you typed them, the phone wallet was never involved. Where the real risks sit is set out in is a crypto card safe.
When the card will not add
Two reasons cover most cases. The first is that the card was issued through a programme not enabled for wallets — nothing you do on the phone changes that, and the issuer has to enable it at their end. A card issued after proper identity verification is the one that behaves like any other.
The second is a country mismatch: the wallet's region, the card's issuing country and the billing address have to line up. A wallet set to one country with a card from another will usually refuse, and the error message rarely says so.
If the card adds but every payment declines, the cause is almost always the balance or a limit, not the wallet.
Common questions
No. It receives a token, and only the card network can translate it back.
For the card number, yes — clearly. It removes the number from the place most likely to leak it.
Through a phone wallet, yes: a terminal accepting contactless accepts it. Without a phone, a virtual card is for online use.
Usually the wallet region. The country set on the device has to match the card's issuing country.
Ready to try it?
Every fee is on one page, and there is no monthly charge to work around.
See the pricing
