# Google Wallet

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

Google payment apps :
2006–2013Google Checkout :
| 2015–2018Android Pay | 2015–2018Android Pay | | | 2015–2018Google Wallet | 2015–2018Google Wallet | 2015–2018Google Wallet | 2015–2018Google Wallet | 2015–2018Google Wallet | 2015–2018Google Wallet | 2017–2018Tez | 2017–2018Tez | 2017–2018Tez | 2017–2018Tez | 2017–2018Tez | 2017–2018Tez |
| 2018–2022Google Pay | 2018–2022Google Pay | | | 2018–2020Google Pay Send | 2018–2020Google Pay Send | 2018–2020Google Pay Send | 2018–2020Google Pay Send | 2018–2020Google Pay Send | 2018–2020Google Pay Send | 2018–2020Google Pay | 2018–2020Google Pay | 2018–2020Google Pay | 2018–2020Google Pay | 2018–2020Google Pay | 2018–2020Google Pay |
| 2022–presentGoogle Wallet | 2022–presentGoogle Wallet | 2022–presentGoogle Wallet | 2022–presentGoogle Wallet | 2022–presentGoogle Wallet | 2022–presentGoogle Wallet | | | | | | | | | 2020–presentGoogle Pay | 2020–presentGoogle Pay | 2020–presentGoogle Pay | 2020–presentGoogle Pay | 2020–presentGoogle Pay | 2020–presentGoogle Pay |
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. 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. 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. 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.

### Google Wallet (2011) launches

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.
The original version of Google Wallet allowed users to make point-of-sale purchases with their mobile devices using near-field communication (NFC) technology. As of September 2015, however, Google dropped NFC from Google Wallet, offering the technology only through Android Pay, which was a separate application available only to Android users. As a result, any gift cards, loyalty programs, and promotional offers stored in an older version of Google Wallet could no longer be used.

### Android Pay launches

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. It also used technology from the carrier-backed Softcard—Google had acquired its intellectual property in February 2015. At launch, the service was compatible with 70% of Android devices and was accepted at over 700,000 merchants. The old Google Wallet still powered web-based Play Store purchases and some app-based peer-to-peer payments.
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.
On September 18, 2017, Google launched a payments app in India known as Tez, utilizing the Unified Payments Interface (UPI). On August 28, 2018, Google rebranded Tez to Google Pay.

### Android Pay and Google Wallet become Google Pay

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. 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. Google Pay adopts the features of both Android Pay and Google Wallet through its in-store, peer-to-peer, and online payments services.
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. The rebranded service provided a new API that allows merchants to add the payment service to websites, apps, Stripe, Braintree, and Google Assistant. The service allows users to use the payment cards they have on file in their Google Account.

### Google Pay becomes Google Wallet (2022)

In January 2022, Bloomberg News reported that the company was planning to transform Google Pay into a "comprehensive digital wallet", following the app's reported slow growth and the shutdown of Plex. 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. Google officially announced Google Wallet on May 11, 2022, at the 2022 Google I/O keynote. 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. 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

In its UK launch, 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. 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. Android Pay was launched in Singapore on June 28, 2016 and in Australia on July 14, 2016.
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.
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.
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. Cardholders of participating Mastercard partner banks for these countries will be able to use the Google Pay service through their respective mobile banking apps.
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. 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.

## Features

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.
Digital car keys in Google Wallet can still be utilized when the screen is off or the battery is depleted.
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. At Google I/O 2024, Google announced that "expanded support for passes of all types" would be coming to Wear OS and Fitbit OS.

### Comparison between phone and wearable versions

