How to create a Google Wallet loyalty card for your shop: the merchant guide (2026)

To create a Google Wallet loyalty card, you have two routes: build against Google's Wallet API yourself (free, but a real development project), or use a loyalty platform that generates the card for you (from about €9/month, live the same day). Either way, your customers end up with the same thing: your loyalty card in the Google Wallet app, saved in one tap, with no app of yours to install.

Half the phones walking past your counter run Android, and nearly all of them ship with Google Wallet already installed. That preinstalled app is the whole opportunity: your loyalty card can live where their bank cards and boarding passes already do, instead of on a paper card drying out in a coat pocket.

We make Stampo, a loyalty card platform that uses Google Wallet (and Apple Wallet) under the hood, so the platform route below includes us and we're biased about it. The DIY route is covered honestly too, because for some businesses it's genuinely the right call, and we'll say which.

Key Takeaways

Customers save a Google Wallet loyalty card in one tap from a link or QR scan; there is no app to download and no account to create beyond an email.

Merchants have two routes: DIY against the free Google Wallet API (weeks of developer time) or a platform from ~€9/month (same-day launch).

Google Wallet cards update in real time: stamp at the counter, and the card in the customer's pocket already shows the new count.

Google Wallet covers Android; a complete program pairs it with Apple Wallet for iPhone customers. Good platforms do both from one dashboard.

Skip the DIY route unless you have in-house developers and an unusual, specific need a platform can't meet.

What a Google Wallet loyalty card actually is

A Google Wallet loyalty card is a digital pass in the customer's Google Wallet app showing your shop's branding, their stamp or point balance, and a barcode or QR code you scan at the counter. When the balance changes, the card updates itself; the customer does nothing.

From the customer's side, the whole lifecycle is three moments. They scan your QR code or tap a link, hit "Add to Google Wallet," and they're enrolled. On each visit, they open the wallet (or just tap the card notification) and show their code. When their reward is earned, the card says so.

From your side, the card is a window into your loyalty system. You never "send" cards; you publish one card design, and every customer's copy stays synchronized with their own balance. That live-update behavior is what separates wallet passes from a PDF or a loyalty app, and it's native to how Google's Wallet platform works.

One scope note before the how-to: Google Wallet reaches Android. iPhones use Apple Wallet, a separate system with a different format. We've compared the two in detail in Apple Wallet vs Google Wallet for loyalty programs; the practical takeaway is that a complete loyalty program speaks both, and any platform worth paying for handles both from one dashboard.

Route one: build it yourself on the Wallet API

Google's Wallet API is free to use, well documented, and genuinely open to any business. Here's what the project actually involves, minus dev-speak, so you can judge whether it belongs on your plate:

Register as an issuer with Google Pay & Wallet Console and get your business approved.
Define the loyalty card class: your branding, fields, and barcode format.
Build the enrollment flow: a signup page that creates a unique card for each customer and produces the "Add to Google Wallet" link.
Build the update mechanism: every stamp needs your system to push the new balance to Google so the customer's card refreshes.
Build the counter side: something that scans the customer's code and records the stamp, with protection against double-scans.
Maintain all of it, forever, including the iPhone half of your customer base, which means doing the whole project a second time against Apple's system.

For a developer, none of this is exotic. It's simply a few weeks of skilled work plus permanent upkeep, to reproduce what platforms sell for the price of two coffees a month.

The DIY route is right for you if: you have in-house engineering, unusual requirements (custom CRM integration, thousands of locations, regulatory constraints), or loyalty is core product territory for your company. A national chain should probably own this. A bakery should not.

Route two: use a platform

A loyalty platform has already built everything above and rents it out. You configure your card in a dashboard; the platform generates the Google Wallet card, the enrollment page, the QR codes, and the scanner.

