Hubbry Logo
Google WalletGoogle WalletMain
Open search
Google Wallet
Community hub
Google Wallet
logo
7 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Google Wallet
Google Wallet
Google Wallet
View on Wikipedia
from Wikipedia

Google Wallet
DeveloperGoogle
Initial release18 July 2022; 3 years ago (2022-07-18)
Stable release(s) [±]
Android25.44 (Build 828571963) / 6 November 2025; 10 days ago (2025-11-06)[1][2]
Wear OS25.41 (Build 827587639) / 4 November 2025; 12 days ago (2025-11-04)[1][3]
Operating system
Discontinued
Service nameGoogle Wallet
(Wallet for short)
TypeDigital wallet app
Websitewallet.google

Google Wallet (or simply Wallet) is a digital wallet platform developed by Google. It is available for the Android, Wear OS, and Fitbit OS operating systems, and was announced on May 11, 2022, at the 2022 Google I/O keynote. It began rolling out on Android smartphones on July 18, 2022.

History

[edit]

The "Google Wallet" brand name was first used for the company's mobile payment system of the same name, which was introduced in 2011 before being merged with Android Pay into a new app called Google Pay in 2018.[4][5] The old Wallet app, with its functionality reduced to a peer-to-peer payments service, was rebranded Google Pay Send before it was discontinued as well in 2020.[6] In 2020, the Google Pay app underwent an extensive redesign based on Google's India-focused Tez app, expanding into an all-encompassing personal finance app.[7] This replaced the Tez app on the Play Store, while the 2018 Google Pay app continued to co-exist as a separate, pre-installed app on Android smartphones.[8][9]

Google Wallet (2011) launches

[edit]

Google demonstrated the original version of the original Google Wallet app at a press conference on May 26, 2011. The first app was released in the US only on September 19, 2011. Initially, the app only supported Mastercard cards issued by Citibank.

On May 15, 2013, Google announced the integration of Google Wallet and Gmail, allowing users to send money through Gmail attachments. While Google Wallet was available only in the United States, the Gmail integration was made available in the U.S. and the United Kingdom.

In 2015, a physical Google Wallet card was launched as an optional addition to the app, which allowed users to make purchases at point-of-sale (in stores or online) drawing from funds in their Google Wallet account, attached debit card account, or bank account. The card could also be used to withdraw cash at ATMs with no Google-associated fee, and could be used like a debit card for virtually any purpose, including such things as renting a car. The Wallet Card was discontinued on June 30, 2016, and replaced with Android Pay.

Android Pay launches

[edit]

Originally launched as Android Pay, the service was released at Google I/O 2015. Android Pay was a successor to and built on the base established by Google Wallet which was released in 2011.[10] It also used technology from the carrier-backed Softcard—Google had acquired its intellectual property in February 2015.[11][12] At launch, the service was compatible with 70% of Android devices and was accepted at over 700,000 merchants.[11] The old Google Wallet still powered web-based Play Store purchases and some app-based peer-to-peer payments.[11]

The logo of the former branding of the service, Android Pay

In 2016, Google began a public trial in Silicon Valley of a related mobile app called Hands Free. In this system, the customer does not need to present a phone or card. Instead, a customer announces that they wish to "pay with Google" and give their initials to the cashier, who verifies their identity with a photo previously uploaded to the system. The customer's phone will only authorize payment if its geographic location system indicates that it is near a participating store.[13][14]

On September 18, 2017, Google launched a payments app in India known as Tez, utilizing the Unified Payments Interface (UPI).[15] On August 28, 2018, Google rebranded Tez to Google Pay.[16]

Android Pay and Google Wallet become Google Pay

[edit]
Google Pay acceptance mark

On January 8, 2018, Google announced that Google Wallet would be merged into Android Pay, with the service as a whole rebranded as Google Pay.[17][18] This merger extends the platform into web-based payments integrated into other Google and third-party services. It also took over the branding of Google Chrome's autofill feature.[19] Google Pay adopts the features of both Android Pay and Google Wallet through its in-store, peer-to-peer, and online payments services.[20][17]

The rebranding began to roll out as an update to the Android Pay app on February 20, 2018; the app was given an updated design and now displays a personalized list of nearby stores that support Google Pay.[21][22][23] The rebranded service provided a new API that allows merchants to add the payment service to websites, apps, Stripe, Braintree, and Google Assistant.[24] The service allows users to use the payment cards they have on file in their Google Account.[25]

Google Pay becomes Google Wallet (2022)

[edit]

In January 2022, Bloomberg News reported that the company was planning to transform Google Pay into a "comprehensive digital wallet",[26] following the app's reported slow growth and the shutdown of Plex.[27][28] In April, it was reported that Google was planning to revive the "Google Wallet" branding in a new app or interface, and integrated with Google Pay.[29][30] Google officially announced Google Wallet on May 11, 2022, at the 2022 Google I/O keynote.[31] The app began rolling out on Android smartphones on July 18, replacing the 2018 app and co-existing with the 2020 Google Pay app in the U.S.[9][32] While the app name itself was changed from Google Pay to Google Wallet, the service name of actually paying for things online or in-store remains as "Google Pay."

International deployment

[edit]

In its UK launch,[when?] Android Pay supported Mastercard, Visa, and debit cards from many of the UK's major financial institutions – including Bank of Scotland, First Direct, Halifax, HSBC, Lloyds Bank, M&S Bank, MBNA and Nationwide Building Society – "with new banks being added all the time", according to Google.[citation needed] NatWest, RBS and Ulster Bank launched on September 14, 2016. On September 8, 2016, it was reported that UK banks TSB and Santander would be participating in the following weeks.[33] Android Pay was launched in Singapore on June 28, 2016[34] and in Australia on July 14, 2016.[35][36]

Android Pay launched in Ireland on December 7, 2016, and was initially available to customers of AIB and KBC, having since been extended to Bank of Ireland and Ulster Bank. The service works with both credit and debit cards.[37]

On December 21, 2018, Google Payment obtained an e-money license in Lithuania – the license will enable Google to process payments, issue e-money, and handle electronic money wallets in the EU.[38][39]

On November 17, 2020, Google Pay was enabled by Mastercard in ten new European countries: Austria, Bulgaria, Estonia, Greece, Hungary, Latvia, Lithuania, Netherlands, Portugal, and Romania.[40] Cardholders of participating Mastercard partner banks for these countries will be able to use the Google Pay service through their respective mobile banking apps.[41]

On June 30, 2022, it was announced at the Google for Mexico event that payment method Google Pay & the Google Wallet app would soon be available in Mexico.[42] Google Wallet was introduced in India on 8 May 2024, albeit it will function in tandem with Google Pay mobile app, the main payment solution in the market.[43]

Features

[edit]

Google Wallet allows users to store items such as payment cards for use via Google Pay, as well as passes such as loyalty cards, digital keys, digital identification cards, transit passes, event tickets, and health passes.[44]

Digital car keys in Google Wallet can still be utilized when the screen is off or the battery is depleted.[45]

Although the Wear OS and Android versions of Wallet are currently fragmented, Google has stated that its "long-term goal is for feature parity on your watch and phone," though as of 2024, new features continue to be launched without parity on all platforms.[46] At Google I/O 2024, Google announced that "expanded support for passes of all types" would be coming to Wear OS and Fitbit OS.[47]

Comparison between phone and wearable versions

[edit]
Feature Android Wear OS Fitbit OS Notes
Pay with EMV payment cards via Google Pay Yes Partial Partial Some payment cards are not supported on Wear OS or Fitbit OS.
Pay with FeliCa payment cards via Google Pay Yes Yes No For Wear OS:

Only for Pixel Watches, Galaxy Watch Ultra, and Galaxy Watch6 or later devices purchased in Japan.[48][49][50]

Pay via QR code Yes No No For Android:

Only available in Brazil.

Store passes[51] Yes Partial Coming soon For Wear OS:

Private passes are not supported. Smart Tap (NFC) passes only show their fallback QR code/barcode/number.[47]

Store campus identifications Yes Coming soon No
Store corporate badges Yes Yes Coming soon
Store government-issued identifications Yes No No
Store hotel keys Yes Yes No [52]
Store digital car keys Yes Yes No For Android:

Only for select devices, most notably Pixel Fold, Pixel 6, & Pixel 6a or later devices.

For Wear OS:

Only for Pixel Watch 3 or later.[53]

Store MIFARE/ITSO/EMV transit cards Yes Partial Partial For Android:[54]

iPASS can only be stored on

  • Xiaomi 14T/14T Pro
  • POCO F7 Ultra/POCO F7 Pro
  • POCO X7 Pro

For Wear OS:

Only SmarTrip, Clipper, ORCA, PRESTO, and Myki are supported.[55]

For Fitbit OS:[56]

iPASS can only be stored on

  • Sense Series
  • Versa Series (excluding Lite version)
  • Charge 3 Series and above
Store FeliCa transit cards Yes Partial Partial For Android:

Only for supported devices purchased in Japan.

For Wear OS:

Only for Pixel Watches, Galaxy Watch6 or later, and Galaxy Watch Ultra devices purchased in Japan.[57][50]

For Fitbit OS:

Suica cards can be stored through Fitbit Wallet instead (Fitbit account region must be set to Japan.)

Store FeliCa e-money cards Yes No No For Android:

Only for supported devices purchased in Japan.

Store transit loyalty cards Yes No No [58]

Skip device unlock & Battery depletion

[edit]

Most NFC passes can be transmitted when the Android device is locked, but the screen must be lit (Always On Display does not count.) This includes most compatible transit cards, loyalty passes, tickets, and campus IDs. However, government IDs can only be used when the device is unlocked.[59]

