Lorixen.
EN

Loyalty Card in Apple Wallet and Google Wallet: Pass First, App Later?

Short answer: Start with the card in the customer's phone wallet, and let six months of real use tell you whether an app is worth building. A wallet card costs the customer one tap to add and needs no store listing from you, so it tests the idea cheaply. An app becomes the right next step only when customers ask for things a card cannot hold, such as ordering ahead, booking or a purchase history. Below is a trial plan with checkpoints so the decision rests on what your own till reports.

Why the card wins the first round

Ask what a loyalty scheme needs to do on day one: identify the member at the counter, record a visit, and show the reward in sight. Nothing in that list needs a download. A card in Apple Wallet or Google Wallet already sits on the phone, opens from the lock screen and displays a code that your scanner can read.

The friction gap is the real argument. Installing an app means a search, a download, a sign-up form and a notification question. Adding a card means scanning one square code on your counter sign. In a queue of people holding coffees, only one of those happens.

Each wallet works differently behind the scenes. Apple's cards are signed files issued under a developer account. Google's cards are created through an API, where you define a card design once and then issue one record per member. The official documentation for both is listed in this article's sources, and as of November 2026 you should read the current requirements there before agreeing a budget with anyone. A member on iPhone and a member on Android get different files, so your system must link both to one customer record.

Months 1 and 2: a minimal scheme

Keep the first rule so plain that a new employee can explain it in ten seconds. "Buy nine, the tenth is on us" is plain. A system with tiers and category multipliers is not.

Things to settle before launch:

  • Where the member ID lives. One short number per person, printed under the code so staff can type it if scanning fails.
  • Who adds the stamp. The cashier, on the same device that rings up the sale, or a separate tablet by the till.
  • What happens to someone without a smartphone wallet. A paper card or a phone-number lookup, tied to the same record.
  • What you ask at sign-up. A first name and a mobile number or email is enough. Everything extra is a liability.

Put the QR code on the counter, on receipts and on a small table card. Train staff to say one sentence when handing over a drink: "Want your card on your phone? Scan this."

Illustrative scenario: a fictional bakery in Halifax puts one square code beside its card reader. Within a minute, a customer has the card, and the cashier scans it on the next visit. The owner reads the weekly report on Monday morning, and nothing else is needed.

Month 3: read the numbers

Four figures decide most of what comes next:

  1. How many cards were added
  2. How many members came back a second time
  3. How many stamps were redeemed
  4. How many people asked staff for something the card could not do

The fourth is the most valuable and the one most owners forget to record. Give staff a notebook or a shared note and ask them to jot down every request, such as "Can I order ahead?" or "Can I see my last order?". Tally them after eight weeks.

Months 4 to 6: decide with evidence

What you see What it suggests
Members return and redeem, few extra requests The card is enough, keep improving it
Many requests to order or book ahead A web ordering page may serve you faster than an app
Requests for history, saved favourites and account details An app, or a members' web area, starts to pay for itself
Low sign-up despite staff effort The offer or the counter prompt is weak, not the format
Many members on one platform only Check the other platform's card is working properly

Notice the second row. A website with ordering often answers the demand sooner and for less than an app does, so test that before you commit to store submissions.

If an app does come, keep the wallet card. New customers still prefer a tap over an install, and the card can sit alongside the app as the quick way to join.

What a card can and cannot carry

It can hold a logo, a name, a member number, a points or stamp figure, a short message and a scannable code. Its content can be updated from your server after the customer has added it, and on both platforms it can be surfaced at relevant moments, with the rules set by Apple and Google.

It cannot hold a menu, take a payment, run custom logic on the phone or act as an account area. If your reward rules need a long explanation, the card is the wrong place for them. Link to a short web page from the back of the card instead.

Staff and counter checklist

  • [ ] Test scanning a real card on an iPhone and an Android phone at the till
  • [ ] Try it with a dim screen, in bright shop light and with a cracked screen protector
  • [ ] Print the member number under every code
  • [ ] Write a three-line script for staff, covering how to add, how to scan, how to redeem
  • [ ] Decide what to do when a customer changes phone
  • [ ] Decide how a lost or shared card is handled
  • [ ] Agree who can issue a manual stamp, and keep a record of it

Privacy and honesty

A card ties a name or number to buying habits, so treat it as personal data. Collect the minimum, say plainly what you do with it, and let people leave the scheme and have their record removed. Rules differ by country and province, so check your national privacy regulator's guidance for retail businesses rather than assuming. Avoid sending frequent promotional messages through card updates, because customers can delete a card in one swipe and you lose the link altogether.

Costs without invented numbers

We will not quote prices here, because fees for developer accounts and any third-party pass service are set by those providers and change. What stays constant is the shape: an Apple account for signing, a Google issuer setup, some hosting for your member records, and time for someone to maintain it. Compare that with an app's ongoing items, which include store listings, review rounds, updates for new phone versions and support.

FAQ

Do customers need to install anything?

No. The wallet application is already on their phone. They only add your card.

Can a single card file serve both iPhone and Android?

No. Each platform has its own format. Offer two buttons on the sign-up page and link both to one member.

What if a member never opens the card?

Cards cost you nothing when idle. Look at who has not been scanned in ninety days and consider a gentle prompt at the till rather than a message.

Can we move members to an app later?

Yes, as long as the member ID is yours and stored on your own system. That is why the record should never live only inside a third party's tool.

If you would like to try a wallet card before deciding on an app, tell us what your till and customer list look like and we will map out the first two months.

Sources

WhatsAppBook a call