Google Wallet in Australia

Where they differ is what's wrapped around the core payment function. Google Wallet has been more open in its dealings with Australian banks since launch in 2016, supports more transit systems natively (including Mobile myki in Victoria, which iOS doesn't have), and has consistently added support for additional passes (boarding passes, loyalty programs, event tickets, digital identification) faster than Apple Wallet has.

The product was originally called Google Pay when it launched in Australia in 2016. Google rebranded the consumer app to Google Wallet in 2022, with Google Pay continuing to exist as the underlying payment processing technology. The two names get used interchangeably in older articles and even in some current bank materials, which causes ongoing confusion. They refer to the same thing for end users.

This page covers what Google Wallet actually does for Australian Android users, the Mobile myki integration that makes it the standard choice for Melbourne commuters, how AU bank coverage compares to Apple Pay, the open-versus-closed architecture debate, and where Google Wallet's limits sit.

Quick facts

How Google Wallet works

The mechanics are the same as Apple Pay's tokenisation. When you add a card to Google Wallet:

1. Your card details are sent to your card-issuing bank for verification.
2. The bank generates a Device Account Number (a token) unique to your specific device.
3. The token is encrypted and stored in your phone's secure hardware.
4. From that point on, your real card number isn't on the device; the token is.

When you tap your phone at a contactless terminal:

1. The terminal requests payment via NFC.
2. Your phone presents the token plus a one-time cryptogram.
3. Biometric authentication (fingerprint or face unlock) or PIN confirms it's actually you.
4. The processor routes the transaction through Visa, Mastercard, American Express or eftpos to your bank.
5. Your bank authorises the payment from your underlying card account.

To the merchant it looks like a contactless card transaction. To your bank it's a transaction tied to your underlying card. To Google itself, the company isn't a participant in the money flow.

Google has been explicit about this positioning. In a public statement summarising its role: "We are not a bank nor do we have the intention of being a bank. Google is not involved in the flow of money when a transaction is made using our service. Payment cards added to Google Wallet function just like a physical card and are eligible for the same benefits offered by the issuing bank. No monies are ever transferred into Google Wallet and banks maintain full control over the set up and transaction approvals."

The framing matters because it explains why Google Wallet's AU rollout was less contested than Apple Pay's.

The open architecture story

This is the section that separates Google Wallet from Apple Pay in the Australian market.

When Apple Pay launched in 2014 and arrived in Australia in 2015, Apple sought a share of the interchange fee that banks pay on card transactions. The Big Three (CBA, NAB, Westpac) refused to negotiate on those terms, which led to a multi-year stand-off and patchy AU coverage from 2015 to 2019.

Google took a different approach. Google Wallet (then Android Pay, then Google Pay) launched in Australia in 2016 with an open architecture: Google didn't charge banks for the privilege of being supported, and the platform allowed multiple competing wallet apps to coexist on Android phones. CBA's CEO Matt Comyn made this comparison explicit in committee testimony in 2021: "Google, as I said, has a much more open architecture and allows multiple competing wallets, and it does not charge on the Android operating system."

The practical consequence in Australia: Big Four bank support for Google Wallet was effectively complete by 2017-2018, two years before Apple Pay achieved the same coverage. AU users with Android phones had universal mobile wallet access during the years when iPhone users were locked out at three of the four major banks.

This early head start matters less now (Apple Pay coverage is also universal in 2026), but it shaped the AU ecosystem. Many of the integrations that Australian banks built first, particularly the eftpos network support and the early loyalty card integrations, happened on the Google Wallet side because that's where the negotiations were faster.

Mobile myki: the AU feature iOS doesn't have

This is the standout AU feature of Google Wallet, and worth covering in detail.

Mobile myki is the digital version of Melbourne's myki transit card. It launched in March 2019 as a partnership between Public Transport Victoria, NTT Data, and Google. The Victorian government became the first Australian transit operator to offer a fully digital transit card on a phone. Within 11 weeks, almost 100,000 users had switched to Mobile myki on Android.

Mobile myki only runs on Android via Google Wallet. iPhone users in Melbourne cannot use Mobile myki and instead need to top up a physical myki card through the PTV app (which does support Apple Pay for top-ups, but not for the card itself). This is the single biggest difference between Google Wallet and Apple Pay for AU transit users.

How Mobile myki works on Google Wallet:

You need Android 5.0 (Lollipop) or later with NFC. Open Google Wallet, tap the "Add to Wallet" button, and choose Mobile myki under the Passes section. You'll need an Australian Mastercard or Visa card for the initial purchase (around A$6) and ongoing top-ups; this is a Google requirement.

Once activated, your phone behaves as a complete myki card. Tap at any myki reader on Melbourne trains, trams, buses, or regional V/Line services to touch on and off. Fare capping, weekly caps, and zone-based fares all apply the same way as a physical myki.