Only one class of NFC passes allows usage when the screen is unlit or the battery is depleted: car keys.[60]

Usage

[edit]

Passes and cards stored in Wallet require varying levels of authentication in order to convey to a reader.[61][62][63]

Feature Android Wear OS Fitbit OS
Pay with EMV payment cards via Google Pay Phone on, phone unlocked. To pay with non-default, Wallet app must be open to desired card. Watch on, watch unlocked, Wallet app open. Watch on, watch unlocked, Wallet app open.
Pay with FeliCa payment cards via Google Pay Phone on, phone unlocked to pay with default iD/QUICPay card. To pay with non-default, Wallet app must be open to the desired card. Watch on, watch unlocked to pay with default iD/QUICPay card. To pay with non-default, Wallet app must be open to desired card. —
Pay via QR code Phone on, phone unlocked, Wallet app open & ready to scan QR. — —
Use code-based or visual passes (excluding visual transit passes) Phone on, phone unlocked, Wallet app open & viewing desired pass. Watch on, watch unlocked, Wallet app open & viewing desired pass. —
Use general NFC (Smart Tap) passes Phone on, phone screen lit. Some Pixel devices will wake their own screen when presented to an NFC reader. — —
Use private passes Phone on, phone unlocked, Wallet app open, authenticate additional time. — —
Use government-issued identifications Phone on, phone unlocked, verify shared info. Additional step of opening the Wallet app is required if scanning 2D code instead of NFC. — —
Use digital car keys Phone can be on or off for use via NFC. For UWB, phone must be on. Watch can be on and unlocked or manually powered off after having been unlocked for use via NFC. For UWB, watch must be on and unlocked. —
Pay with EMV payment cards on transit Phone on. To pay with non-default, phone must be unlocked and Wallet app must be open to desired card. Watch on, watch unlocked. To pay with non-default, Wallet app must be open to desired card.
Use MIFARE/ITSO/EMV transit cards Phone on, phone screen lit. Some Pixel devices will wake their own screen when presented to an NFC reader.** Watch on, watch unlocked.*[64] Watch can be on or off, depending on device.^[65]
Use FeliCa transit cards Phone can be on or off. Watch on, watch unlocked. —
Use transit loyalty cards Phone on, phone screen lit. Some Pixel devices will wake their own screen when presented to an NFC reader. — —

* = except Clipper & myki; Wallet app must be open in those cases

** = except iPASS; phone can be off in that case

^ = iPASS only

Pass Transfers

[edit]

When switching devices or factory resetting, passes that are limited to one device have the potential to be lost, as Android/Wear OS does not automatically remove data from Wallet when the aforementioned processes are initiated. The user must remember to clear device-specific passes, such as transit cards, IDs, and keys from their current devices.[66]

Ecosystem

[edit]
"Add to Google Wallet" badge

Google Wallet has a passes feature, which exists in a larger ecosystem. They are presented below the user's payment cards and can be sorted manually. Developers must first be granted access to the Google Wallet API before they can author such items.[67] Passes can be shared to other users via a link, so long as the issuer of said pass does not restrict its addition to more than one user's Wallet.[68]

In its simplest form, an interaction (or transaction) between a pass and a system is facilitated by a 1D or 2D code, although it requires the customer to initiate the activity. Passes can also contain nothing but plain text or an image.

In addition to retailer-specific passes, Google Wallet also supports contactless student IDs that can be added through the Transact eAccounts and CBORD GET Mobile applications.[69] Government-issued IDs are also supported in ten American states.[70][71][72]

Smart Tap

[edit]

Google Wallet offers Smart Tap technology for use by developers and merchants that enables NFC passes to be stored within a customer's Google Wallet for use at a compatible terminal. Google offers the technology free of charge through the Google Pay & Wallet Console. Each pass issuer is given a Collector ID to use to configure their compatible terminals. If multiple passes within a user's Wallet match a terminal's Collector ID, a carousel will appear when tapping, allowing the user to tap their device, swipe to the next pass, and then repeat the process until all desired passes are transmitted.[73]

This technology is currently used by a variety of businesses worldwide for a wide range of uses. Walt Disney World Resort (USA), Ticketmaster (USA & UK), and Pathé Cinémas (France) use it for ticketing.[74][75] Redbox (USA), Nando's (UK & Ireland), and Woolworth's (Australia) use it for loyalty programs.[76][77][78] And Anytime Fitness (Globally), Keepcool (France), Club Lime (Australia), & David Lloyd Clubs (UK) use it for memberships.[79][80][81][82]

Financial services

[edit]

Google Pay

[edit]
Main article: Google Pay (payment method)

Google Pay is a service within Wallet that allows for payments with select banks and card networks. Currently available in a subset of the countries that support Google Wallet.

QR Payments

[edit]
Not to be confused with QR payments via GPay app.

Wallet allows for QR payments in Brazil. This service supports the Visa, Mastercard, and Elo networks, as well as via Pix, and is primarily intended for users that do not have NFC functionality in their Android-powered devices.[83][84][85]

Availability

[edit]

Supported countries

[edit]
Global availability of Google Wallet
  Google Wallet available
  Upcoming

As of September 2025, Google Wallet is available in 150 countries worldwide for both Android & Wear OS.[86][87]

* = Not available for Fitbit OS

** = Google Pay functionality available through Google Pay app

^ = Google Wallet website Unavailable[88]

Upcoming

[edit]

Region locking

[edit]

Google Wallet prohibits FeliCa-based payment, transit, and loyalty functionality (e.g. Suica, PASMO, WAON, etc.) from being accessed on non-Japanese devices by restricting the initialization of the required third-party Osaifu-Keitai middleware apps on both Android & Wear OS. However, users have discovered ways to enable the functionality on non-Japanese models of Pixels via rooting.[89][90] This behavior is in contrast to other wallets such as Apple Wallet, which allow users with any regional device model (iPhone 7 or later) to add FeliCa-based cards.[91][92]

In turn, users with Japanese devices cannot access North American & European transit cards such as SmarTrip and Pop, though there is a workaround via previewing a route in Google Maps that uses the desired fare payment method, and selecting the banner that offers to add said card to Wallet.

Campus IDs are also locked to devices bought in the United States of America, Canada, and Australia. Google claims support for international devices is "coming soon," though this has been promised for several years as of 2024.[62]

In addition, UWB functionality for car keys is limited to regions that allow the frequency to be broadcast in personal mobile devices by law.[93]

Supported loyalty programs

[edit]

These programs are conveyed through NFC through Google Wallet's Smart Tap feature. Some of these can be added through the Google Wallet app directly, while others must be added through the respective retailer's app or website. Programs that support One Tap are conveyed at the same time as a payment card stored in Google Wallet. Conversely, Two Tap programs are redeemed in a sequential manner, where a loyalty pass is scanned first, and then payment can be presented.[94]

Country Retailer One Tap/Two Tap
 Australia Dan Murphy's My Dan's[95]
Woolworths' Everyday Rewards[78] Two Tap
 Ireland Nando's Nando Card[96] Two Tap
 Japan d Point[97] Two Tap
Rakuten Point Card[98] Two Tap
New Zealand Woolworths' Everyday Rewards[99] Two Tap
 Taiwan OPEN POINT[100][101] One Tap
 United Kingdom Nando's Nando Card[102] Two Tap
Texaco's Star Rewards[103] Two Tap
Valero's SaveUP Rewards[104]
 United States Coca-Cola's Vending Pass[105] One Tap
Dave & Buster's Power Card[106] One Tap
Jimmy John's Freaky Fast Rewards[107] One Tap
Walgreens' myWalgreens[108] Two Tap
Yogurtland's Real Rewards[109] One Tap

Supported public transport systems

[edit]

Due to the open nature of the Android platform, some transit cards are only available through other Android-based mobile wallets or via their own apps (e.g. Navigo for Samsung Wallet or TAP for Android). Transit cards that support direct provisioning can be issued within the Google Wallet app itself, without needing to download a separate third party application. Some public transport systems listed here support skipping verification with Google Pay on Android and Wear OS, wherein the only requirement for transmitting a payment or transit card is for the device to be on (for phones), or further have the device unlocked (for watches.) This is not supported on Google Wallet for Fitbit OS, however. Users with Fitbit watches must open the Wallet app time each time they scan their fare payment method (except FeliCa-based fare methods).[110][111]

All FeliCa-based cards require separate apps to be used and managed by Wallet. Suica and PASMO require the Osaifu-Keitai app, and Octopus requires the Octopus app. All these cards are region-locked and cannot be added by foreign tourists.[90]

Transit Insight cards are passes that can be linked to one payment card in a user's Wallet. Similarly to a transit card, it will keep track of rides made on the system and offer fare caps. However, there is no standalone balance. All funds are pulled directly from the linked payment card.[58]

Country Area Skip verification Direct provisioning Wear OS support Stored via Fare Payment Method(s)
 Australia Queensland — — — Payment cards
Sydney Yes — — — Payment cards
Victoria Yes Yes Yes Host Card Emulation Myki*
 Brazil  Rio de Janeiro (only MetrôRio) — — — Payment cards
 São Paulo (only SPTrans) — — — Payment cards
 Canada Ontario (TTC, GO Transit, Brampton Transit, MiWay, Oakville Transit and UP Express.[112]) Yes Yes Yes Host Card Emulation PRESTO
— — — Payment cards- VISA, Mastercard and American Express accepted. UP Express also accepts Interac debit cards.
Vancouver — — — Payment cards
 Greece Athens Yes — — — Payment cards- VISA and Mastercard accepted.
Hong Kong Countrywide[113] Yes No No Secure Element via Octopus app Octopus
 Japan Countrywide Yes Yes Yes Secure Element via Osaifu-Keitai app Suica
