A loyalty card that does not live in Apple Wallet
Apple Wallet and Google Wallet passes look like the modern way to replace a paper stamp card. They are a real method, with real strengths. They are also a worse fit for most counters than a camera pointed at a QR code, and the reasons are practical rather than ideological.
Start your free trial →The camera is already on every phone
A wallet pass has to be added before it can be used. That is an install by another name — tap, confirm, wait for the pass to land, then find it again next visit. The camera is already unlocked in the customer's hand, so the first stamp happens before they have decided whether they "want a loyalty card".
Old phones and mixed pockets still work
Wallet passes need a recent enough iPhone or Android and a working Wallet app. Plenty of regulars still carry a five-year-old handset, a hand-me-down, or a phone whose Wallet was never set up. A web page opened from the camera does not care which of those it is.
You do not become a pass issuer
Shipping a pass means certificates, an Apple or Google issuer account, expiry dates, and a payload that has to be signed every time the stamp count changes. A QR on a screen you already own has none of that. The trade is that you also do not get a lock-screen pass or Wallet push.
Two ways to put a card on a phone
Both methods get the paper card off the counter. They do it in opposite orders.
A wallet pass is an object that has to be issued, signed and added. The customer agrees to put something into Apple Wallet or Google Wallet, the pass appears in that stack, and later visits update it. The payoff is a native artifact next to the boarding passes. The cost is paid up front, at the till, before the first stamp has any value.
A camera QR card reverses that. The customer points the camera they already have at a code on your screen. A web page opens with the stamp already on it. Nothing is added to Wallet. Nothing is installed. The card is remembered on that phone, so the next visit is another single scan.
The rest of this page is about which of those costs you actually want to pay.
What a wallet pass is good at
Worth saying plainly, because the comparison is dishonest if it is not:
- It lives in a place people already look. Once added, a pass sits in Apple Wallet or Google Wallet with the tickets and cards. Some customers like that more than a page in the browser.
- It can update on the lock screen. A pass can show a new stamp count without the customer opening anything. A web page cannot do that.
- It feels official. For a minority of customers, “added to Wallet” reads as more finished than a URL.
Those are real. They are also benefits that only exist after the pass has been added, which is the step that most people standing in a queue will skip.
What you take on as the shop
Issuing passes is not a toggle. You become a pass issuer:
- An Apple Developer or Google Wallet issuer account.
- Certificates that expire and have to be rotated.
- A signed payload every time the stamp count changes.
- A fallback for the phones that cannot add a pass at all.
None of that is visible on a marketing screenshot of a pretty pass. It is visible the first time a certificate lapses on a Saturday or a regular’s phone is too old to install one.
A QR code on a screen you already own has none of this. The kiosk is a web page. The card is a web page. The only moving part is a code that dies after thirty seconds and is replaced by a new one.
The honest trade-offs
| Camera QR | Wallet pass | |
|---|---|---|
| First stamp | Camera, already in their hand | Add to Wallet, then find it |
| Old phones | Works if it has a browser | Needs a current Wallet |
| Lock-screen updates | No | Yes, once added |
| Certificates | None | Required, and they expire |
| Push into Wallet | No | Yes |
| Works across iPhone and Android | Same page on both | Two pass formats |
The row that decides it for most local shops is the first one. The first stamp has to happen in the ten seconds someone is paying, holding a coffee, with a queue behind them. A method that adds a step there loses people you never see again. A method that uses the camera they already opened does not.
Who should still use a wallet pass
If you already issue passes for tickets or memberships, and your customers already have you in Wallet, putting stamps on that pass is reasonable — the add-to-wallet cost was paid for something else. If loyalty is the reason you would become a pass issuer, skip it. Put a screen by the till, let the camera do the work, and keep the certificates off your weekend.
The questions everyone asks
Is this the same as saying Wallet passes do not work?
No. A pass in Apple Wallet or Google Wallet is convenient once it is there — it sits with the boarding passes, it can update on the lock screen, and some people prefer that. The question is how many of your customers will complete the add-to-wallet step at a busy till, and whether you want to run the certificate machinery for that fraction.
What do I give up by not using a wallet pass?
Two things worth stating. You cannot push an update onto the lock screen the way a pass can, and the card is a web page rather than a native Wallet object, so it will not appear in the Wallet stack. In exchange you skip certificates, issuer accounts and the "add this pass" prompt that loses people at the counter.
Does the customer still have something on their phone?
Yes. The stamp card is a web page remembered on that phone for a year, opened again by the next scan. Anyone who wants it to survive a new phone can link a Google, Facebook or email account from their own screen. That step is optional and happens after they have already earned stamps.
Can I offer both a pass and a QR card?
You can in theory, and you then maintain two ways to be out of date. For a single counter the simpler version wins — one screen, one code, one place the count lives. If a customer specifically wants a Wallet pass, that is a different product with a different cost of ownership.
$19/month · 7-day free trial
Unlimited stamps · Unlimited customers · No per-scan fees
Start your free trial →