A virtual card that works for online payments is not necessarily eligible for Google Wallet; likewise, successfully adding a card to Google Wallet does not necessarily mean it can already be used for in-store contactless payments.
These three states are often confused:
The card is saved to a Google Account and can be used for payments on websites or in apps;
The card has completed Google Wallet verification and can be used for NFC contactless payments;
The card has actually completed a transaction at a merchant terminal.
A failure at any one of these stages can have a different cause.
Some users can add RedotPay to Google Wallet but fail at terminals that require a PIN. Others use the European version of Coinbase Card, which supports contactless payments on the physical card itself but cannot be added to Google Wallet. Even cards under the same brand may have completely different capabilities when issued under different regional programs.
The key issue is not whether a card is labeled “virtual.” What matters is the issuing program, country of issuance, BIN, issuer, and whether that specific program is integrated with Google Wallet.

Sources and Scope of Conclusions
Primary verification sources: Find supported payment methods; Where you can use Google Wallet; Bitget Wallet Card.
Verifiable statements in this article about issuer support and regional requirements for adding virtual cards to Google Wallet are based on the cited official or regulatory materials. Actual service status, fees, eligibility, and geographic availability should always be confirmed on the issuer’s or platform’s page at the time of application.
Results may vary by issuer, region, account tier, and merchant rules. Experiences, success rates, fee comparisons, or trend assessments that are not directly disclosed in the primary sources above should be treated as analysis or inference and have not been officially confirmed for individual cases by the relevant institutions.
Which Virtual Cards Currently Support Google Pay?
The following results are based primarily on official card-provider information. They do not mean that every account in every region is eligible.
Card | Virtual Card | Google Pay / Wallet Status | Main Regional Restrictions |
|---|---|---|---|
Yes | Supported by multiple regional programs | Europe, Switzerland, Australia, Asia-Pacific, Argentina, Brazil, Peru and others supported; Mexico program not supported | |
Crypto.com Prepaid Card | Yes | Supported by multiple major card programs | U.S., Canada, EU, UK, Australia, Singapore, Bahrain and selected Latin American programs |
Yes | U.S. card supported | EU and UK versions explicitly do not support mobile wallets | |
Nexo Card | Yes | Officially supported | Available only to residents of selected European countries |
Yes, up to 3 | Officially supported | Mainly for euro-area residents | |
KAST Card | Yes | Officially supported | Google Wallet must be available in the user’s region, and card/KYC status must be valid |
Yes | Officially supported | Data may need time to sync after activation; virtual card has no PIN | |
Yes | Officially supported | Available only in selected issuing regions; new applications paused in the U.S. and UK | |
Yes | Supported in designated issuing regions | EEA, UK, Switzerland, Gibraltar and Brazil | |
OKX Card | Virtual only | Officially supported | Issued under regional programs, currently including the EEA, Brazil and other separate programs |
Yes | Officially supported | Currently available only to verified individual users in the UK and EEA | |
Wirex Card | Yes | Officially supported | Official guidance mainly covers Australia, the UK and EEA |
Yes | Explicitly supported by provider | No complete country-by-country list; legacy card-creation flow is currently being upgraded |
Bybit Card
Bybit’s current official regional table shows that card programs in Argentina, AIFC, Georgia, Kazakhstan, Australia, Asia-Pacific, Brazil and Peru support Google Pay, while the Mexico program currently does not. Bybit’s EEA and Switzerland card programs are also integrated with Google Pay.
Crypto.com Prepaid Card
Crypto.com provides relatively detailed information about its virtual cards. U.S.-issued virtual cards support Apple Pay, Samsung Pay and Google Pay. Virtual cards in Australia, the EU and Canada support Apple Pay and Google Pay, while Singapore virtual cards support Google Pay. Its regional table updated in March 2026 also shows Google Wallet availability for the UK, Bahrain and certain Latin American card programs.
Coinbase Card
The U.S. version of Coinbase Card can be added to Apple Pay or Google Pay. The EU and UK versions, however, explicitly cannot currently be added to mobile wallets and must rely on the physical card’s own contactless functionality. U.S. applicants must reside in the United States, excluding Hawaii, and complete identity verification.
Nexo Card
Nexo provides an “Add to Google Pay” option inside its app, allowing the virtual card to be added directly to Google Wallet. Nexo Card is currently available only to residents of selected European countries. Virtual cards remain available, while physical card orders are temporarily paused.
Bitpanda Card
Bitpanda Card supports Google Pay. Users can hold up to three active virtual cards at the same time, but only one physical card per person. Applicants must complete identity verification and live in the euro area. Current card services exclude Cyprus and Liechtenstein.
KAST Card
Both KAST virtual and physical cards can be added to Google Wallet. For a virtual card, users manually enter the card number, expiration date and CVV, then complete verification by SMS, email or in the app. KAST also states that a card can normally be linked to only one Google Wallet account, and activation and KYC must be completed before linking.
RedotPay Card
RedotPay explicitly allows users to add virtual cards to Google Pay for online and in-store payments. The virtual card currently carries a one-time $10 issuance fee. After activation, card data may require time to synchronize with platforms such as Google Pay. Most users can use the card within two days, while some cases may take three to five days.
RedotPay virtual cards do not have a PIN. This does not affect most mobile contactless transactions, but a payment may fail at terminals that force the user to enter a card PIN.
MetaMask Card
MetaMask Card can be added manually to Google Wallet and then used for in-store contactless payments, web payments and app payments. This applies to both virtual and metal cards. MetaMask has currently paused new card applications in the U.S. and UK, while existing cardholders are unaffected.
Gnosis Pay Card
Gnosis Pay clearly states the regions where Google Wallet is supported: cards issued in the EEA, UK, Switzerland, Gibraltar and Brazil can be added. Users need to enter card details manually and complete verification by SMS or email.
OKX Card
OKX Card currently offers virtual cards only. Depending on the issuing region, the card network may be Visa or Mastercard. The official product documentation explicitly supports Apple Pay and Google Pay. Help documentation from July 2026 shows that some card programs currently cover the EEA and Brazil, while availability elsewhere depends on what is actually enabled in the user’s account.
Krak Card
Krak Card is a spending card offered by Kraken. Once approved, users receive a virtual card immediately and can add it to Apple Wallet or Google Wallet. A physical card can be ordered separately. It is currently available only to verified individual accounts in the UK and EEA.
Wirex Card
Both Wirex virtual and physical cards can be added to Google Pay. Official guidance currently covers Australia, the UK and the EEA. Users can either add the card with one tap from the Wirex App or manually enter card details in Google Wallet.
Wirex says its card services cover more than 130 countries and serve over 7 million users, but “being able to register on the platform” and “having a local card program that supports Google Wallet” are still two different things. The card-linking option shown in the user’s account should be treated as the final reference.
Fizen Card
Fizen’s official product pages and articles state that Google Pay is supported, and that virtual cards can be funded with USDT and then used for contactless payments. Fizen says its cards can be used at more than 1.5 million—more accurately, over 150 million—Visa-accepting merchants, and users can create multiple virtual cards.
However, Fizen’s current website indicates that the existing card-creation feature is temporarily paused for an upgrade and that the new card program has not yet fully launched. Existing-card compatibility and new-user card issuance therefore need to be evaluated separately; older tutorials alone are not sufficient.
What Is the Difference Between Google Pay and Google Wallet?
The wallet app on Android phones is now called Google Wallet, while Google Pay is more commonly seen on payment buttons, checkout pages and contactless-payment branding.
A simple way to understand the distinction:
Google Wallet stores cards and handles mobile contactless payments;
Google Pay is the payment service and brand used during merchant checkout;
Seeing “Buy with GPay” on a website does not mean a card necessarily supports phone-based NFC payments;
A card being saved to Google services does not mean contactless payment setup has been completed.
Google explicitly states that even if a card cannot be set up for “Tap to pay,” it may still be stored in Google Wallet for purchases of Google products or for payments on websites and apps that offer a Google Pay button.
For that reason, UCardRadar should separate at least the following three compatibility states:
Status | What It Means |
|---|---|
Can be saved to a Google Account | Can be used on some websites, apps or Google services |
Can be set up for Tap to pay | Issuer token verification has been completed |
Contactless payment actually succeeds | A transaction has been completed at a real POS terminal |
A screenshot showing that a card was “successfully added” proves, at most, the second item.
Why Can a Virtual Card Be Used for Contactless Payments?
Although a virtual card has no physical plastic, it still has a card number, expiration date, CVV and issuing institution.
After the card is added to Google Wallet, the phone does not transmit the original card number directly for every payment. Instead, it uses a device-specific virtual account number or payment token. Google explains that for certain refunds, users may need to provide the last four digits of the virtual card number shown in Google Wallet rather than the last four digits of the original card.
Crypto.com similarly notes that the virtual account number displayed in Google Wallet is not the same as the Crypto.com virtual card number. When processing a refund, a merchant may ask for the last four digits of the wallet token.
This is also why users often need to re-add a card after changing phones, performing a factory reset or removing a Google Account. The card itself has not changed, but the payment token on the original device is no longer valid.
What Conditions Must Be Met to Use Google Wallet for Contactless Payments?
Whether a card can be linked depends on at least three factors: the device, the region and the card.
The Phone Must Support NFC
In-store contactless payments require an Android phone with NFC, with Google Wallet set as the default NFC payment app. The wallet does not need to remain open during payment; the phone simply needs to be unlocked and held near a terminal that supports contactless payments.
The Phone Must Pass Security Checks
Google Wallet may reject:
Rooted phones;
Devices using a custom ROM;
Devices with an unlocked bootloader;
Devices running an uncertified operating system;
Devices without a supported screen-lock method.
Simply installing the Google Wallet APK therefore does not guarantee that contactless payments will work. The device must also run Google Play services normally and pass system integrity and security checks.
Tap to Pay Must Be Available in the Region
Coverage for the Google Wallet app, Google Pay web payments and mobile Tap to pay is not exactly the same.
Google’s official contactless-payment support list includes Hong Kong and Macau, but as of this review, Mainland China is not listed among the supported regions for Google Wallet and Tap to pay.
For users in Mainland China, this means that even if they hold an overseas virtual card, “supports Google Pay” should not be interpreted as “can be used for normal contactless payments on an Android phone in Mainland China.”
The Issuer Must Support It
Google explicitly states that the card issuer ultimately decides whether a particular card can be used for mobile payments. The same bank may enable only selected card products and may restrict certain BINs, prepaid cards, business cards or virtual cards.
That is why two virtual Visa cards can behave differently: one may link successfully while the other shows “Card can’t be set up for tap and pay.”
How Do You Add a Virtual Card to Google Wallet?
There are two common methods.
Add It Directly from the Card App
Platforms such as Bybit, Nexo and Wirex may provide the following options on the card page:
Add to Google Pay
Add to Google Wallet
After tapping the option, accept the issuer terms and complete verification by SMS, email or in the app.
This method is generally more reliable than entering the card manually because the card app can send the correct issuing-program and tokenization information directly to Google.
Add It Manually in Google Wallet
The typical steps are:
Open Google Wallet;
Tap “Add to Wallet”;
Select “Payment card”;
Select “New credit or debit card”;
Scan the physical card or enter the card number manually;
Read and accept the issuer’s terms;
Complete verification by SMS, email or in the app.
Virtual cards from KAST, Gnosis Pay and MetaMask Card can all be added manually.
When linking a card, it is advisable to use the real name and billing address registered with the card provider. If the name, country, postal code or billing address does not match the KYC records, the issuer may refuse to generate a payment token.
Are There Spending Limits for Mobile Contactless Payments?
Google Wallet itself does not impose one universal global transaction limit.
Actual limits usually come from:
The card issuer;
The merchant terminal;
Local contactless-payment rules;
Daily or per-transaction card limits;
Whether the phone has been unlocked or additional verification has been completed.
Crypto.com publishes the following reference limits for Google Pay:
Region | Reference Limit |
|---|---|
Australia | Merchant may require a PIN for transactions over AUD 200 |
Canada | Google Pay transactions up to CAD 250 each |
Europe | Reference contactless threshold of EUR 50; device verification or PIN may be required |
Singapore | Set by the merchant; some transactions require a PIN |
UK, Bahrain | Subject to merchant and card limits |
These are rules for Crypto.com card programs and are not universal limits for all Google Wallet cards.
Gnosis Pay has a per-transaction card spending limit of 5,000 and a rolling 24-hour spending limit of 8,000, denominated in card settlement assets such as EURe, GBPe or USDCe. Its official documentation also specifically notes that the physical card’s contactless limit does not apply to Apple Pay or Google Pay transactions.
Why Does In-Store Payment Still Fail After the Card Is Successfully Added?
When a card in Google Wallet shows “Ready to pay,” it only means that a device token has been created. When an actual payment is made, the transaction must still be authorized by the merchant, card network and issuer.
Common reasons for failure include:
Insufficient card balance;
Card frozen or suspended;
Per-transaction, daily or monthly limit exceeded;
Restricted merchant category;
Country restricted by the card provider;
Merchant terminal requires a PIN but the virtual card has no PIN;
Crypto-asset conversion fails;
Issuer flags the transaction as unusual;
Terminal does not support mobile contactless payments.
Google also explains that if the phone gives contactless feedback but the cashier terminal shows a decline, the card or issuer has usually rejected the transaction and the user should contact the issuer.
RedotPay is a typical example: its virtual card can be added to Google Pay, but because it has no PIN, payment may fail at terminals that force PIN entry.
How to Troubleshoot Common Card-Linking Errors
“Couldn’t finish card setup”
This usually means the issuer did not approve the payment token.
First check that:
The card has been activated;
KYC is still valid;
The card is not frozen;
Google Wallet is supported in the region;
The name and billing address match the card records;
You have not repeatedly attempted setup within a short period.
Google recommends contacting the issuer when this message appears because Google cannot approve the card on the issuer’s behalf.
“Card can’t be set up for tap and pay”
The card may still work for web and app payments, but not for NFC payments.
Check separately whether:
The card supports only online Google Pay;
The card’s BIN is integrated with Google Wallet;
The phone supports NFC;
The system passes security certification;
Tap to pay is available in the account’s region.
“Phone can’t be set up for tap and pay”
Focus on the phone rather than the card:
Is NFC enabled?
Is Google Wallet the default payment app?
Is a screen-lock password or biometric authentication configured?
Is the phone rooted?
Is the bootloader unlocked?
Is the ROM certified by Google?
RedotPay Still Cannot Be Added After Activation
RedotPay says that card data must synchronize with platforms such as Google Pay after activation. Most accounts complete this process within two days, while some take three to five days.
Repeated card-linking attempts or repeated failed transactions during synchronization may trigger risk controls or even freeze the card.
The Card Suddenly Disappears from the Wallet
The following actions may cause the payment token to be removed:
Disabling or changing the screen-lock method;
Not opening Google Wallet for more than 90 days;
Factory-resetting the phone;
Clearing Google Play services data;
Removing the Google Account from the device;
Using an incompatible app-cloning feature.
What Should Users in Mainland China, Hong Kong and Macau Know?
Mainland China
As of July 2026, Mainland China is not listed among the officially supported regions for Google Wallet mobile contactless payments. Even with an overseas-issued virtual card, Tap to pay may be unavailable because of regional restrictions, the Google services environment, or device certification.
Changing the Google Account country, switching networks or installing an APK does not change the card’s BIN or issuer, nor does it bypass Google Wallet’s regional and device-security checks.
For users in Mainland China, overseas virtual cards are generally more practical for web payments, app payments and overseas use than for assuming they will work for Google Wallet contactless payments at POS terminals in Mainland China.
Hong Kong
Hong Kong is included in the supported regions for Google Wallet and Tap to pay. However, whether an overseas virtual card can be added still depends on the issuing program and the applicant’s eligibility.
Google Wallet support in Hong Kong does not mean Hong Kong residents can apply for any U.S. or European card. Products such as the U.S. Coinbase card, Nexo, Bitpanda and Krak Card all impose genuine residency and KYC requirements.
Macau
Macau is also within Google Wallet’s supported coverage, but available cards still depend on Google’s supported-issuer list and each provider’s application requirements.
Which Cards Are Worth Prioritizing by Region?
United States
Key options to review include:
Crypto.com Prepaid Card;
An existing MetaMask Card.
The U.S. Coinbase card supports Google Pay, but applicants must genuinely reside in the U.S. and complete the required identity verification. Crypto.com U.S. virtual cards can also be added to Google Wallet before the physical card arrives.
European Economic Area and United Kingdom
Key options to review include:
Nexo Card;
Bybit European card programs;
Crypto.com European or UK card programs;
OKX Card;
Wirex Card.
Note that although Coinbase Card remains available for application and use in Europe and the UK, it currently cannot be added to Google Wallet.
Australia
The clearer options currently include:
Bybit Australia Card;
Crypto.com Australia Card;
Wirex Card;
Selected OKX regional programs.
Google Pay, Apple Pay and Samsung Pay are all available for the Bybit Australia Card. Crypto.com’s Australian virtual card can also be added directly to Google Wallet.
Singapore
Crypto.com’s Singapore virtual card explicitly supports Google Pay. For other cards, users need to check their assigned issuing program and whether a Google Wallet option appears in the app.
Latin America
Options vary by country:
Bybit: supported in Argentina, Brazil and Peru;
Gnosis Pay: Brazil-issued cards supported;
OKX: Brazil card program;
Crypto.com: Brazil and selected Latin American users;
MetaMask Card: selected Latin American countries;
KAST and RedotPay: subject to actual account eligibility.
How Do You Choose a More Reliable Option?
If you need a virtual card immediately for use in Europe, the main options to review are Bitpanda, Nexo, Gnosis Pay, Krak, OKX and Wirex.
If you live in the United States, start with Coinbase Card and Crypto.com.
Users in Australia can focus on Bybit and Crypto.com.
If you want broader availability and relatively flexible application regions, KAST and RedotPay are worth checking. Before applying, however, confirm that Google Wallet is available locally and that the relevant card BIN has actually been integrated.
To determine whether a virtual card really works with Google Pay, the key question is:
Which card, issued in which region, can actually be added to Google Wallet, enable Tap to pay, and successfully complete a contactless transaction at a real merchant?
From the homepage, open the Google Pay category under “Find Cards by Use Case” to access the detailed page and view recommended cards.