Yes Yes Yes Secure Element via Osaifu-Keitai app PASMO
 Mexico CDMX (only Mexico City Metrobús and Mexico City Metro) — — — Payment cards
 Singapore Countrywide Yes — — — Payment cards
 Slovakia Countrywide[114] Yes No No Host Card Emulation Ubian
 Spain Madrid[115][116] Yes No No Host Card Emulation Tarjeta Transporte Público
 Taiwan Countrywide Yes Yes No Secure Element iPASS[117]
Kaohsiung No — Yes — Payment cards- VISA and Mastercard accepted.
New Taipei Metro No — Yes — Payment cards- Mastercard are accepted by Ankeng and Danhai light rail.
Taichung Metro No — Yes — Payment cards- VISA accepted.
Taoyuan Airport MRT No — Yes — Payment cards- VISA and Mastercard accepted.
 Ukraine Kyiv — — — Payment cards
 United Kingdom Brighton and Hove[118] Yes No Transit loyalty card connected to payment card
Edinburgh Yes — — — Payment cards
London Yes — — — Payment cards
Manchester Yes — — — Payment cards
Tyne and Wear Yes Yes No Host Card Emulation Pop
West Midlands Yes No No Host Card Emulation Swift
 United States Chicago Yes No No Host Card Emulation Ventra
Yes — — — Payment cards
Dallas Yes — — — Payment cards
Las Vegas Yes No No Host Card Emulation Contactless ticket
Miami Yes — — — Payment cards
Monterey[119] Yes No Transit loyalty card connected to payment card
New York City Yes — — — Payment cards
Portland, Oregon Yes No No Host Card Emulation Hop Fastpass
Yes — — — Payment cards
San Francisco Yes Yes Yes Host Card Emulation Clipper*, payment cards (BART only)
Seattle Yes Yes Yes Host Card Emulation ORCA[120]
Washington, D.C. Yes Yes Yes Host Card Emulation SmarTrip, payment cards (Metrorail only)[121]

* = Card cannot be used without opening Wallet beforehand on Wear OS.

Upcoming

[edit]
Country Area Wear OS support Stored via Fare Payment Method(s)
Mexico Jalisco[122] Unknown Unknown Mi Movilidad
United Arab Emirates Dubai[123] Unknown Unknown nol
United States Los Angeles[124] Unknown Unknown TAP
Philadelphia[125] Unknown Unknown SEPTA Key
Washington, D.C. Unknown Host Card Emulation Kids Ride Free SmarTrip[126]

Supported digital keys

[edit]

These vehicle models, hotel rooms, and more can be unlocked via NFC. Car keys in particular require select devices running Android 12/Wear OS 5 or later, most notably the Pixel 6 or later. In addition, certain car models that support operation via UWB (AKA "passive entry") require an UWB compatible device, such as the Pixel Fold, Pro models of Pixel 6 and later devices, or Pixel Watch 3 and later, for enhanced functionality.[127][128]

Main article: List of digital keys in mobile wallets

Supported government-issued identifications

[edit]

These territories permit their residents to save their government-issued identification credentials in Google Wallet. Mobile IDs in Google Wallet support three personal identification standards: ISO 18013-5, ISO 23220-4, and NIST 800-63.[129] Users have a choice whether to present their ID via NFC or QR. Once the credential is read, the ID holder must confirm the personal information they wish to share (full name, age, etc.) The transmission to the reader device will be completed over BLE after the presentation is fully verified. Credentials can also be utilized in apps or on the web. All IDs are free except those issued by North Dakota, which costs $5 per ID renewal.[130] Available for devices running Android 9 or later.[131][132]

Country Type State/Territory
 United States ID Arizona
ID Arkansas[133]
ID California[134]
ID Colorado
ID Georgia
ID Iowa[135]
ID Maryland[136]
ID Montana[137]
ID New Mexico[138]
ID North Dakota[130]
ID Puerto Rico[6]

Upcoming

[edit]
Country Type State/Territory
Japan ID Countrywide[139]
 United States ID Illinois[140]
ID Ohio[141]
ID Virginia[142]
ID West Virginia[143]

Other non-government issued identifications

[edit]

These are ID passes issued by Google that utilize information from an individual's government-issued ID, but the digitized pass itself is not considered to be "government-issued."

Country Type
 United States Passport[144][143]
United Kingdom

Device-specific & region-locked features

[edit]

Some features in Wallet are locked to certain devices that have additional hardware or software that aren't included in other Android/Wear OS devices, such as secure elements or licenses for certain region-specific middleware.

Car keys

[edit]

Some devices may need Android OS or Play System updates before being compatible. Compatible Pixel Watches must be paired with a compatible Pixel phone to use digital keys.[145]

Brand Model UWB availability
Google Pixel 6a No
Pixel 6 No
Pixel 6 Pro Yes
Pixel 7a No
Pixel 7 No
Pixel 7 Pro Yes
Pixel 8a No
Pixel 8 No
Pixel 8 Pro Yes
Pixel Fold Yes
Pixel 9a No
Pixel 9 No
Pixel 9 Pro Yes
Pixel 9 Pro Fold Yes
Pixel 10 No
Pixel 10 Pro Yes
Pixel 10 Pro Fold Yes
Pixel Watch 3 Yes
Pixel Watch 4 Yes
Motorola[146] Edge 50 Ultra[147] Yes
Razr 50 Ultra No
Razr 60 Ultra No
Razr Plus 2024 No
Razr Ultra 2025 Yes
OnePlus[146] 11 No
Open No
12 No
13 No
Oppo[148] Find N3 No
Find N3 Flip No
Find N5 No
Find X8 No
Find X8 Pro No
Xiaomi[149][148] 12 No
12 Pro No
13 No
13 Pro No
13 Ultra No
13T No
13T Pro No
14 No
14 Ultra No
14T No
14T Pro No
15 No
15 Ultra No
MIX Flip Yes

Transit cards

[edit]
Transit card Requirement(s)
iPASS Phones:

Xiaomi 14, Xiaomi 14 Ultra, Xiaomi 14T, Xiaomi 14T Pro, Xiaomi MIX Flip

POCO F7 Ultra, POCO F7 Pro, POCO X7 Pro

Wearables:

Fitbit Sense or later, Fitbit Versa or later (except Lite), Fitbit Charge 3 or later

Google Account region must be set to Taiwan

Octopus Phones: Android 12 or later with NFC

Must install Octopus Wallet app (which requires a Hong Kong phone number to sign up for)

PASMO Phones: Japanese models of select phones

Must install Osaifu-Keitai app

Wearables:

Japanese models of Google Pixel Watch or later

Japanese models of Samsung Galaxy Watch6 or later, Galaxy Watch Ultra

Google Account region must be set to Japan

Suica

e-Money cards

[edit]
e-Money card Requirement(s)
Edy Phones: Japanese models of select phones

Must install Osaifu-Keitai app

nanaco
WAON

See also

[edit]

References

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

Google Wallet

View on Grokipedia
from Grokipedia
Google Wallet is a secure service developed by Google that enables users to store and manage payment cards, loyalty cards, event tickets, transit passes, digital keys, and identification documents—including digital passports added in November 2025 for enhanced travel verification—on compatible Android devices and the web, providing quick access for contactless payments and other everyday uses. Originally launched on September 19, 2011, as a pioneering mobile payment system allowing users to load credit and debit cards onto NFC-enabled Android phones for in-store tap-to-pay transactions, Google Wallet faced limited adoption due to hardware constraints and partnerships. Over the following years, it evolved into Android Pay in 2015 and then Google Pay in 2018, shifting focus to broader digital payments including peer-to-peer transfers and online transactions while phasing out the standalone Wallet branding. In 2022, Google reintroduced Google Wallet as a distinct app during Google I/O on May 11, emphasizing secure storage for a wider array of digital items beyond just payments, with full rollout beginning July 18 in 39 countries. Key features of Google Wallet include tap-to-pay functionality at millions of merchants worldwide where is accepted, integration with digital IDs such as driver's licenses in select U.S. states and territories for age and identity verification, and support for virtual car keys via technology for lock/unlock actions. Users can also add boarding passes, movie tickets, and loyalty programs for seamless presentation via QR codes or NFC, with built-in privacy controls allowing selective sharing of stored data. As of 2025, enhancements include family sharing options for on children's wallets and predictive pass suggestions based on user habits, though not all features are available globally. In the United States, following the discontinuation of the standalone Google Pay app on June 4, 2024, Google Wallet serves as the primary app for contactless payments and storage of cards, passes, and other digital items, with peer-to-peer transfers no longer supported; Google Pay branding persists for transaction processing and online checkout. It is available in over 70 countries but with varying support for features like digital IDs limited to select U.S. states and territories. The service prioritizes security through device , biometric authentication, and tokenization to protect sensitive information without storing full card details on Google's servers.

History

Initial launch and early versions (2011–2015)

