For decades, loyalty in a physical shop meant a paper card and an ink stamp. It worked until the customer lost it, soaked it in a coat pocket or forgot to bring it. A digital loyalty card solves that without asking anyone to change their habits: it uses the wallet they already carry.
What it actually is
It is the digital version of your stamp or points card. Instead of card stock, it lives inside Apple Wallet on iPhone or Google Wallet on Android, the same apps people keep boarding passes and event tickets in. Every time the customer buys, the card updates itself: one more stamp, the points balance current, the reward when it is due.
Paper, own app, or wallet
An own-brand app looks like the complete option and runs into a wall: most people will not install the app of a coffee shop. A wallet card avoids that wall because there is nothing to install. It is the balance between capability and zero friction.
How the customer adds it, in three steps
- They scan the QR code in the shop, or open a link. The card opens in the browser.
- They tap "Add to Apple Wallet" or "Save to Google Wallet". No app is downloaded.
- Done. The card sits in their wallet and updates itself on every visit.
On your side, adding a stamp is just as simple: a member of staff scans the customer code from a phone or the till, and the card reflects it immediately.
What makes the proximity alert different
This is the part most often misunderstood, so it is worth being precise. The lock screen alert is not a push notification. The business does not send it, cannot schedule it and cannot write it. The phone's own operating system builds it when the customer walks within roughly a hundred metres of a location stored inside the card.
- It cannot be abused. There is no way to fire twenty of them. The phone shows it when the customer is nearby, and that is all. It irritates far less than a notification.
- It depends on your shop coordinates being set. This is the most common failure: a business is created without latitude and longitude, so the alert simply never exists and nothing reports an error.
- Android and iPhone find out differently. Google propagates a location change to installed cards almost on its own. On iPhone the data travels inside the pass file, so a change does not arrive until an update is pushed to the device. If you move premises and only Android customers notice, this is why.
What a wallet card does not do
- You cannot be certain an Android user saved it. Apple confirms it when the iPhone registers the pass. On Google the signal is indirect, so Android install figures are an approximation.
- It does not replace email. The text that fits on a pass is short and the customer only sees it if they open their wallet.
- It does not read the card payment or the receipt. Unless you connect it to your till system, a person scanning a code is what adds the stamp. If your business rings almost everything through a fast till, that integration stops being a luxury.
- It is useless without identifying the customer. An anonymous card does nothing: the whole point is recognising them next time.
What to ask a provider
- What happens when I change the card design? The good answer is that it updates on phones that already have it. If customers have to add it again, that part is not solved.
- How does an iPhone find out about a change? If the answer does not mention pushing an update to the device, the provider has probably only implemented the Google side.
- What happens if I push a change to a thousand customers at once? A serious system does it in batches. Waking a thousand phones together makes all of them request their pass at the same moment.
- Can I export my data? Your customers are yours. With no export, you are renting your own list.
- What language does the customer see it in? If you serve visitors, it matters that the card speaks their language and not yours.
How long it takes to set up
The card itself takes minutes: name, colours, logo, how many stamps and what the reward is. What takes time is everything around it, and that is where success is decided: the QR placed where the customer is already waiting, the sentence used to offer it ("the tenth coffee is free, shall I put it on your phone?" captures twice as much as "do you have our card?"), the staff actually offering it, and the automated messages that bring back anyone going quiet.
What if the customer wants more than the card
Some customers, usually your best ones, want to see their history, their rewards and what they can redeem. That is worth offering, and it is worth offering as an addition rather than a requirement.
A web profile they reach from the card itself covers almost all of it with nothing to install. An app has its place for the most engaged, but the moment it becomes the way in, you are back to the wall that made paper cards fail: most people will not install it, and the ones who will were already loyal.
The promise underneath has to survive whatever you add on top: nothing to download to get started.
Digitising your stamp card, in practice
If you already run a paper card, the migration is the part people get wrong. Three things matter.
- Honour the stamps they already have. Asking a regular to start again is the fastest way to lose the exact people the programme exists for. Carry the balance over, even approximately, and say so.
- Run both for a few weeks. Not everyone will switch on day one, and refusing the paper card at the counter creates an argument nobody wins.
- Pick a date to stop printing. Running both forever means running neither well, and your staff will default to whichever is easier to explain.
One thing worth doing on the way across: this is your only free chance to change the number of stamps or the reward. Changing it later reads as moving the goalposts; changing it during a migration reads as a new programme.

