Lorixen.
EN

Apple Wallet and Google Wallet Passes for Loyalty Cards and Tickets

Short answer: A wallet pass is a digital card stored in Apple Wallet or Google Wallet. It shows a barcode or QR code, can carry a stamp count or a balance, and can be updated by push when something changes. It is the better choice than a full app when customers need a loyalty card or a ticket they show at the counter and do not want to download anything else. A pass cannot run complex logic, show rich menus or hold large amounts of content, so it suits simple, repeat actions. Plan the design within the platform limits, then choose between a pass service and a custom build based on how many passes you issue and how often you change them.

When a pass is the right tool

Think about what the customer does with the card. A coffee loyalty card is scanned, a stamp is added and the card is shown again. A concert ticket is scanned once at the door. A gift voucher is redeemed against a total. Each of these needs one barcode, a few fields and a way to update the balance. A pass does all of that without an app, and it sits on the lock screen when the customer needs it.

A full app earns its place when customers must browse, book, pay or receive detailed content. If the main job is "show a code and collect a stamp", the pass is usually enough.

How passes work

Both wallets use a pass file that holds the design, the fields and the barcode. The business creates the pass with a standard structure and signs it, so the wallet can trust where it came from. Customers add the pass from an email, a web page or a QR code. Once installed, the pass can be updated, and the wallet refreshes it through a push message or on the next sync.

Two details matter for planning:

  • Pass types. Each wallet offers a set of categories, such as loyalty, event tickets, coupons or boarding passes. Choose the closest category, because the layout and the available fields depend on it.
  • Updates. Passes can be updated with new values, such as a new stamp count or a changed expiry date. Limit updates to real changes, because frequent pushes drain battery and can irritate customers.

Pass format or custom build

There are two broad routes. You can use a pass service, which is a provider that handles signing, issuing and updates through a dashboard or an API. Or you can build the pass generation yourself, using the wallet developer documentation and your own backend.

Factor Pass service Custom build
Setup time Days, with a dashboard Weeks, with a developer
Ongoing cost A monthly or per-pass fee, which varies by provider Hosting and developer time
Design control Within the provider's templates Full control within platform rules
Updates Handled by the service Your code and your certificates
Data ownership Check the terms carefully You hold the data

Pricing and terms differ between providers and change over time, so compare current quotes rather than relying on any figure in an article. Make sure the service can issue passes for both Apple and Google, because you need both wallets to reach most customers.

Designing a loyalty card that works

Keep the design simple. Wallet passes have fixed areas for a logo, a header, a primary field, secondary fields and a barcode. Use the space for what the customer needs at the counter.

For a café with a ten-stamp card, a sensible layout is:

  1. Logo and business name at the top.
  2. A large field showing "7 of 10 stamps".
  3. A secondary field with the next reward, such as "Free coffee after 10".
  4. A barcode or QR code at the bottom, with the card number printed as text.
  5. A back-of-card note with opening hours and terms.

Avoid long terms on the front, and do not place important numbers only in the barcode, because staff may need to read them out.

Counter workflow

Staff need a fast way to read the pass. Most passes display a barcode that a scanner or the staff's own phone can read. Test with the scanner at your counter, using a real pass on a real phone, in bright light and with the screen at a typical brightness. Some barcodes fail on dim phone screens, so check the setting customers commonly use.

For stamps, the staff member scans the pass, the system adds a stamp, and the updated pass is pushed back to the customer. Write the process down, and include what happens when a phone is out of battery. A paper backup, such as a printed card number, avoids a queue at the till.

Limits to accept

Passes are deliberately simple. They cannot run complex logic, such as tiered rewards that depend on purchase categories, nor can they hold large media, interactive menus or long-form content. Design the rewards to fit the card: one stamp per visit or one point per dollar spent, for example, rather than a rule that changes by product.

If your rules outgrow the pass, you can keep the pass as the front door and link it to a web page or an app for the detail. That approach uses the pass for the quick interaction and the page for the rules.

Steps to decide

  1. Write down what the customer does with the card, step by step.
  2. Confirm whether the action needs only a code, a stamp or a balance.
  3. Choose a pass category that matches the card's purpose.
  4. Pick a pass service or a custom build, using the comparison above.
  5. Test the scan at the counter on both wallets with real phones.
  6. Decide how often the card updates, and measure the effect on customer retention.

FAQ

Do customers need an app to use a wallet pass?

No. They need the built-in wallet on their phone, which both Apple and Google provide on supported devices. The business does not need a separate app.

Can a pass be updated after it is issued?

Yes, within the platform rules. Stamps, balances and expiry dates are common updates. Test the update path before you launch, so you know how long a change takes to appear.

What happens if a customer loses their phone?

They can add the pass again from the original email or link, provided the pass is tied to a customer record. Keep a card number that staff can look up, so a lost phone does not lose the loyalty history.

Is a wallet pass secure enough for vouchers?

It is suitable for many simple vouchers, especially when the barcode is checked against your system at redemption. Use unique codes for each voucher and check each one when it is used, because a copied image of a barcode is easy to share.

If you want wallet passes for your loyalty card or tickets, tell us how customers use the card now and we will help you pick the right route: get in touch.

Sources

WhatsAppBook a call