Google Wallet was launched on September 19, 2011, as the first major application to enable contactless transactions using (NFC) technology, initially supporting Citi-issued credit cards and a Google Prepaid Card for payments at participating merchants in the United States. The service debuted exclusively on Sprint's 4G smartphone, with plans to expand to the upcoming device, marking a pioneering effort to integrate digital wallets into everyday mobile commerce through partnerships with carriers like Sprint and payment networks including , Visa, and Discover. At launch, the app's core features allowed users to store credit and debit cards for tap-to-pay transactions, as well as loyalty cards and promotional offers, with seamless integration to Google Offers—a daily deals platform that enabled automatic redemption of coupons at checkout via NFC. This functionality aimed to consolidate physical cards and vouchers into a single digital interface, positioning Google Wallet as an open ecosystem for merchants to load offers without fees. Early adoption faced significant hurdles, including limited device compatibility restricted to NFC-enabled phones like the and on select carriers, which constrained its reach amid a fragmented Android ecosystem. Security concerns emerged prominently in early 2012 when researchers identified vulnerabilities in the app's four-digit PIN protection, allowing potential brute-force attacks to access stored card data on rooted devices, prompting to enhance and mandate PIN usage for all transactions to mitigate risks. Additionally, merchant acceptance remained sparse, with only a fraction of U.S. retailers equipped for NFC payments, slowing consumer uptake and highlighting the need for broader investment. In response to these challenges, discontinued support for the Google Prepaid Card feature in October 2012, citing low usage and a strategic shift toward emphasizing traditional and integrations. By 2013, the service expanded significantly to support nearly all Android devices running version 2.3 or higher across major U.S. carriers like , , and Verizon, eliminating the NFC hardware requirement for non-payment functions such as storing offers and loyalty cards while maintaining U.S.-only availability to focus on domestic market maturation. Despite these improvements, ongoing issues with device support and persisted, underscoring the foundational limitations of the initial NFC-centric model during this period.

Transition to Android Pay and Google Pay (2016–2021)

Following the launch of Android Pay in September 2015, Google Wallet was repositioned in 2016 as a dedicated (P2P) payments application, focusing on money transfers between users while Android Pay handled contactless and in-app payments. This separation allowed Google to streamline its mobile payment ecosystem, with Google Wallet emphasizing features like sending money via , phone number, or without requiring the recipient to have the app installed. In August 2016, Google Wallet introduced automatic transfers to linked bank accounts or debit cards, enabling users to move funds instantly to debit cards (with some banks processing in up to 24 hours) or within 1-3 business days to banks, reducing the need for manual cash-outs and positioning it as a competitor to services like and . The physical Google Wallet prepaid card was discontinued in March 2016, further shifting the service toward digital P2P interactions. From 2016 to 2018, Android Pay and operated as complementary services within the Android ecosystem, supporting over 700,000 physical stores and thousands of apps for Android Pay, while facilitated P2P transfers among U.S. users. This dual structure addressed different use cases but led to user confusion, prompting to unify them. On January 8, 2018, announced the rebranding of both services into a single platform called , aiming to simplify payments across online, in-store, and P2P scenarios while enhancing security through tokenization and device authentication. The new integrated Android Pay's NFC capabilities with 's transfer features, supporting credit and debit cards from major networks like Visa, , , and Discover, and expanding compatibility with partners such as and . Post-rebranding, Google Pay saw significant global expansions between 2018 and 2021, rolling out to new markets including the in 2018 and integrating with more banks and transit systems worldwide. In , the service evolved from the 2017 Tez app (rebranded to Google Pay in 2018) to support (UPI) for seamless local transactions. By 2020, Google Pay underwent a major U.S. revamp on November 18, introducing a redesigned app for Android and that combined payments with financial management tools, such as personalized insights into spending and savings, cashback rewards, and integration with banks for balance checks and transaction history. This update emphasized a holistic money management experience, allowing users to track expenses, set budgets, and access offers without switching apps, while maintaining core security features like biometric authentication. Through 2021, Google Pay continued to grow, adding support for more cryptocurrencies in select regions and enhancing cross-platform compatibility, solidifying its role as a comprehensive digital wallet.

Relaunch and rebranding as Google Wallet (2022–2023)

On May 11, 2022, Google announced the revival of Google Wallet at its I/O developer conference, establishing it as a dedicated platform for non-payment digital storage separate from , which remained focused on transactions. The new Wallet was designed to serve as a centralized home for items such as IDs, transit tickets, cards, boarding passes, event tickets, cards, and keys, aiming to enhance user convenience by consolidating these essentials in one secure app. This separation addressed previous overlaps in functionality, allowing to specialize in while Wallet handled broader digital item management. The app officially relaunched on July 18, 2022, initially for Android devices and smartwatches, with an emphasis on secure storage and quick retrieval of non-financial passes and keys. Key initial features included Smart Tap, which enabled users to access stored items rapidly via NFC taps at compatible terminals without unlocking their device, and integration with to add passes or IDs directly from saved images. These capabilities extended to 3 devices, supporting tap-to-access for payments and passes on smartwatches. The rollout prioritized the and 38 other countries, beginning with Android users before expanding to , to ensure broad accessibility while testing infrastructure for digital item verification. Early adoption in 2023 included the integration of student IDs from select universities, such as , where users could add their campus cards to Wallet for building access and meal payments via NFC. This rebranding initiative stemmed from 's goal to provide clearer branding, distinguishing Wallet's role in everyday digital storage from Google Pay's emphasis on secure financial transactions and thereby reducing user confusion in a multi-app .

Expansions and updates (2024–2025)

In 2024, the standalone Google Pay app in the United States was discontinued on June 4, with its payment and storage functions transitioned to Google Wallet, which now handles contactless NFC tap-to-pay, card storage, transit passes, event tickets, loyalty cards, and digital IDs in supported regions, but without built-in peer-to-peer money transfers (previously discontinued to promote alternatives like Venmo, Cash App, or Zelle). Google Wallet continued to expand its digital ID support in the U.S., building on implementations in states like , , Georgia, , and (launched in 2023). Further additions included in October 2025 to enhance mobile identity verification. Concurrently, Google Wallet launched in in May 2024 through partnerships with local service providers, introducing features tailored for Android users to store and manage passes, including transit integration. At 2025 (May 21–22), Google announced several enhancements, including family sharing for passes to allow multiple users to access shared digital items like tickets and cards. Key updates also introduced real-time transit notifications on passes, such as delay alerts, for broader identity storage. Additionally, accessibility improvements were rolled out for devices, enabling seamless transit pass usage and tap-to-pay without opening the app on 5 or later. In October 2025, Google Wallet integrated Android 16's Live Updates feature, providing real-time status notifications for flights, train trips, and events directly on the or within the app, such as progress bars for flight durations. This update enhances travel convenience by displaying dynamic information without requiring users to launch additional apps. November 2025 brought the "Everything Else" feature, which leverages users' purchase and pass history to auto-suggest and simplify adding digital passes for items like event tickets or memberships. Users can now create personalized digital versions by scanning photos, with consent-based recommendations to streamline pass management. On the international front, Google Wallet advanced deployments in markets like by supporting transit cards for local systems and pass storage. In the , partnerships aligned the app with emerging regulations, ensuring compliance for secure identity and payment features amid the rollout of the EU Digital Identity Wallet framework. Developer tools saw updates to the Google Wallet API in release notes up to October 14, 2025, including support for custom passes with features like Nearby Passes geofence notifications for up to 10 locations per class and pass nicknames up to 25 characters for easier management. These enhancements enable developers to create more tailored, location-aware digital passes across all regular pass types.

Overview and Core Features

Payment and storage capabilities

Google Wallet allows users to securely store various payment methods, including and debit cards, which can be added directly through the app by scanning the card with the device's camera or manually entering details after verification by the issuing bank. Loyalty cards, gift cards, and promotional offers from participating merchants can also be added by searching for the program within the app or scanning the physical card's , enabling quick access at checkout without carrying physical versions. However, gift cards bearing an issuer logo, such as Mastercard or Visa, must be added as payment methods rather than as gift cards. Compatibility of such cards as payment methods varies by issuer, and many virtual Visa e-gift cards and prepaid Visa gift cards are reported as incompatible with Google Wallet due to issuer restrictions or lack of digital wallet support. For enhanced security during online transactions, eligible users in supported regions like the can generate virtual card numbers—temporary, merchant-specific alternatives to the actual card details—that mask the real information and can be managed via the Google Wallet app or website. The platform supports pass management for everyday items such as boarding passes, event tickets, and membership cards, which users can add by tapping links in confirmation emails, scanning QR codes or barcodes from apps or screenshots, or entering URLs provided by issuers directly in the Google Wallet app. Once added, these passes are organized in the app for easy retrieval, with options to edit details, archive unused items, or reorder for priority access during use. This storage approach reduces the need for physical documents, streamlining access at airports, venues, or retail locations. To facilitate quick contactless interactions, Google Wallet includes a "skip device unlock" option for select scenarios, allowing payments or pass scans when the screen is off or locked, provided the device has a secure screen lock enabled and recent authentication has occurred. The service also maintains functionality in low-battery mode, though critically low power levels may temporarily disrupt NFC operations until recharged. On smartwatches, Google Wallet offers a simplified compared to smartphones, with gesture-based —such as to select and to scan passes—lacking advanced features that are available on phones, while still supporting core storage and access for loyalty cards, gift cards, and tickets. All stored items in Google Wallet sync automatically across compatible devices signed into the same , ensuring seamless availability on phones, tablets, or wearables without manual re-addition for most passes and cards.

Pass and ticket integration