Important constraints:

• Mobile myki can only be active on one device at a time. If you move to a new phone, you deactivate from the old one and activate on the new.
• Smartwatches (Wear OS) cannot run Mobile myki. It's a phone-only feature.
• You cannot transfer balance from an existing physical myki to a Mobile myki. They're separate cards with separate balances.
• The card must be re-purchased rather than copied across devices, so factory resets without prior deactivation can lose your balance.
• International (non-AU) cards work for top-ups but refunds require a visit to the PTV Hub at Southern Cross Station rather than online processing.

Setting Google Pay as default for Mobile myki:

Some Samsung devices have Samsung Wallet set as the default tap-and-pay app, which interferes with Mobile myki recognition at transit readers. The PTV recommends setting Google Pay as the default tap-and-pay app on Samsung phones (Settings → Apps → Default Apps → Tap & Pay) to ensure Mobile myki taps consistently.

This is the kind of detail that doesn't appear in global Google Wallet documentation but matters in practice for Australian users.

Other AU transit integrations

Google Wallet works on the other Australian transit systems through tokenised card payments rather than as a native transit pass.

Opal (NSW). Contactless card tap-on through Google Wallet works at all Opal readers. The transaction uses your tokenised card the same way Apple Pay does. There's currently no native Opal card in Google Wallet equivalent to Mobile myki, though Transport for NSW has signalled this could change with the Opal Next Gen upgrade targeted for 2027.

Adelaide Metro Tap and Pay. Contactless EMV through Google Wallet supported at validators on metro trains, trams and buses.

Brisbane (TransLink). Contactless rolled out across most modes in 2024, with Google Wallet support.

Perth (Transperth). Currently limited contactless card support; smart-ticketing system being developed.

For Sydney, Adelaide and Brisbane, the user experience with Google Wallet on transit is similar to Apple Pay. The Melbourne difference is the structural one: Mobile myki is a phone-native pass on Android only.

Other AU passes Google Wallet supports

Google Wallet's openness extends beyond payment cards to a wider range of passes than Apple Wallet currently supports for Australian users.

Boarding passes. Both Virgin Australia and Jetstar offer boarding passes that can be added to Google Wallet. Qantas also supports this. The pass shows your flight details, gate, seat, and a QR code for scanning at the airport.

Loyalty programs. Australia's largest loyalty programs integrate directly with Google Wallet: Everyday Rewards (Woolworths), Flybuys (Coles), and various smaller programs. Tap your phone at the loyalty terminal or present the pass to scan.

Student passes. Monash University was an early integration, allowing students to add their student ID to Google Wallet for campus services. Other universities have followed.

Event tickets. Ticketmaster, Eventbrite and similar platforms can add tickets to Google Wallet for major events. The pass replaces printed tickets.

Digital identification. Some Australian state governments are exploring digital ID integration with Google Wallet, though full rollout varies by state.

Apple Wallet supports many of the same categories, but the breadth and depth of Australian-specific integrations on Google Wallet has historically been larger, particularly for loyalty programs and student passes.

AU bank coverage

Universal across Australian retail banking. Confirmed Google Wallet supporters include:

Big Four banks. CommBank, Westpac, NAB, ANZ — all support adding debit and credit cards to Google Wallet. Coverage achieved earlier than for Apple Pay due to Google's open-architecture approach.

Major regional and digital banks. Macquarie, ING, Bendigo, Bank of Queensland, Suncorp, Heritage, Bankwest, HSBC Australia, Citi Australia, Bank Australia.

Credit unions and mutual banks. Great Southern Bank, Beyond Bank, P&N, Teachers Mutual, RACQ Bank, IMB.

Neobanks. Up, Volt (restructured), 86 400 (now NAB), Judo Bank, and various challengers.

Specialist institutions. Most insurance-linked card products, prepaid travel cards (Wise, Revolut), and business banking products from major banks.

eftpos support. Google added eftpos to Google Wallet earlier than Apple did, giving AU users with eftpos-only debit cards a path to mobile payments before Apple Pay supported the same.

If your AU debit or credit card can't be added to Google Wallet in 2026, it's almost certainly a niche specialist product or a very small issuer that hasn't yet implemented mobile wallet support.

Setting up Google Wallet

Three steps.

