Apple Wallet is the app that already lives on every iPhone. It holds debit cards, boarding passes, event tickets, and increasingly, loyalty cards. For a business owner, putting a loyalty card into Apple Wallet means meeting the customer where their other valuables already are — no download, no friction, no separate app to maintain. If you're still weighing the move, the paper vs digital comparison is the right starting point.
This is the practical guide: how the technology works, what customers actually see, what it costs to run, and why the adoption numbers leave app-based loyalty programs behind.
How Apple Wallet passes actually work
An Apple Wallet loyalty card is a file format called .pkpass. It contains the card's design, the customer's stamp or point count, the merchant's branding, and a connection back to a server. When the merchant updates the card — adds a stamp, marks a reward as ready — the server pushes the change through Apple's notification system. The card on the customer's phone updates within seconds.
The technical pieces matter only to the platform building the pass. As a business owner, you never touch the .pkpass file directly. You design the card in a dashboard, define the reward logic, and the platform handles certificate signing, push notifications, and delivery. What ships to the customer is a single tap.
What sits on the customer's lock screen is what matters. When they're within a few hundred meters of your business, the pass surfaces automatically. When you add a stamp, a notification appears with the new count. When they're ready to redeem, the pass shows the reward state without any taps required.
What the customer experience looks like
The enrollment flow is two steps. A customer scans a QR code at the counter, on a tent card, or on your receipt. The phone opens the pass preview — your logo, your colors, the program details. They tap "Add to Apple Wallet" and the card lands next to their debit card. Total time: under five seconds.
From there, the card behaves like any other Apple Wallet pass. It shows on the lock screen when geographically relevant. It updates in real time when stamps are added. It survives device upgrades automatically — buy a new iPhone, sign into iCloud, the loyalty card follows. The customer can't lose it the way they lose a paper card.
The redemption moment is also two steps. The customer hands the phone over, staff scans the pass barcode, the reward is applied. Done. There's nothing to install, nothing to log into, nothing for the customer to remember between visits.
Adoption rates: wallet passes vs app downloads
This is the number that ends most debates. Wallet-based loyalty programs typically see 60-75% enrollment rates among customers who are offered the card. App-based loyalty programs see 10-20% — the rest of the customers see the prompt to download, decide it's not worth it, and the moment passes.
The reason is friction math. Adding a wallet pass is two taps. Downloading an app is: app store tap, search, install, open, signup, account creation, notifications permission, location permission, and finally enrollment. Each step is a place customers drop off. The compounded drop-off is why app loyalty programs see such low conversion.
The same customer who'd say "no thanks" to downloading another app will happily add a wallet pass. The decision isn't about interest in the loyalty program — it's about the cost of saying yes. Wallet passes lower that cost to near-zero.
The friction of saying yes determines who enrolls. Wallet passes get to yes in two taps. Apps require ten.
What it costs to run
The pricing for wallet-native loyalty platforms in 2026 typically runs €0-€99 per month. Small businesses land in the €30-50 range for the plan with the features they need — branding, points, referrals, push notifications, full analytics. The full cost breakdown across all loyalty platform types is worth a read before committing.
One cost detail to watch: some developer-oriented platforms require you to maintain your own Apple Developer Account, which costs $99 per year and is billed separately by Apple. Turnkey platforms like Fideliya bundle the certificate management — you never see the Apple Developer side of things. If you're evaluating a platform and the setup instructions mention "your Apple certificates," that's a signal you're looking at infrastructure rather than a finished product.
Per-scan fees, SMS messaging fees, and setup fees can quietly add to the bill on some platforms. Wallet-native programs that include push notifications natively don't carry these — the notification goes through Apple's free push system, not through paid SMS.
Google Wallet works the same way
Every credible loyalty platform supports Google Wallet alongside Apple Wallet, not one or the other. The pass formats are different under the hood — Apple uses .pkpass, Google uses JWT-signed objects — but the customer experience is identical. Android users tap "Add to Google Wallet," the card lives next to their Google Pay cards, and the same lock-screen behavior applies.
If you're evaluating a platform that only supports Apple Wallet, that's a red flag. Roughly half your customers won't have iPhones, and locking out Android users defeats the universal-distribution argument that makes wallet loyalty work in the first place.
Common misconceptions
"My customers aren't tech-savvy enough for this." This concern is usually rooted in an outdated picture of the customer base. The same customers who can't be talked into downloading an app are routinely using Apple Pay at the same counter. Wallet passes use the same wallet they're already opening to pay. There's no new skill to learn.
"It's complicated to set up." On modern platforms, designing your first wallet pass takes about five minutes. You pick a template, upload your logo, set the reward threshold, and download a QR code to print. The complexity is in the platform's infrastructure, not in your dashboard work.
"Customers will see my card alongside competitors and switch." Customers see passes from businesses they've already chosen to enroll with. Your card sits next to the other businesses they love, not next to your competitors. The comparison only happens if a customer enrolls in both programs voluntarily — which means they're already a customer of both.
What you can't do with wallet passes
Wallet passes are cards, not apps. The limitations matter to understand before committing.
You can't take in-pass purchases. The pass doesn't process payment. Stripe, Square, or your existing POS still handles transactions — the wallet pass is the loyalty record, not the payment instrument.
You can't build complex app-like interactions. The pass surface area is fixed: a logo, a barcode, a counter, optional fields like a member name or tier. There's no rich UI, no chat, no in-pass browsing.
You can't push unlimited content. Notifications are intentionally limited by Apple and Google to prevent abuse. A few targeted pushes per month per customer work well; ten per week will get you flagged and silenced.
These limitations are features, not bugs. The customer enrolled in a wallet pass because it doesn't behave like an app. Respecting that constraint is what makes the channel keep working.
Apple Wallet loyalty cards turn the customer's phone into your most reliable touchpoint — without asking them to download anything. The technology has been mature for years. The platforms have caught up. For any small business currently running a paper stamp card or a low-adoption loyalty app, the wallet route is now the default answer.