Google Wallet supports a variety of dynamic passes and tickets, enabling users to store and access digital versions of event tickets, transit passes, and health-related proofs directly on their Android devices. These passes are designed to integrate seamlessly with everyday activities, such as attending concerts or boarding flights, by leveraging NFC technology for quick verification at venues or gates. Among the supported types, event tickets include those for concerts and sports events issued through partners like , where users can add digital copies via the provider's app for easy access. Transit passes allow for fare payments and travel tracking on supported public transportation systems, while health passes encompass records and test results from verified sources. These passes are not static; they can receive updates from issuers to reflect changes in event details or travel status. Adding passes to Google Wallet occurs through multiple methods, including manual upload from a pass issuer's app or website by selecting "Add to Google Wallet" under sections like "Tickets" or "Passes." Auto-detection from automatically imports eligible passes, such as movie tickets or boarding passes, upon receiving confirmation emails, provided "Smart features and personalization" is enabled in settings. Partner apps facilitate direct addition, and users can also scan photos of physical passes using the Wallet app's camera feature. Transferability between users depends on the issuer; for supported passes like certain boarding passes, sharing is possible via the app, though most require contacting the provider for approval. Real-time features enhance usability by providing live updates directly within the pass. For flights, Wallet displays gate changes and boarding times pulled from airline data, while 2025 expansions introduced live transit status notifications, such as train delays or on-time arrivals, integrated via Android 16's Live Updates API. Venue entry for events utilizes NFC, allowing users to hold their unlocked phone near a contactless reader for verification, with a blue check mark confirming acceptance. These updates ensure passes remain current without manual intervention. Family support was enhanced in 2024 through integration with , allowing supervised sharing of certain passes like event tickets and loyalty cards with family members or children on compatible devices. This feature enables parents to manage and view passes for minors, promoting secure access for group activities such as family outings. In 2025, Google Wallet for kids expanded this further, supporting passes on Family Link-supervised devices for added convenience. Limitations include restrictions on editing passes, as issuer-locked content cannot be modified by users to maintain and accuracy; any changes must come from the provider. Expiration handling automatically moves outdated passes to an "Expired passes" section in the app up to 24 hours after the valid time interval ends, preventing clutter while retaining access for reference, though users cannot extend validity themselves.

Security measures

Google Wallet employs tokenization to enhance payment security by replacing actual card numbers with unique device-specific tokens generated through EMV standards. This process ensures that merchants and payment networks receive only the token during transactions, not the sensitive card details, thereby reducing the risk of data breaches even if intercepted. The tokens are securely provisioned and managed via Android's device authentication mechanisms, linking them to the user's rather than the physical card. Access to Google Wallet requires biometric authentication, such as scanning or face unlock, or a device PIN, to verify the user before authorizing payments or adding cards. This multi-factor approach integrates with the device's secure hardware, ensuring that only authenticated users can initiate transactions. Additionally, in the event of device loss or theft, users can remotely wipe Google Wallet data using the Find My Device feature, which erases payment information and locks the app to prevent unauthorized access. Privacy controls in Google Wallet include end-to-end data for information in transit using secure protocols and at rest on both the device and Google's servers to protect stored payment details. Users can of sharing transaction history with for or purposes through , allowing control over data usage while maintaining functionality. As of November 2025, an opt-in setting allows users to enable of recommendations and deals based on purchase and pass history within Google Wallet. Google Wallet maintains compliance with the Payment Card Industry Data Security Standard (PCI DSS), which mandates rigorous controls for handling cardholder data, including , access restrictions, and regular vulnerability assessments. This certification applies to Google Pay's underlying infrastructure, ensuring that all payment processing meets industry benchmarks for security. In 2025, Google Wallet introduced enhanced security for family sharing features, requiring individual parental consents to add payment cards for supervised child accounts and providing real-time notifications for all transactions. This update, integrated with Family Link, ensures that minors' access is tightly controlled, with parents able to monitor and revoke permissions at any time. For certain low-risk scenarios like transit payments, Google Wallet supports quick tap access without requiring device unlock after initial authentication, balancing convenience with security.

User interface and accessibility

The Google Wallet app features a streamlined home screen layout centered around a of cards and passes, presented as a stack for quick access to the active method on top. Users can swipe horizontally through the stack to select different cards or passes, with tapping a card revealing detailed views such as recent transaction activity or customization options like nicknames. This emphasizes touchless payments by keeping the primary card prominent, while the bottom of the screen includes a "+" for adding new items via "Add to Wallet." Navigation within the app is organized into distinct categories, including payments for credit/debit cards and digital wallets, transit for tickets and boarding passes, and IDs for supported digital identification like driver's licenses in select regions such as . Tapping the profile icon in the upper-right corner accesses settings, while categories are accessible via a bottom navigation bar or swipe gestures to switch between sections. This categorical structure allows users to manage passes grouped by type, such as health-related items in supported countries, ensuring efficient organization without overwhelming the interface. To enhance accessibility and streamline contactless payments, users can set Google Wallet as the default payment app on their Android device. Open the Settings app, search for “NFC,” tap NFC > Contactless payments > Payment default, select Google Wallet, and tap OK to confirm. Steps may vary depending on the device. On Samsung devices, ensure Samsung Wallet is not set as the default in the same menu, and optionally configure the side button to launch Google Wallet for quicker access. Google Wallet incorporates Material You theming, introduced with , which dynamically adapts colors from the user's wallpaper to generate personalized palettes for app elements like buttons and backgrounds. This adaptive theming extends to dark mode support, which follows the device's system-wide setting to reduce eye strain and conserve battery on screens, applying darker surfaces while maintaining readability through limited color accents. Accessibility features in the Google Wallet app integrate with Android's built-in tools, including TalkBack screen reader support to provide spoken feedback for icons, buttons, and text, enabling eyes-free navigation through gestures. Options for larger text sizes and high-contrast modes enhance visibility, while haptic feedback delivers tactile confirmation for taps and swipes, aiding users with motor impairments. These elements ensure compliance with Android accessibility standards, allowing customization via device settings without altering core functionality. On devices, the Google Wallet interface supports watch face complications, permitting quick glances at payment card details or pass statuses directly from the watch face without opening the app. Gesture-based navigation, such as wrist tilts or flicks, facilitates hands-free interaction, with the double-tap side button often mapped to launch Wallet for contactless payments. This compact design prioritizes glanceability on small screens, integrating seamlessly with gestures enabled by default. In 2025, Google Wallet received a redesign incorporating Material 3 Expressive elements, rolling out via server-side updates to version 25.38 and beyond, which enhances pass previews with smoother animations, card-like list items, and real-time updates for travel information like flight statuses. This update, aligned with Android 16's expressive design language, improves visual hierarchy for better pass organization and personalization, making previews more dynamic and informative on both phones and watches.

Integrations and Ecosystem

Device and platform compatibility

Google Wallet primarily supports Android devices running version 9.0 () or higher, with (NFC) hardware and host card emulation (HCE) capabilities required for features. This ensures secure tokenization and transaction processing, though not all budget Android devices include NFC, limiting compatibility to mid-range and flagship models from manufacturers like , , and others. On Samsung devices, users may need to set Google Wallet as the default payment app by navigating to NFC settings, tapping Contactless payments > Default payment app, and selecting Google Wallet, especially if Samsung Wallet is currently set as the default. For wearable devices, Google Wallet is compatible with smartwatches running version 2.18 or higher, enabling tap-to-pay and pass storage on models such as the Google Pixel Watch series. Older versions receive limited or no support, with features like contactless payments restricted to updated hardware. Access to Google Wallet is also available via the web at wallet.google.com, allowing users to view, manage, and add passes, loyalty cards, and other items from any modern browser on desktops or mobile devices. There is no native app for Google Wallet. Certain advanced features impose additional hardware requirements; for instance, NFC with HCE is essential for all contactless payments across supported regions, while digital car keys in Google Wallet necessitate or later and may require (UWB) technology on devices like and newer for enhanced passive entry and proximity detection. is maintained for legacy users, as payment cards and passes from the former Android Pay service automatically migrate to Google Wallet upon signing in with the associated on a compatible device.

Partnerships with services and providers

Google Wallet has established key partnerships with major networks to facilitate secure tokenization and . Visa collaborates with Google Wallet to enable tokenization for fleet cards and broader integration, allowing users to add Visa cards for contactless payments while replacing sensitive card details with secure tokens. supports similar tokenization through its integration with Google Wallet, enabling users to store and use credentials for in-store and online transactions with enhanced security. partners via its Token Service to provide digital payment solutions, allowing Amex cardholders to add cards to Google Wallet for seamless mobile payments. Banks such as Chase further extend these capabilities through virtual card support in Google Wallet. Chase enables users to add its Visa cards to Google Wallet for contactless payments and integrates virtual credit card numbers, which can be stored in the wallet for secure, temporary use in digital transactions. This partnership enhances user flexibility by allowing virtual cards to function within Google Wallet's ecosystem, including compatibility with digital wallets for in-app and online purchases. In the transit sector, Google Wallet partners with providers like the (WMATA) to support contactless fare payments via SmarTrip integration. Users can add their SmarTrip card to Google Wallet for tapping on Metro rail, buses, and parking without needing a physical card. Similarly, (TfL) collaborates to enable contactless payments across the London Underground, buses, and other services using Google Wallet, leveraging the city's tap-and-go system for daily commuting. For event and travel ticketing, Google Wallet integrates with issuers such as , allowing users to add digital tickets directly from their accounts for easy scanning at venues. supports ticket addition to Google Wallet through its app, enabling attendees to store and access event passes securely on their devices. Airlines like Delta partner to facilitate storage in Google Wallet, where users can save passes from the Delta app for offline access during travel. Google Wallet's digital identity features stem from partnerships with state Departments of Motor Vehicles (DMVs), including Arizona, California, Colorado, Georgia, Maryland, and Arkansas (as of October 2025). In Colorado, residents can add their state-issued driver's license or ID to Google Wallet as a secure digital copy, complementing the physical card. Georgia's Department of Driver Services enables similar integration, allowing eligible users to store their digital driver's license in Google Wallet for verification purposes. Additionally, collaborations with university systems provide student ID support; for instance, the University of Arizona integrates its CatCard into Google Wallet for campus access and payments, while Purdue University offers mobile credentials via the wallet for building entry and services. In 2025, Wallet expanded through EU initiatives aligned with regulations for wallets. A partnership with launched the first Wallet-based age verification service in , with a pilot in July 2025 that is ongoing as of November 2025, enhancing compliance with 2.0 for secure identity proofs across the bloc. Family sharing features, integrated via and Family Link, allow parents to manage children's wallets, including card approvals and pass storage, promoting safer usage for minors.

