Feature

Google Wallet loyalty cards

Roughly the same argument as Apple Wallet, aimed at the other half of your queue. Android customers scan the same QR code and get a card in the wallet app their phone already has.

One QR for both platforms

You print one code. The enrollment page works out which wallet the phone in front of it uses.

No second system to run

Your staff scanner, your analytics and your customer list do not care which wallet a card lives in.

Different platform, honest preview

Google Wallet lays passes out differently from Apple. The card designer shows you each, labelled, rather than one idealised mock-up.

Web fallback included

Older phones and locked-down devices get a web card carrying the same code, so nobody is turned away at the counter.

Brew House
Coffee Club
7 / 10
3 more → Free coffee
Shaheer#48291

Why both wallets, not one

A café queue is not an iPhone queue or an Android queue, it is both, usually in a ratio you cannot control. Supporting only one platform means half your regulars get a worse experience and your staff have to remember which is which. Supporting both means the barista never asks what phone anyone has.

What the customer actually does

Scan the code on the counter. Type a first name. Tap Add to Google Wallet. That is the entire onboarding, and it happens while their drink is being made.

Common questions

What if a customer’s phone cannot add a wallet pass?
They get a web card instead — a page showing the same card and the same scannable code. Your staff scan it exactly the same way.
Do I need separate QR codes for Apple and Android?
No. One enrollment code serves both.

Keep reading

Put your loyalty card in your customers’ pockets

Publish a branded card in about five minutes. 14-day free trial, no card required.