| Feature | Wear OS | Fitbit OS | Notes |
| Pay with EMV payment cards via Google Pay | Partial | Partial | Some payment cards are not supported on Wear OS or Fitbit OS. |
| Pay with FeliCa payment cards via Google Pay | | | For Wear OS: Only for Pixel Watches, Galaxy Watch Ultra, and Galaxy Watch6 or later devices purchased in Japan. |
| Pay via QR code | | | For Android: Only available in Brazil. |
| Store passes | Partial | Coming soon | For Wear OS: Private passes are not supported. Smart Tap (NFC) passes only show their fallback QR code/barcode/number. |
| Store campus identifications | Partial | | |
| Store corporate badges | Partial | Coming soon | |
| Store government-issued identifications | | | |
| Store hotel keys | | | |
| Store digital car keys | Partial | | For Android: Only for select devices, most notably Pixel Fold, Pixel 6, & Pixel 6a or later devices. For Wear OS: Only BMW & MINI keys are supported. Only for Pixel Watch 3. |
| Store MIFARE/ITSO/EMV transit cards | Partial | Partial | For Android: iPASS can only be stored on Xiaomi 14T/14T Pro. For Wear OS: Only SmarTrip, Clipper, ORCA, and PRESTO are supported. For Fitbit OS: iPASS can only be stored on Sense Series Versa 2 Series and above (excluding LITE version) Charge 4 Series and above |
| Store FeliCa transit cards | Partial | | For Android: Only for supported devices purchased in Japan. For Wear OS: Only for Suica on Pixel Watches, Galaxy Watch6 or later, and Galaxy Watch Ultra devices purchased in Japan. 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 | | | For Android: Only for supported devices purchased in Japan. |
| Store transit loyalty cards | | | |

### Skip device unlock & Battery depletion

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.
Only one class of NFC passes allows usage when the screen is unlit or the battery is depleted: car keys.

### Usage

Passes and cards stored in Wallet require varying levels of authentication in order to convey to a reader.
| 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 must be on for use via either NFC or UWB. | — |
| Use MIFARE/ITSO/EMV transit cards (except iPASS) | Phone on, phone screen lit. Some Pixel devices will wake their own screen when presented to an NFC reader. | Watch on, watch unlocked, Wallet app open. For transit networks that accept both open loop payment cards and closed loop transit cards in Wallet, the transit card must be viewed in Wallet to be transmitted in place of the payment card. | — |
| 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. | — | — |

### Pass Transfers

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.

## Ecosystem

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. 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.
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. Government-issued IDs are also supported in six American states: Arizona, California, Colorado, Georgia, Maryland, and New Mexico.

### Smart Tap

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.
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. Redbox (USA), Nando's (UK & Ireland), and Woolworth's (Australia) use it for loyalty programs. And Anytime Fitness (Globally), Keepcool (France), Club Lime (Australia), & David Lloyd Clubs (UK) use it for memberships.

## Financial services
### Google Pay

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

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.

## Availability
### Supported countries

As of March 2025, Google Wallet is available in 97 countries worldwide for both Android & Wear OS.
* Albania
* Andorra*^
* Argentina
* Armenia*
* Australia
* Austria
* Azerbaijan*
* Bahrain*^
* Belgium
* Bermuda
* Bosnia and Herzegovina
* Brazil*
* Bulgaria
* Cambodia
* Canada
* Chile
* Colombia
* Costa Rica
* Croatia
* Cyprus
* Czech Republic
* Denmark
* Dominican Republic
* Ecuador
* El Salvador
* Egypt*^
* Estonia
* Faroe Islands
* Finland
* France
* Georgia*
* Germany
* Gibraltar*^
* Greece
* Greenland
* Guatemala*^
* Guernsey
* Honduras*^
* Hong Kong
* Hungary
* Iceland
* India**
* Ireland
* Isle of Man
* Israel*
* Italy
* Japan
* Jordan
* Kazakhstan*
* Kosovo
* Kuwait
* Kyrgyzstan*
* Latvia
* Liechtenstein
* Lithuania
* Luxembourg
* Macau*^
* Malaysia
* Malta
* Mexico
* Moldova*
* Monaco
* Montenegro
* Morocco
* Netherlands
* New Zealand
* Nicaragua
* Norway
* North Macedonia
* Pakistan
* Panama
* Paraguay
* Peru
* Poland
* Portugal
* Qatar
* Romania
* San Marino
* Serbia*
* Singapore
* Slovakia
* Slovenia
* South Africa
* Spain
* Sweden
* Switzerland
* Taiwan
* Tajikistan
* Thailand
* Ukraine*
* United Arab Emirates
* United Kingdom (includes Cayman Islands)^
* United States (includes American Samoa, Guam, Puerto Rico, and Northern Mariana Islands)
* Uruguay*^
* Venezuela*^
* Vietnam*
* = Not available for Fitbit OS
** = Google Pay functionality available through Google Pay app
^ = Google Wallet website unavailable