API and developer tools

The Google Wallet API provides third-party developers with RESTful endpoints to create, manage, and distribute digital passes, such as loyalty cards, offers, and event tickets, enabling seamless integration into applications and websites. This API supports the issuance of passes through JSON payloads or signed JSON Web Tokens (JWTs), allowing developers to generate "Add to Google Wallet" links for user adoption. For authentication, developers use JWTs signed with a Google Cloud service account key, authorized via the Google Wallet Business Console, which serves as the central developer portal for managing issuer accounts, API keys, and pass configurations. Complementing the core API, the Smart Tap API facilitates NFC-based interactions by enabling passes to trigger actions like app launches, content sharing, or redemption at compatible terminals without requiring additional hardware. Developers configure Smart Tap within pass objects to define collector IDs and class-specific behaviors, supporting use cases such as loyalty point redemptions or event check-ins via . The Google Wallet Android SDK further simplifies integration by providing native methods to check API availability, add passes directly from apps, and handle save-to-wallet flows, reducing the need for backend dependencies. To streamline development, the includes pre-built templates for common pass types, such as loyalty cards with customizable fields for images, barcodes, and messaging, which developers can extend at the class level to apply consistent styling across multiple objects. These templates support pass objects that inherit class-level properties, ensuring uniformity while allowing instance-specific updates like balance changes or expiration dates. In 2025, enhanced the with support for real-time updates through integration with Android 16's Live Updates feature, allowing dynamic notifications for passes related to , events, and transit, such as flight status or train delays, delivered via expanded SDK capabilities. This update builds on the 's existing mechanisms for inserting messages and patching objects, enabling developers to push live data to users' wallets without manual refreshes.

Financial and Payment Services

Contactless payments

Google Wallet enables users to make in-person contactless payments by tapping their NFC-enabled Android device on a point-of-sale (POS) terminal, simulating a physical card transaction without needing to present an actual card. This feature leverages (NFC) technology to securely transmit payment information to compatible merchants, allowing for quick and convenient checkout experiences at retail locations, restaurants, and other businesses equipped with contactless readers. The underlying NFC tap mechanism in Google Wallet utilizes host card emulation (HCE), a software-based approach that enables the device to emulate a directly at the POS terminal without requiring specialized hardware. This process supports the contactless standard, a global specification for secure chip-based s that ensures with networks like Visa and . During a transaction, the device generates dynamic , including a one-time , to authenticate the securely. Contactless payments through Google Wallet are accepted at millions of locations worldwide wherever the contactless symbol or Google Pay branding is displayed, facilitated by the extensive Google Pay network that integrates with major card issuers and payment processors. Users can select from multiple added cards at the point of sale if needed, enhancing flexibility for different payment preferences. Transaction limits for these payments vary by card issuer and region; for example, in the US, many issuers enforce a default limit of around $100 for contactless transactions without requiring a PIN or additional verification, after which a signature or PIN may be prompted for higher amounts. Google Wallet supports offline functionality for contactless payments in areas with poor or no connectivity by caching encrypted payment credentials and on the device, allowing transactions to proceed and sync later once a connection is restored. This ensures reliability in remote or low-signal environments, such as during or in rural areas. Unlike online , contactless transactions bypass web browsers entirely, relying solely on direct NFC interaction for enhanced speed, with most completing in under one second to minimize wait times at checkout. For added security, Google Wallet employs device tokenization, replacing actual card numbers with unique virtual during NFC communications to prevent exposure of sensitive data.

Online and in-app transactions

Google Wallet facilitates seamless online and in-app transactions by integrating with web browsers and mobile applications, allowing users to complete purchases without manually entering details each time. Through the Google Pay API, developers can implement one-tap checkout on websites via Chrome and within Android apps, providing a streamlined experience for users with saved cards in their . This integration enables merchants to offer fast, secure transactions to hundreds of millions of Google users worldwide. A key feature for online forms is saved card autofill, which securely populates payment fields during checkout on Chrome and Android devices. When users have eligible payment methods stored in Google Wallet, the autofill option suggests tokenized or virtual card details rather than exposing the full card number, enhancing by preventing merchants from accessing sensitive information. This process requires user authentication, such as a PIN, , or face unlock, to confirm the autofill action. To further mitigate fraud risks in online purchases, Google Wallet supports virtual card numbers, which generate temporary card details for transactions depending on the issuer. Users can enable virtual cards for eligible credit or debit cards added to their Wallet, sharing only the virtual number with merchants during in-app or web checkouts instead of their physical card information. This approach limits exposure if a merchant's systems are compromised. Transactions initiated through Google Wallet sync across devices, allowing payments started on a phone to continue seamlessly on the web via the user's . This cross-device functionality ensures that saved payment methods and preferences are consistently available, whether shopping on mobile or desktop. Additionally, Google Wallet integrates buy-now-pay-later (BNPL) options from providers like Affirm, , and , enabling users to split purchases into installments directly at checkout without needing separate apps. Users can access detailed analytics of their online and in-app transactions within the Google Wallet app or the dedicated , where a chronological history of payments is displayed, including details, amounts, and dates. For record-keeping, transaction data can be exported via , allowing downloads in formats like or CSV for personal review or integration with financial software. This contrasts with in-store contactless payments, which may require separate device verification but share the same secure backend.

QR code and alternative payment methods

Google Wallet supports payments as an alternative to contactless NFC transactions in select regions, allowing users to scan merchant-generated s for quick settlements. In , for instance, integration with the (UPI) enables users to open the app—linked to Google Wallet—and scan a static or dynamic at merchants to complete payments instantly from linked bank accounts. This feature has become widespread, with UPI QR transactions surging 91.5% to 657.9 million in March 2025 alone, reflecting its role in 's digital payment ecosystem. In , Google Wallet users could generate or scan QR codes for card-based payments until December 8, 2025, after which support for credit and debit cards in this method ends, prompting a shift to the app for continued QR functionality. Availability in other markets like remains limited due to regulatory restrictions on services, where local alternatives dominate QR payments. Peer-to-peer (P2P) transfers provide another non-NFC option, permitting users to send or request money using a recipient's phone number or . In regions like , this leverages UPI for seamless transfers, including split-bill features where groups can divide costs and settle via the app. However, P2P functionality was discontinued in the starting June 4, 2024, limiting it to international markets where operates. Alternative integrations extend to voice-activated payments through , where users can command "Hey Google, pay with " to initiate transactions, confirming details via voice or screen for security. In-app wallets further complement this, as seen with services like , where serves as a stored payment method for seamless rideshare bookings without re-entering details. These methods are not universally available, varying by and device compatibility, with fallbacks to manual entry or traditional cards in unsupported areas.

Availability and Regional Support

Supported countries and regions

Google Wallet provides full support for its core features, including contactless payments, online transactions, and digital passes, in over 140 countries and territories as of 2025. This encompasses major markets such as the , , , , and , where users can add eligible and debit cards from participating banks to enable seamless NFC-based tap-to-pay at millions of merchants. In these regions, the app integrates with local payment networks like Visa, , and regional systems, supporting both in-store and in-app purchases without additional hardware beyond NFC-enabled Android devices. Partial support extends to additional areas, with NFC contactless payments available across nations regardless of the issuing bank, provided the device and merchant terminals are compatible. For instance, users in countries like and can store and present digital passes such as event tickets or vaccination cards, though full payment functionality may require cards from supported local issuers. These variations stem from regulatory approvals, banking partnerships, and infrastructure readiness, limiting certain features like peer-to-peer transfers to select markets. Upcoming expansions are underway to broaden accessibility, with planned rollouts in —including the and other countries—driven by rapid mobile adoption and partnerships with regional fintechs, and pilot programs in . Region-specific restrictions apply universally: payment methods must be issued by banks in supported countries to comply with local financial regulations, while features like digital IDs and car keys are confined to the issuing for and legal reasons. Historically, Google Wallet originated as a U.S.-only service in 2011, focusing on NFC payments in select cities, before being discontinued in 2015. Post-2018 expansions accelerated under the umbrella, which unified payment services and enabled international growth to over 40 countries by 2020, paving the way for the 2022 revival of Google Wallet with global scalability. This phased rollout prioritized high-adoption markets before extending to emerging regions, adapting to varying NFC infrastructure and data privacy laws.

Loyalty programs and cards

Google Wallet enables users to store digital versions of loyalty and membership cards from numerous retailers and programs worldwide, facilitating convenient access to rewards during purchases. These cards are added manually via the app by searching for the merchant, scanning a , or linking through the issuer's app or , and they integrate seamlessly with the wallet's interface for quick presentation at checkout. The platform supports or display for scanning by retailers, ensuring compatibility with point-of-sale systems. In the United States, prominent supported programs include Rewards and myWalgreens. Users can add their loyalty card to Google Wallet, allowing them to earn and redeem stars by presenting the digital at stores or via contactless payments. Similarly, ' Balance Rewards (now myWalgreens) has been integrable since 2016, when it became the first retail to link with Android Pay, Google's predecessor to Wallet, enabling users to load their membership number and track rewards alongside transactions. Other U.S. examples encompass CVS ExtraCare and various pharmacy and grocery chains that utilize the Google Wallet API for pass creation. Internationally, Google Wallet accommodates programs like the in the , where users can digitize their card for points accumulation on grocery purchases, and in , Air Canada's frequent flyer loyalty scheme, which stores the membership card for earning miles at partner retailers. The Google Wallet API facilitates these integrations by allowing merchants to issue customizable loyalty passes with fields for balance, points, and images, supporting over a thousand programs globally through developer tools that enable real-time updates and notifications. Features such as points tracking appear on the card interface when provided by the issuer, while expired loyalty passes are automatically grouped in a dedicated section of the app for easy management, though specific expiration alerts depend on merchant-implemented push notifications. Region-specific limitations exist, with certain programs unavailable outside their primary markets due to partnership requirements; for instance, major Chinese retail chains like those operated by Alibaba are not directly supported in Google Wallet absent formal API integrations. Cards are securely stored within the Google Wallet app, accessible across compatible Android devices and smartwatches for on-the-go use.