Step 1. Open Google Wallet (or your bank's app, which usually has an "Add to Google Wallet" button). Tap to add a card.

Step 2. Enter or scan your card details. The card details are sent to your card-issuing bank for verification.

Step 3. Your bank confirms the setup via SMS, in-app notification, or a quick call. The Device Account Number is generated, encrypted, and stored in your phone's secure hardware. The card is ready to use.

For Mobile myki, the same flow but you choose Mobile myki under Passes rather than a payment card. The Google Wallet app guides you through purchase and initial top-up.

You can add the same card to multiple devices (phone, tablet, Wear OS watch). Each device generates its own unique token.

Tokenisation security

The security model is essentially identical to Apple Pay's, with Android-specific implementation details:

Tokenisation. Your real card number is never on the device after initial setup and never shared with merchants. The Device Account Number is unique to each device.

Biometric authentication. Fingerprint sensor or face unlock on the phone confirms each transaction. PIN or pattern unlock as backup. A stolen Android device without biometric authentication can't make Google Wallet payments.

One-time cryptograms. Each transaction includes a transaction-specific cryptogram that can't be replayed.

Find My Device remote lock. If you lose your phone, you can remotely lock the device or wipe it through Find My Device, which suspends Google Wallet.

Privacy from Google. Google itself doesn't see what you bought or who you paid. Your card-issuing bank processes the transactions.

Privacy from merchants. Merchants see only the tokenised Device Account Number plus a transaction-specific cryptogram. They can't track you across visits using card details.

For most purposes, Google Wallet and Apple Pay offer equivalent security. The differences are at the operating system layer (how the secure hardware is implemented, how biometric data is stored) rather than at the wallet level.

Devices

Android phones running Android 5.0 (Lollipop) or later with NFC. This covers essentially every Android phone sold in Australia since 2015.

Wear OS smartwatches. Some Wear OS watches support Google Wallet for payments. Note that Wear OS watches do not support Mobile myki; that's phone-only.

Tablets. Tablets with NFC can run Google Wallet, but in-person payments are practically limited because tablets aren't designed for tap-and-go convenience. In-app and online payments work.

Wear OS Google Wallet support is broader than Apple Watch Apple Pay support in terms of supported card types but narrower in transit features.

Where Google Wallet is the best tool

Five scenarios where Google Wallet is the right choice.

Melbourne public transport on Android. Mobile myki is genuinely the best transit experience available in Melbourne for Android users. Your phone becomes a complete myki card with fare capping, zone discounts, and weekly caps applied automatically.

Any in-person tap-and-go transaction on Android. Faster and more secure than fumbling for a physical card.

Carrying multiple passes in one app. Boarding passes, loyalty cards, event tickets, and payment cards all in one wallet app. Reduces the need for multiple separate apps.

eftpos transactions. Google Wallet's earlier eftpos integration means Australian users with eftpos-only debit cards have had access to mobile payments slightly earlier than Apple Pay equivalents.

International travel with an Android phone. Google Wallet works at any contactless terminal globally that accepts your underlying card's network. Foreign exchange terms follow your card's terms.

Limitations

Android ecosystem only. Switching from Android to iPhone means switching from Google Wallet to Apple Pay. Loyalty cards and boarding passes need to be re-added to the new wallet.

Mobile myki has constraints. One device only, no Wear OS support, no balance transfer from physical myki, default tap-and-pay app must be set to Google Pay on Samsung phones.

No native Opal card. Sydney commuters tap with their tokenised credit/debit card via Google Wallet but don't have a native Opal card in the wallet equivalent to Mobile myki.

Card issuer must support Google Wallet. Universal for AU retail banks in 2026, but specialist or niche card products may not be supported.

Doesn't replace bank account features. Google Wallet tokenises your existing card. It doesn't give you bill payments, transfers, savings, or any of the broader financial services your bank account provides. For those, you still use your bank's app or one of the AU-native payment services covered in our Group B pages.

Some markets have limited Google Wallet availability. Travelling to a destination without Google Wallet support means falling back to your physical card.

How Google Wallet compares to alternatives

Against Apple Pay, the two are direct competitors limited by ecosystem. Apple Pay works only on Apple devices; Google Wallet works only on Android. AU bank coverage is equivalent. Mobile myki is the major differentiator: Android has it, iOS doesn't. Apple Pay's transit integration with Opal is more polished currently due to NSW's Express Mode rollout, while Google Wallet has stronger Melbourne myki support. Both are excellent within their respective platforms.

Against Samsung Pay, Google Wallet has a broader device footprint (any compatible Android phone, not just Samsung) and integrates with more AU-specific features. Samsung Pay works only on Samsung devices and has a more limited AU integration footprint, though some users prefer its Samsung-specific features.

Against PayID and Osko, the comparison is structural and complementary. Google Wallet is for tap-and-go merchant payments using your existing card. PayID and Osko are for person-to-person and arbitrary bank-to-bank transfers. Most Australians use Google Wallet and PayID together for different transaction types.

Against a physical contactless card, Google Wallet wins on security (tokenisation, biometric authentication, remote lock) and on the additional pass storage (loyalty, transit, boarding passes).

For a method-by-method comparison, see our e-wallet fees and speed comparison.