How to add a crypto card to Apple Pay and Google Pay

Why bother, when the card already works online

A virtual card pays for anything on the internet the moment it is created. Adding it to a wallet buys you two things beyond that.

The first is tapping in a shop. Your phone becomes the card, which is the whole reason most people never order plastic. The second is quieter but matters more over time: the wallet gives every merchant a device-specific number instead of your real card number. If a shop is breached, what leaks is a token tied to that phone, not the card behind it.

For a no-KYC card that second point is worth pausing on. The card already carries no name. Adding it to a wallet means the merchant does not even receive the card number — only a token. There is less to lose at every step.

Adding the card to Apple Pay

The card is added from the Wallet app on your iPhone, not from our dashboard. We do not push cards into wallets, and no service can — Apple requires the request to come from your device.

1. Open your card in the dashboard and reveal the full number, expiry and CVV.
2. Open Wallet on the iPhone, tap +, then Debit or Credit Card.
3. Tap "Enter Card Details Manually". The camera scan expects an embossed plastic card and will not help you here.
4. Type the number, expiry and CVV. For the name field, enter anything reasonable — the card carries no name, and the wallet only stores what you type locally.
5. Accept the terms and wait for verification. It takes seconds.

On a Mac, the same flow lives in System Settings → Wallet & Apple Pay. Cards added on one device do not appear on your others automatically; each device is added separately, which is exactly what makes the token device-specific.

Adding the card to Google Pay

Same idea, slightly fewer steps.

1. Open the Google Wallet app and tap Add to Wallet → Payment card.
2. Choose "New credit or debit card" and enter the number, expiry and CVV by hand.
3. Confirm. The card appears in the wallet and is ready to tap.

Google Wallet will sometimes ask you to set a screen lock before it accepts a payment card. That is a device requirement, not something we impose, and it applies to every card in the wallet.

When the wallet refuses the card

This is where most people get stuck, and the error messages are famously unhelpful — "Your card issuer does not support this card" tells you nothing about which of five things went wrong.

Work through these in order. They are ranked by how often they turn out to be the cause.

• Your Apple or Google account region. This is one setting to check. Wallets only accept cards from regions where the payment scheme has enabled them for that account's country. Changing your account region is an account setting, not a card problem.
• The card is frozen. A frozen card declines everything, including the tiny verification charge the wallet makes. Unfreeze it, then add it.
• The balance is empty. Some wallets run a small authorisation to verify the card. With a zero balance it fails. Top up first, then add the card.
• You typed the CVV from a screenshot. The CVV is derived on demand and shown when you ask for it. Copy it fresh from the dashboard rather than from an old screenshot.
• Device region or language mismatch. Occasionally a wallet refuses a card when the device region and the account region disagree. Aligning them resolves it.

If all five check out and the wallet still refuses, the card itself is fine — it will keep working online. Wallet eligibility is decided upstream of us, and we cannot override it.

Why the wallet shows a different number

Look at the card in Apple Pay or Google Pay and the last four digits will not match the card in your dashboard. Nothing has gone wrong.

The wallet stores a Device Account Number — a token that stands in for your card on that one device. Merchants receive the token. If you remove the card from the wallet, the token dies and your actual card is untouched.

Two practical consequences. When a merchant asks for "the last four digits of the card you paid with", they want the wallet's four digits, not your card's. And when you check your transaction history, payments made by tapping still show against the real card, because that is where the money came from.

What still applies once it is in the wallet

Adding a card to a wallet changes how it is presented, not what it can do.

• Your balance is still the limit. A tap declines when the balance does not cover it.
• A monthly cap on the card still applies. The wallet has no idea it exists; the decline comes from us.
• Freezing still works instantly, including for the wallet. That is the fastest way to stop a lost phone from spending anything.
• 3-D Secure does not apply to taps. It is an online-checkout mechanism. In-store payments are authorised by your face or fingerprint instead.

That last point is worth remembering: if you mainly want to avoid the 3-D Secure step, paying in store through a wallet skips it entirely. More on that in 3-D Secure without a phone number.

Frequently asked questions

Product references and further reading

• CryptoCard fees and funding minimums
• CryptoCard Terms of Service
• Apple: set up Apple Pay
• Google: add a payment card to Wallet

Published by CryptoCard. Product terms, eligibility and third-party features can change; use the linked reference for the current details.