Transit systems and access controls

Google Wallet enables users to make contactless payments for public transit fares in select cities by storing supported credit or debit cards in the app, allowing a simple tap at fare gates or readers. In the United States, this includes integration with the and buses managed by the (MTA), where users tap their Android device to pay without opening the app or managing physical cards. Similarly, in , Google Wallet works with the system for the () trains and Pace buses, supporting tap-and-go transactions that draw from linked payment methods for seamless commuting. In the , Google Wallet does not support direct addition of physical Oyster cards, but it facilitates contactless pay-as-you-go payments on (TfL) services, including the Underground, buses, trams, and Overground, using compatible bank cards stored in the app. Google Wallet also supports digital car keys for vehicle access, allowing users to lock, unlock, and start compatible cars via NFC or Ultra-Wideband (UWB) technology on their Android device. This feature is available for models equipped with Digital Key Plus, which uses UWB for precise proximity detection, and Hyundai vehicles with Digital Key 2, enabling similar secure interactions. Digital keys stored in Google Wallet can be securely shared with family members or designated users through the app's sharing options. Beyond transit and vehicles, Google Wallet integrates with NFC-based access controls for various venues. Users can store digital tickets for stadium entry, tapping their phone at gates for quick validation and fraud prevention in sports events and concerts. For accommodations, it supports hotel room keys issued by participating properties, where guests hold their NFC-enabled device near door readers to gain secure entry without physical keycards. Expansions continue, with ongoing developments in including a planned Express Transit Card feature, which would allow payments without unlocking the device for faster interactions at gates. Certain e-money transit cards face regional limitations in Google Wallet; for instance, Japan's card, while addable for use, cannot be reloaded outside due to restrictions on international methods.

Digital IDs and car keys

Google Wallet enables users to store and present government-issued digital identities, including driver's licenses and state IDs from ten U.S. states as of late 2025. Supported states include (since 2023), , , , Georgia, , , , , and . These digital IDs allow verification at TSA checkpoints through biometric matching, such as facial recognition, while maintaining via selective disclosure, where only essential information is shared without revealing the full document. In select countries, Google Wallet supports as ID passes, primarily for U.S. and U.K. passport holders, usable at supported TSA security checkpoints in the U.S. for identity verification during air travel. Upcoming expansions include support for more international passports, aligning with broader initiatives. For non-government IDs, Google Wallet accommodates IDs from over 200 universities across the U.S., , and other regions, integrated through service providers like Transact and CBORD for campus access and payments. It also supports health cards, including digital copies of cards and records, stored securely for use at medical facilities or pharmacies. Google Wallet's digital car key feature allows users to lock, unlock, and start compatible vehicles using their Android phone or , supporting passive entry where the device detects proximity via (UWB) or NFC technology. Supported models include 2023 and later vehicles such as select Chevrolet, GMC, and lines, with expansions to additional brands like , Hyundai, and Kia. Looking ahead, Google Wallet is positioned to integrate with the European Union's full digital ID wallet initiative, expected to roll out by 2026, enabling EU citizens to store national IDs, driver's licenses, and other documents for cross-border use.