#### Upcoming

* Bhutan
* Indonesia | March 2025
* Oman
* Saudi Arabia | April 2025
* Sri Lanka

#### Region locking

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. This behavior is in contrast to other wallets such as Apple Wallet, which allow users with any regional device model (iPhone 7) to add FeliCa-based cards.
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.
In addition, UWB functionality for car keys is limited to regions that allow the frequency to be broadcast in personal mobile devices by law.

### Supported loyalty programs

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.
| Country | Retailer | One Tap/Two Tap |
| Australia | Dan Murphy's My Dan's | |
| Australia | Woolworths' Everyday Rewards | Two Tap |
| Ireland | Nando's Nando Card | Two Tap |
| Japan | d Point | Two Tap |
| Japan | Rakuten Point Card | Two Tap |
| New Zealand | Woolworths' Everyday Rewards | Two Tap |
| Taiwan | OPEN POINT | One Tap |
| United Kingdom | Nando's Nando Card | Two Tap |
| United Kingdom | Texaco's Star Rewards | Two Tap |
| United Kingdom | Valero's SaveUP Rewards | |
| United States | Coca-Cola's Vending Pass | One Tap |
| United States | Dave & Buster's Power Card | One Tap |
| United States | Jimmy John's Freaky Fast Rewards | One Tap |
| United States | Walgreens' myWalgreens | Two Tap |
| United States | Yogurtland's Real Rewards | One Tap |

### Supported public transport systems

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, wherein the only requirement for transmitting a payment or transit card is to have the screen awake. This is not supported on Google Pay for Wear OS or Fitbit OS, however. Users with watches must open the Wallet app time each time they scan their fare payment method (except FeliCa-based fare methods).
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.
Transit loyalty 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.
| Country | Area | Direct provisioning | Wear OS support | Stored via | Fare Payment Method(s) |
| Australia | Queensland | — | — | — | Payment cards |
| Australia | Sydney | — | — | — | Payment cards |
| Australia | Victoria | | | Host Card Emulation | Myki |
| Brazil | Rio de Janeiro (only MetrôRio) | — | — | — | Payment cards |
| Brazil | São Paulo (only SPTrans) | — | — | — | Payment cards |
| Canada | Ontario (TTC, GO Transit, Brampton Transit, MiWay, Oakville Transit and UP Express.) | | | Host Card Emulation | PRESTO |
| Canada | Ontario (TTC, GO Transit, Brampton Transit, MiWay, Oakville Transit and UP Express.) | — | — | — | Payment cards- VISA, Mastercard and American Express accepted. UP Express also accepts Interac debit cards. |
| Canada | Vancouver | — | — | — | Payment cards |
| Greece | Athens | — | — | — | Payment cards (pilot program at the airport — buses X93, X95, X96, X97) |
| Hong Kong | Countrywide | | | Secure Element via Octopus app | Octopus |
| Japan | Countrywide | | | Secure Element via Osaifu-Keitai app | Suica |
| Japan | Countrywide | | | Secure Element via Osaifu-Keitai app | PASMO |
| Mexico | CDMX (only Mexico City Metrobús and Mexico City Metro) | — | — | — | Payment cards |
| Singapore | Countrywide | — | — | — | Payment cards |
| Slovakia | Countrywide | | | Host Card Emulation | Ubian |
| Spain | Madrid | | | Host Card Emulation | Tarjeta Transporte Público (in public beta) |
| Taiwan | Countrywide | | | Secure Element | iPASS |
| Taiwan | Kaohsiung | — | | — | Payment cards- VISA and Mastercard accepted. |
| Taiwan | New Taipei Metro | — | | — | Payment cards- Mastercard are accepted by Ankeng and Danhai light rail. |
| Taiwan | Taichung Metro | — | | — | Payment cards- VISA accepted. |
| Taiwan | Taoyuan Airport MRT | — | | — | Payment cards- VISA and Mastercard accepted. |
| Ukraine | Kyiv | — | — | — | Payment cards |
| United Kingdom | Brighton and Hove | | | | Transit loyalty card connected to payment card |
| United Kingdom | Edinburgh | — | — | — | Payment cards |
| United Kingdom | London | — | — | — | Payment cards |
| United Kingdom | Manchester | — | — | — | Payment cards |
| United Kingdom | Tyne and Wear | | | Host Card Emulation | Pop |
| United Kingdom | West Midlands | | | Host Card Emulation | Swift |
| United States | Chicago | | | Host Card Emulation | Ventra |
| United States | Chicago | — | — | — | Payment cards |
| United States | Dallas | — | — | — | Payment cards |
| United States | Las Vegas | | | Host Card Emulation | Contactless ticket |
| United States | Miami | — | — | — | Payment cards |
| United States | Monterey | | | | Transit loyalty card connected to payment card |
| United States | New York City | — | — | — | Payment cards |
| United States | Portland, Oregon | | | Host Card Emulation | Hop Fastpass |
| United States | Portland, Oregon | — | — | — | Payment cards |
| United States | San Francisco | | | Host Card Emulation | Clipper |
| United States | Seattle | | | Host Card Emulation | ORCA |
| United States | Washington, D.C. | | | Host Card Emulation | SmarTrip |

