Google Wallet — the digital wallet built into most Android phones — can store loyalty cards alongside payment cards, boarding passes, and event tickets. For small businesses, this is significant because it means your loyalty programme can live on your customers' phones without requiring them to download a dedicated app. But the way Google Wallet loyalty works is quite different from what most business owners expect.
This guide covers how Google Wallet loyalty passes actually work, how you can issue them, what the limitations are, and how the experience compares to Apple Wallet and standalone loyalty apps. It's aimed at business owners who want practical answers, not a technical deep-dive.
How Google Wallet loyalty passes work
A Google Wallet loyalty pass is a digital card that gets added to a customer's Google Wallet. It can display a barcode or QR code for scanning, show the customer's loyalty balance or stamp count, and include your branding — your logo, business name, and colour scheme. When the customer opens Google Wallet on their phone, your loyalty card sits right alongside their payment cards.
Unlike a standalone app, Google Wallet passes don't require any download or installation. The customer taps an "Add to Google Wallet" button — on your website, in an email, or from a QR code — and the pass is saved instantly. There's no account creation, no onboarding flow, no permissions to grant. This low friction is the biggest advantage of the wallet-based approach.
Note
Google Wallet passes are available on Android devices running Android 6.0 or later with Google Play Services. This covers the vast majority of Android phones in the UK — roughly 95% of the Android install base.
How businesses issue passes
You can't create Google Wallet passes directly through a consumer interface. As a business, you need to use the Google Wallet API, which requires a Google Cloud project and developer credentials. In practice, most small businesses don't do this themselves — they use a loyalty platform or pass management service that handles the technical integration for them.
The typical flow works like this: a customer taps an NFC tag, scans a QR code, or clicks a link. Your loyalty platform generates a pass using the Google Wallet API and presents the "Add to Google Wallet" button. The customer taps it, and the pass appears in their wallet within seconds. From that point on, the platform can update the pass remotely — adding stamps, changing the reward balance, or sending notifications.
What Google Wallet passes can and cannot do
- Can display your logo, brand colours, and business name
- Can show a loyalty balance, stamp count, or tier status
- Can include a barcode or QR code for scanning at point of sale
- Can be updated remotely by your platform (new stamps, rewards earned)
- Can send lock-screen notifications when the pass is updated
- Cannot run custom code or logic on the device
- Cannot collect customer data beyond what Google provides at pass creation
- Cannot trigger location-based notifications reliably (unlike Apple Wallet)
- Cannot support complex multi-step interactions — it's a card, not an app
Tip
Think of a Google Wallet pass as a smart business card that can update itself. It's excellent for simple loyalty mechanics (stamp cards, point balances), but if you need complex features like ordering, messaging, or detailed analytics, you'll need a companion web experience or app.
Google Wallet vs Apple Wallet
Both Google Wallet and Apple Wallet support loyalty passes, but there are meaningful differences. Apple Wallet passes use the PKPass format and have been available since iOS 6 in 2012 — they're mature and well-understood. Apple also supports location-based notifications, showing your pass on the lock screen when a customer is near your shop. Google Wallet's location triggering is less reliable in practice.
The update mechanisms differ too. Apple Wallet uses push notifications tied to each individual pass, while Google Wallet updates passes through the Google Wallet API. Both allow remote updates, but the developer experience and reliability vary. In the UK market, the iPhone-to-Android split is roughly 52-48, so ideally you want a solution that supports both wallets.
Google Wallet vs a standalone loyalty app
The big trade-off is between reach and capability. A Google Wallet pass reaches more customers because there's no download barrier. A standalone app can do more — push notifications, in-app ordering, detailed profiles, gamification. But an app that nobody downloads is worthless regardless of its features.
Key Stat
The average consumer has 80 apps installed but only uses 9 daily. Asking a customer to install your loyalty app means competing with every other app on their phone for attention — and most small business apps lose that fight within a week.
For most small businesses, the wallet-based approach wins because it prioritises adoption over features. A pass that 50% of your customers use will always outperform an app that 8% of them download and 3% actively use. The smartest approach is often a hybrid: issue a wallet pass for the basic loyalty mechanic, and offer a web-based experience for customers who want more.
Getting started with Google Wallet loyalty
If you're considering Google Wallet passes for your business, the path of least resistance is to choose a loyalty platform that handles the technical integration. Look for platforms that support both Google Wallet and Apple Wallet, so you're not leaving half your customers behind. Ask whether pass updates happen in real time or with a delay — some platforms batch updates, which means customers don't see their new stamp immediately.
The technology behind Google Wallet loyalty is genuinely good, and it solves the biggest problem in small business loyalty: getting customers to actually carry and use the card. A loyalty pass that lives on the phone they already check 150 times a day is inherently more effective than a paper card buried in a wallet. The key is choosing a platform that implements it well and keeps the experience seamless for both you and your customers.