References

  1. https://support.google.com/wallet/answer/11951709?hl=en
  2. https://www.google.com/wallet/
  3. https://www.nytimes.com/2025/11/14/travel/digital-identification-travel.html
  4. https://www.theguardian.com/technology/2011/sep/19/google-wallet-available-public
  5. https://www.dintero.com/newsroom/blog/the-history-of-google-pay
  6. https://techcrunch.com/2022/05/11/google-launches-google-wallet/
  7. https://9to5google.com/2022/07/20/google-wallet-rolling-out/
  8. https://wallet.google/intl/en_us/
  9. https://blog.google/products/google-pay/google-wallet-age-identity-verifications/
  10. https://support.google.com/wallet/answer/12060038?hl=en
  11. https://blog.google/technology/families/google-new-built-in-protections-kids-teens/
  12. https://android.gadgethacks.com/news/google-wallets-new-feature-predicts-your-pass-needs/
  13. https://support.google.com/googlepay/answer/14555219
  14. https://www.androidauthority.com/google-wallet-2022-3163117/
  15. https://nfcw.com/2022/07/20/378135/google-rolling-out-new-multifunction-mobile-wallet-to-39-countries/
  16. https://commerce.googleblog.com/2011/09/launching-google-wallet-on-sprint-and.html
  17. https://abcnews.go.com/Technology/google-launches-google-wallet/story?id=14558391
  18. https://www.nfcw.com/2011/05/26/37720/google-wallet-day-one-for-nfc/
  19. https://techcrunch.com/2011/05/26/google-wallet-offers/
  20. https://arstechnica.com/gadgets/2011/05/get-discounts-pay-with-your-phone-with-google-wallet-offers/
  21. https://www.siliconrepublic.com/life/google-wallet-arrives-in-the-us
  22. https://www.reuters.com/article/technology/google-wallet-a-security-risk-researchers-idUSTRE81A00L/
  23. https://www.paymentsdive.com/ex/mpt/news/security-company-finds-pin-protecting-google-wallet-may-be-vulnerable/
  24. https://techcrunch.com/2011/10/02/paypal-on-google-wallet-mass-adoption-of-nfc-is-years-away/
  25. https://www.cnet.com/tech/services-and-software/google-wallet-to-discontinue-prepaid-cards-in-october/
  26. https://www.theverge.com/2013/9/17/4740566/google-wallet-now-available-all-android-phones-every-us-carrier
  27. https://allthingsd.com/20130917/with-ios-version-on-tap-new-google-wallet-for-android-moves-past-nfc/
  28. https://martech.org/has-google-wallet-failed/
  29. https://android.googleblog.com/2015/09/tap-pay-done.html
  30. https://techcrunch.com/2016/08/26/google-wallet-debuts-automatic-transfers-so-you-can-skip-cashing-out/
  31. https://techcrunch.com/2016/03/31/bye-google-wallet-cards/
  32. https://blog.google/products/google-pay/announcing-google-pay/
  33. https://blog.google/products/google-pay/reimagined-pay-save-manage-expenses-and-more/
  34. https://blog.google/technology/developers/io-2022-100-things/
  35. https://www.engadget.com/google-wallet-io-2022-182503938.html
  36. https://www.theverge.com/2022/7/18/23269186/google-wallet-pay-app-rollout-39-countries
  37. https://developers.google.com/wallet/smart-tap
  38. https://support.google.com/wallet/answer/12060038
  39. https://www.androidcentral.com/apps-software/google-wallet-update-rollout
  40. https://www.purdue.edu/newsroom/2023/Q2/purdue-launches-purdue-mobile-id-for-students-allowing-them-to-get-around-campus-with-just-a-simple-tap-of-their-mobile-device
  41. https://arstechnica.com/gadgets/2022/07/google-wallet-rolls-out-to-users-will-live-alongside-google-pay-in-the-us/
  42. https://www.zdnet.com/article/google-wallet-brings-digital-ids-to-more-states/
  43. https://www.financemagnates.com/fintech/google-wallet-goes-live-in-india-in-partnership-with-local-service-providers/
  44. https://developers.googleblog.com/en/explore-the-latest-updates-google-wallet-io-25/
  45. https://developers.google.com/wallet/docs/release-notes
  46. https://support.google.com/wallet/answer/16305341?hl=en
  47. https://9to5google.com/2025/10/20/google-wallet-live-updates/
  48. https://www.androidauthority.com/google-wallet-android-16-live-updates-3608801/
  49. https://9to5google.com/2025/11/07/google-wallet-purchase-pass-personalization/
  50. https://www.digitaltrends.com/phones/new-google-wallet-setting-uses-your-shopping-history-for-personalized-ads/
  51. https://ibsintelligence.com/ibsi-news/google-wallet-forays-into-india-to-streamline-finances-for-android-users/
  52. https://ec.europa.eu/digital-building-blocks/sites/spaces/EUDIGITALIDENTITYWALLET/pages/694487738/EU%2BDigital%2BIdentity%2BWallet%2BHome
  53. https://www.phocuswire.com/how-european-digital-identity-wallet-impact-travel-2025
  54. https://passkit.com/blog/mobile-wallet-monthly-october-2025/
  55. https://9to5google.com/2025/10/14/google-wallet-nickname-passes/
  56. https://support.google.com/wallet/answer/12058983?hl=en
  57. https://support.google.com/wallet/answer/12059603?hl=en
  58. https://support.google.com/googlepay/answer/11234179?hl=en&co=GENIE.Platform%253DAndroid
  59. https://support.google.com/wallet/answer/12059256?hl=en
  60. https://support.google.com/wallet/answer/12059519?hl=en
  61. https://support.google.com/wallet/answer/12200245?hl=en
  62. https://support.google.com/wallet/answer/14260807?hl=en
  63. https://support.google.com/wallet/answer/15797843?hl=en
  64. https://developers.google.com/wallet/tickets/events
  65. https://help.ticketmaster.com/hc/en-us/articles/9612428118801-How-do-I-use-Google-Wallet-for-event-entry
  66. https://support.google.com/wallet/answer/12059518?hl=en
  67. https://support.google.com/wallet/answer/12059257?hl=en
  68. https://support.google.com/wallet/answer/13570938?hl=en
  69. https://www.engadget.com/google-wallet-can-now-automatically-add-your-movie-tickets-and-boarding-passes-214241833.html
  70. https://support.google.com/wallet/answer/14188766?hl=en
  71. https://www.theverge.com/2023/7/7/23787326/google-wallet-pass-sharing-tickets-android-update
  72. https://support.google.com/families/answer/15877353?hl=en
  73. https://blog.google/feed/google-wallet-for-kids-family-link/
  74. https://developers.google.com/wallet/generic/use-cases/expired-passes
  75. https://www.walletthat.com/help/google-wallet-supprt/
  76. https://blog.google/products/google-pay/device-tokens-google-wallet/
  77. https://www.uspaymentsforum.org/wp-content/uploads/2025/08/USPF_MTPWC-Leading-Practices-for-Securing-Mobile-and-Contactless-Payments_WP.pdf
  78. https://www.thalesgroup.com/en/solutions-catalogue/enterprise/financial-services/tokenization
  79. https://www.corbado.com/blog/how-to-use-google-pay
  80. https://support.google.com/accounts/answer/6160491?hl=en
  81. https://support.google.com/googlepay/answer/10223752
  82. https://www.getmoss.com/guide/en/is-google-pay-safe/
  83. https://www.androidpolice.com/stop-google-wallet-logging/
  84. https://developers.googleblog.com/en/google-pay-inside-sandboxed-iframe-for-pci-dss-v4-compliance/
  85. https://support.google.com/families/answer/15877348?hl=en
  86. https://support.google.com/wallet/answer/12060043?hl=en
  87. https://9to5google.com/2023/06/20/how-to-google-wallet-redesign/
  88. https://support.google.com/wallet/answer/14187052?hl=en
  89. https://eu.community.samsung.com/t5/galaxy-s25-series/set-google-pay-as-default/td-p/11711230
  90. https://source.android.com/docs/core/display/material
  91. https://support.google.com/wallet/thread/184029724/how-to-enable-dark-mode?hl=en
  92. https://support.google.com/wallet/answer/16244062?hl=en&co=GENIE.Platform%253DAndroid
  93. https://www.reddit.com/r/GalaxyWatch/comments/1bbluz4/watch_face_complication_for_google_wallet/
  94. https://support.google.com/wearos/answer/6312406?hl=en
  95. https://9to5google.com/2025/10/02/google-wallet-material-3-expressive-redesign-wide/
  96. https://www.androidpolice.com/google-wallet-material-3-expressive-redesign-rolls-out/
  97. https://www.techradar.com/phones/android/google-wallet-is-adding-support-for-one-of-the-best-new-features-in-android-16
  98. https://support.google.com/wallet/answer/12653781?hl=en
  99. https://developers.google.com/pay/issuers/overview/supported-devices
  100. https://wallet.google.com/
  101. https://developers.google.com/wallet
  102. https://support.google.com/wallet/answer/12060041?hl=en
  103. https://www.android.com/digital-car-key/
  104. https://investor.visa.com/news/news-details/2025/Visa-Brings-Google-Pay-Integration-to-Fleet-Cards-Enabling-Tokenization-and-Push-to-Wallet-Across-the-Digital-Wallet-Ecosystem/default.aspx
  105. https://www.mastercard.co.uk/en-gb/personal/ways-to-pay/wearables-and-mobile-payment/google-pay.html
  106. https://network.americanexpress.com/globalnetwork/v4/partners/overview-payments/
  107. https://www.chase.com/digital/digital-payments/google-pay
  108. https://www.chase.com/personal/credit-cards/education/basics/virtual-credit-cards
  109. https://www.wmata.com/fares/MobilePay/GooglePay.cfm
  110. https://wallet.google/transit/tfl/
  111. https://www.eventbrite.com/help/en-us/articles/783059/how-to-use-the-eventbrite-app/
  112. https://dmv.colorado.gov/colorado-id-in-google-wallet
  113. https://dds.georgia.gov/georgia-licenseid/ga-digital-id/digital-id-google-wallet
  114. https://catcard.arizona.edu/card-options/google-wallet
  115. https://www.purdue.edu/treasurer/finance/card/mobile-id/
  116. https://idtechwire.com/google-and-sparkassen-finanzgruppe-launch-eus-first-google-wallet-based-age-verification/
  117. https://developers.google.com/wallet/reference/rest
  118. https://developers.google.com/wallet/generic/getting-started/auth/rest
  119. https://developers.google.com/wallet/generic/use-cases/jwt
  120. https://developers.google.com/wallet/smart-tap/introduction/overview
  121. https://developers.google.com/wallet/smart-tap/introduction/communication-flow
  122. https://developers.google.com/wallet/generic/android
  123. https://developers.google.com/wallet/retail/loyalty-cards/resources/template
  124. https://developers.google.com/wallet/generic/resources/pass-builder
  125. https://www.lightspeedhq.com/blog/near-field-communication-payments-explained/
  126. https://developer.android.com/develop/connectivity/nfc/hce
  127. https://www.securetechalliance.org/wp-content/uploads/EMV-and-NFC-WP-Final-Nov-2015.pdf
  128. https://pay.google.com/about/pay-in-store/
  129. https://theretailexec.com/payment-processing/how-tap-to-pay-works/
  130. https://9to5google.com/2023/12/20/google-wallet-without-internet/
  131. https://developers.google.com/pay/api/web/overview
  132. https://developers.google.com/pay/api/web/guides/setup
  133. https://support.google.com/googlepay/answer/142893?hl=en&co=GENIE.Platform%253DAndroid
  134. https://pay.google.com/about/pay-online/
  135. https://pay.google.com/about/
  136. https://developers.google.com/pay/api/web/guides/resources/bnpl
  137. https://support.google.com/googlepay/answer/14336825?hl=en
  138. https://support.google.com/wallet/answer/13620999?hl=en
  139. https://support.google.com/googlepay/answer/9015738?hl=en
  140. https://support.google.com/pay/india/answer/14980962?hl=en
  141. https://ddnews.gov.in/en/upi-qr-codes-record-91-5-surge-to-657-9-million-credit-card-growth-slows/
  142. https://support.google.com/wallet/answer/13836932?hl=en
  143. https://www.caixinglobal.com/2025-09-17/china-pilots-unified-cross-border-qr-code-payment-system-102363389.html
  144. https://support.google.com/pay/india/answer/11428814?hl=en
  145. https://support.google.com/googlepay/answer/14555219?hl=en
  146. https://blog.clover.com/use-google-assistant-to-make-payments-with-your-voice/
  147. https://support.google.com/wallet/answer/12060037?hl=en
  148. https://www.chargeflow.io/blog/apple-pay-vs-google-pay-statistics-adoption-rates-market-share
  149. https://support.google.com/googlepay/answer/12429287?hl=en
  150. https://worldpopulationreview.com/country-rankings/google-pay-countries-list
  151. https://www.abs-cbn.com/news/technology/2025/11/12/google-pay-seen-coming-soon-to-the-philippines-other-asean-countries-2343
  152. https://developers.google.com/wallet/retail/loyalty-cards
  153. https://9to5google.com/2016/08/22/android-pay-walgreens-balance-loyalty-program/
  154. https://www.capitalmatters.co.uk/posts/loyalty-cards-google-pay
  155. https://www.androidpolice.com/google-wallet-features-replace-other-apps/
  156. https://developers.google.com/wallet/retail/loyalty-cards/use-cases/expired-passes
  157. https://developers.google.com/wallet/retail/loyalty-cards/resources/faq
  158. https://wallet.google/transit/mta/
  159. https://www.ventrachicago.com/googlepay/
  160. https://wallet.google/transit/ventra/
  161. https://support.google.com/wallet/thread/177760639/why-i-can-t-add-my-oyster-card-to-the-wallet-transport-section?hl=en
  162. https://support.google.com/android/answer/12060041?hl=en
  163. https://faq.bmwusa.com/s/article/FAQ-Setting-Up-A-BMW-Digital-Key-Plus-For-Android-BMW-How-To-lzrc4?
  164. https://www.hyundai.com/eu/en/driving-hyundai/owning-a-hyundai/discover-myhundai-app/digital-key.html
  165. https://to-sports.com/pages/nfc-guide-and-stadium-access
  166. https://developers.google.com/wallet/access/hotel-key/get-started/overview
  167. https://support.google.com/wallet/answer/15067781?hl=en
  168. https://www.androidauthority.com/google-wallet-express-transit-card-3612267/
  169. https://support.google.com/wallet/answer/13145603?hl=en
  170. https://9to5google.com/2025/10/11/google-wallet-state-ids/
  171. https://support.google.com/wallet/answer/12436402
  172. https://support.google.com/wallet/answer/15284332
  173. https://developers.google.com/wallet/access/campus-id/get-started/overview
  174. https://www.stocktitan.net/news/ROP/transact-idx-adds-mobile-credentials-to-apple-and-google-wallets-ejwoiyidogij.html
  175. https://developers.google.com/wallet/health
  176. https://support.google.com/wallet/answer/12059257
  177. https://support.google.com/wallet/answer/12060041
  178. https://gmauthority.com/blog/2025/06/gm-digital-key-will-include-apple-wallet-compatibility/
  179. https://www.biometricupdate.com/202510/eu-updates-plan-for-rollout-of-digital-wallets-mdls
Add your contribution
Related Hubs
User Avatar
No comments yet.