#### Upcoming

| Country | Area | Wear OS support | Stored via | Fare Payment Method(s) |
| United Arab Emirates | Dubai | Un­known | Un­known | nol |
| United States | Los Angeles | Un­known | Un­known | Transit Access Pass |
| United States | Philadelphia | Un­known | Un­known | SEPTA Key |

### Supported car keys

These car models can be unlocked and started via NFC with 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 the Pixel Watch 3, for enhanced functionality.

### Supported government-issued identifications

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. 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. Google has also announced plans for added credentials to be able to be requested by apps to present virtually in the future. Available for devices running Android 8 or later.
| Country | Type | State |
| United States | ID | Arizona |
| United States | ID | California |
| United States | ID | Colorado |
| United States | ID | Georgia |
| United States | ID | Maryland |
| United States | ID | New Mexico |

#### Upcoming

| Country | Type | State |
| United States | ID | Arkansas |
| United States | ID | Illinois |
| United States | ID | Iowa |
| United States | ID | Ohio |
| United States | ID | Virginia |

#### Other non-government issued identifications

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 |

### Device-specific & region-locked features

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

Some devices may need Android OS or Play System updates before being compatible. The Pixel Watch 3 must be paired with a compatible Pixel phone to use digital keys.
| Brand | Model |
| Google | Pixel 6a |
| Google | Pixel 6 |
| Google | Pixel 6 Pro |
| Google | Pixel 7a |
| Google | Pixel 7 |
| Google | Pixel 7 Pro |
| Google | Pixel 8a |
| Google | Pixel 8 |
| Google | Pixel 8 Pro |
| Google | Pixel Fold |
| Google | Pixel 9 |
| Google | Pixel 9 Pro |
| Google | Pixel 9 Pro Fold |
| Google | Pixel Watch 3 |
| Motorola | Moto Edge 50 Ultra |
| Motorola | Razr 50 Ultra |
| OnePlus | 11 |
| OnePlus | Open |
| OnePlus | 12 |
| Oppo | Find N3 |
| Oppo | Find N3 Flip |
| Xiaomi | 12 |
| Xiaomi | 12 Pro |
| Xiaomi | 13 |
| Xiaomi | 13 Pro |
| Xiaomi | 13 Ultra |
| Xiaomi | 13T |
| Xiaomi | 13T Pro |
| Xiaomi | 14 |
| Xiaomi | 14 Ultra |
| Xiaomi | 14T |
| Xiaomi | 14T Pro |

#### Transit cards

| Transit card | Requirement(s) |
| iPASS | Phones: Xiaomi 14T, Xiaomi 14T Pro Wearables: Fitbit Sense or later, Fitbit Versa 2 or later, Fitbit Charge 4 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 Google Account region must be set to Japan |
| Suica | 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 |

#### e-Money cards

| e-Money card | Requirement(s) |
| Edy | Phones: Japanese models of select phones Must install Osaifu-Keitai app |
| nanaco | Phones: Japanese models of select phones Must install Osaifu-Keitai app |
| WAON | Phones: Japanese models of select phones Must install Osaifu-Keitai app |