What the setup actually looks like (Stampo's flow, typical of the category):

Sign up with your email and business name.
Design the card: brand color, logo, stamp icon, template. A live preview shows the exact card your customers will save.
Set the reward: "Buy 9, get the 10th free," or whatever your counter math supports.
Print the kit: a generated poster, sticker, and table stand carrying your QR code.

From zero to a scannable counter is around ten minutes, and the Android experience is particularly clean: a customer who scans your code on an Android phone is taken straight into Google Wallet's save flow, one tap, done. iPhone customers get the Apple Wallet version of the same card from the same QR code; the platform detects the phone and routes accordingly. The step-by-step is on how Stampo works, and the Apple half of the story has its own guide in how to add a loyalty card to Apple Wallet.

Platform pricing for small shops runs from free tiers (BonusQR) through €9/month or €199 lifetime (Stampo) to $25–49/month (Loopy Loyalty, Stamp Me), verified July 2026.

What makes Google Wallet loyalty work at the counter

Three practical behaviors matter more than any feature list.

The save flow is one tap. No form beyond an email, no password, no app. Every additional step in enrollment costs you a measurable share of joiners; Google Wallet's native save flow is about as short as enrollment can physically get.

Updates arrive by themselves. When you stamp a card, the platform patches the customer's pass and Google refreshes it on their phone. Your regular walks out, and the card in their pocket already reads "7 of 10." No sync button, no "pull to refresh," no stale balances to argue about at the counter.

Messages can reach the card. Google Wallet supports notifications tied to the pass, which is how a "we haven't seen you in a while, your card misses you" nudge lands without you running an SMS platform or an email tool. Quieter than push spam, cheaper than SMS, and it goes exactly to people who already chose to carry your card.

When a Google Wallet loyalty card isn't the answer

Your customers skew heavily iPhone. Google Wallet alone covers the Android half. This isn't a reason to skip wallet loyalty; it's a reason to insist on a tool that does both wallets from one card design. Ask any provider "what happens when an iPhone scans this code?" before paying.
Your regulars don't use smartphones. Some counters serve a clientele where paper still wins. Run paper for them; a hybrid counter is fine.
You need loyalty inside your POS reporting. If you live in Square's or Toast's dashboards and want loyalty in the same place, a standalone wallet card is a second system. It's cheaper and portable, but it is a second login.
You wanted a customer app. Some brands specifically want their own icon on the customer's home screen. That's a different (and much more expensive) product category, and honestly, for an independent shop, one we'd talk you out of: the app your customer already has is the wallet.

FAQ

How do customers add my loyalty card to Google Wallet? They scan your QR code or tap your signup link, enter an email, and tap "Add to Google Wallet." The card appears in their wallet app immediately. No app download, no password.

Does it cost money to issue Google Wallet loyalty cards? Google's API itself is free. The real costs are either developer time (DIY route) or a platform subscription, from roughly €9/month for a small shop (July 2026 pricing).

Do Google Wallet loyalty cards update automatically? Yes. When the merchant stamps the card, the platform pushes the new balance and Google refreshes the pass on the customer's phone in near real time.

Can one loyalty card work in both Google Wallet and Apple Wallet? One program can, and should. The same QR code detects the phone: Android goes to Google Wallet, iPhone to Apple Wallet. The customer sees one shop card either way; the platform maintains both formats behind the scenes.

Can I send messages to customers through Google Wallet? Yes, notifications can be attached to the loyalty pass, which is how re-engagement nudges reach customers without SMS costs or a separate email list. Platforms cap send volumes to keep the channel from becoming spam.

Do I need special hardware to scan Google Wallet loyalty cards? No. The customer's card displays a QR code, and any phone or tablet camera at your counter reads it through the platform's scanner page.

The bottom line

Google Wallet turned loyalty cards into something Android phones simply already do. The only real decision left for a shop owner is who maintains the plumbing: your developers (justifiable for chains and product companies) or a platform's (the sane answer for everyone else).

If you want the platform route, Stampo issues Google Wallet and Apple Wallet cards from one ten-minute setup, at €9/month, €90/year, or €199 once, with a 14-day trial and no credit card up front: see how it works and what it costs. Either way, your next loyal customer's card belongs in their wallet, not under your till.

Pricing verified 27 July 2026.