Google Wallet loyalty card: how it works on Android (2026)

A note on who is writing: Stampioo issues loyalty cards for Google Wallet and Apple Wallet, so we have an interest in you choosing a Wallet card over a paper one or an app. Everything below about how Google Wallet behaves comes from Google’s help pages and developer documentation, read on 3 November 2026. Where Google does not document something we say so rather than guess, and where the behaviour is Stampioo’s choice rather than Google’s, the text says which.

What customers call a digital stamp card or punch card on Android is a loyalty card pass in Google Wallet, and that is what we mean by a loyalty card in Apple Wallet and Google Wallet. For the whole journey on both platforms start with our overview of stamp cards in Apple Wallet and Google Wallet; the iPhone side has its own Apple Wallet setup guide. This page is about Android, where the rules are different in ways that catch businesses out.

The one requirement: a Google account

On an iPhone a pass is added with a tap and no sign-in. On Android it is different. Google’s developer documentation for loyalty cards says that adding a pass can only be initiated in the context of a logged-in Google identity. In plain terms: the customer must be signed in to a Google account on the phone for the Add to Google Wallet button to do anything. Nearly every Android phone sold with Google services is set up that way on day one, so most customers never notice. The ones who do notice are the ones with a work phone, a second-hand phone that was never signed in, or a phone without Google services at all.

The second requirement is the Android version. Google’s help page says that since 10 June 2024, Google Wallet requires Android 9 or higher on the phone, because security updates are not available for Android versions below 9. Android 9 was released in 2018, so this excludes only genuinely old devices, but a café with an older crowd will meet a few.

How the customer saves the card

The flow below is Stampioo’s; other Wallet-based tools work the same way. Google’s part starts at step 3, which its documentation describes as an Add to Google Wallet button or link that opens a signed save page.

1. 1

   Scan the QR code

   With the camera app or the phone’s QR reader. The code sits on your counter sign, the menu or the receipt. A link appears; the customer taps it.

2. 2

   Fill in the short form

   Name and whatever you have chosen to ask for, such as email or birthday, then accept the terms. The form opens in the browser, not in an app.

3. 3

   Tap Add to Google Wallet

   If the phone is signed in to a Google account, Google Wallet opens with the card preview. If not, Google asks the customer to sign in first; this is the step where a few customers give up.

4. 4

   Tap Save

   The card is now in Google Wallet and linked to the Google account. As on iPhone, closing the preview without tapping Save leaves the customer without a card.

Pass types: what a stamp card is in Google’s system

Google’s developer catalogue lists the pass types it offers: in retail, Loyalty Cards, Gift Cards and Offers; then boarding passes, event tickets and transit passes; access passes such as corporate badges and hotel keys; and a Generic Pass for anything else. A digital stamp card is normally built as a Loyalty Card pass, which gives it a programme name, a points or balance field (used for stamps), a barcode and a hero image. Some tools use the Generic Pass instead, which looks similar but is treated differently for notifications. Which type your tool uses is rarely stated on its website; it matters mainly for the notification rules below.

Notifications: what Google allows and what it does not

This is where Google Wallet differs most from Apple Wallet, and the documentation is precise about it.

• Messages: the issuer can add a message to the pass that sends a push notification to everyone who has the pass saved. Google allows a maximum of 3 such messages in a 24-hour period.
• Field updates: a change to certain fields, including the loyalty points balance (which is where a stamp count lives), can trigger a notification. Again, a maximum of 3 updates that trigger a push per 24 hours.
• The customer must have notifications enabled for their passes, or nothing arrives. The card still updates silently.
• Google controls the look of the push notification the customer sees on the lock screen; the issuer does not design it.

For a business this means one planned campaign a day, not a burst, and it means a customer who collects four stamps in a day will not get four notifications. With Stampioo, targeted push campaigns are on Pro (10 a month) and Enterprise; stamp updates are on every plan. How the notifications look on each phone, and what gets through, is covered in our guide to Wallet push notifications for loyalty cards.

Nearby reminders on Android

A loyalty pass can carry up to 10 locations, and Google Wallet can show a notification when the customer is near one. Google is clear about the limits. The customer must have notifications enabled and must have granted Google Wallet precise, always-on location access. Google decides how close the customer needs to be and how long they need to stay before the notification appears, and Google writes the text; the issuer only supplies the locations. The customer can dismiss it with a swipe and it disappears when they leave. On iPhone the issuer writes a line of text per location; on Android it does not. If nearby reminders matter to you, expect them to reach a smaller share of Android customers than iPhone customers, because the always-on location permission is one many people decline.

A new phone

Here Android is friendlier than iPhone. Google’s page on transferring passes lists loyalty and gift cards, event tickets and boarding passes as passes that automatically appear when the customer signs in to Google Wallet on a new device with the same account, and says they can be stored on multiple devices at the same time. Payment cards, transit passes, IDs and keys do not transfer that way and need a device-to-device transfer, a cloud restore or a manual re-add. Google’s page on managing items adds the mirror image: remove a pass connected to the Google account on one device and it is removed across all devices, while some passes are device-specific and not connected to the account.

So a customer who upgrades their Android phone and signs in with the same Google account should find your card waiting. If they sign in with a different account, or the pass was device-specific, they scan your QR code again, and with Stampioo your staff add the stamps back by hand from the dashboard.

Phones without Google services

Some phones cannot save the card at all: Huawei models sold without Google Mobile Services, phones running Android below 9, and phones where the owner has removed Google services on purpose. There is no workaround inside Google Wallet, and scanning the QR code again does not help. Say so plainly to the customer and offer a fallback. With Stampioo the fallback is a printed card from the free loyalty card maker; some other tools offer a card that opens in the browser, which works on any phone but has no lock-screen reminders and must be found again each visit.

If you serve many customers in this group, the no-app loyalty programmes comparison explains the difference between a Wallet pass and a browser card.

The Android friction people report

Search any comparison and you will find the line “Android users struggle to add the card”. Its source is a handful of Capterra reviews of Loopy Loyalty, read via search listings, which we have not reproduced and report only as what reviewers wrote. From our own support, the Android problems with any tool fall into four groups, none of them specific to one vendor: the customer skipped the final Save tap; the phone is not signed in to a Google account, so the Add button leads to a sign-in screen; the phone runs Android older than 9; or the phone has no Google services. A sign at the till that shows the two taps, and staff who know the sign-in step exists, remove most of it.

Five tools with Google Wallet loyalty cards

All five issue a real loyalty pass in Google Wallet with no app from the business. Prices are as each vendor shows them, checked 3 November 2026, with no conversion. Two tools people ask about are missing on purpose: Square Loyalty offers an Apple Wallet pass only, and Stamp Me lets only the member-code barcode into Wallet while the stamps stay in the Stamp Me account.

For a ten-tool comparison with the Android column filled in for each, see Loopy Loyalty alternatives. Stampioo includes the Google Wallet card on every plan from €29 a month excluding VAT; plans and pricing shows what each plan adds.

Checklist for an Android-heavy customer base

• Test the sign-up on an Android phone that is signed in and one that is not, so staff recognise the sign-in screen.
• Put the two taps on the counter sign: Add to Google Wallet, then Save.
• Keep a few printed cards for phones that cannot run Google Wallet.
• Plan one campaign a day at most; Google will not deliver more than three with a notification.
• Do not promise nearby reminders to Android customers; they only work for those who allow always-on location.