Almost every customer who walks through your door is carrying a wallet app on their phone. They use it to board flights, to pay for the bus, to enter concerts, to swipe their credit card without pulling the card out. The wallet app is one of the three or four apps that gets opened every single day on a typical smartphone. What is still uncommon — and where the opportunity lives — is for a small independent business to put its loyalty card inside that same app, next to the boarding pass and the credit card. The infrastructure has been mature for years. The platforms have caught up to small business needs. The mental shift is the part that still hasn't happened for most owners.
This guide is for the owner who has decided that wallet passes are worth a closer look and now wants to understand exactly how they work — not at the developer level, but at the level of "what does the customer see, what does my staff do, what does my dashboard look like, and what should I expect in the first ninety days." Our quick introduction to Apple Wallet loyalty covers the headline points; this is the long version that walks through every part of the system end to end.
If you're earlier in the decision and still weighing wallet against paper or a branded app, our digital vs paper guide is the better starting point. From here on, we assume you're past that question.
What a wallet pass is, exactly
A wallet pass is a small piece of data that displays as a card inside Apple Wallet on iPhones and Google Wallet on Android phones. The mental model that works for most owners is this: it sits in the same app as the customer's credit cards, debit cards, gym membership, boarding passes, concert tickets, and pharmacy loyalty card. Visually, it is a card with your branding on it. Functionally, it is connected to a server you control, which means the card on the customer's phone is always up to date with whatever you tell the server to say.
Apple Wallet and Google Wallet are the same concept built by two different companies. Both apps ship pre-installed on every smartphone sold today. Both let third parties — airlines, banks, sports teams, small businesses — issue cards that live inside them. Both support real-time updates, push notifications when the card changes, location-aware behaviors, and barcode display. The wrapper differs; the experience for the customer is close to identical.
What the customer sees when they open the pass is a single card. It carries your logo, a color palette you choose, the customer's name (if you collect it), a stamp count or point balance, a barcode they can present at the counter, and a short list of secondary fields you decide on — date enrolled, last visit, current reward state, anything brief and useful. The pass has a front (what shows by default) and a back (additional details, terms, your contact information). The customer flips between them by tapping a small button at the bottom right.
What you see, on the other side, is a dashboard. Every time a customer enrolls, you get a record. Every time their pass is scanned, you get a timestamped event. Every time a customer goes 30 days without a scan, the dashboard flags it. The pass is not a static piece of cardstock dressed up in pixels — it is a live communication channel that surfaces what is happening with each customer and lets you react to it.
The most useful single insight about wallet passes is this: the pass is bidirectional. The card on the customer's phone shows what the server says. The server learns from every scan the customer does. The two stay in sync without anyone thinking about it. That bidirectional loop is what makes wallet passes a category distinct from paper cards (zero feedback) and branded apps (feedback only when the customer chooses to open the app).
How customers get the pass
The enrollment flow is the single most important interaction in the entire program. Get it right and 60-80% of customers who see the QR code end up with a pass in their wallet. Get it wrong — by routing through an app or a signup form — and the number falls to 5-15%.
The correct flow is three taps. The customer points their phone camera at a QR code at the counter. Their phone recognizes the wallet pass format and shows a preview of the card with an "Add to Wallet" button. They tap once to add. The card is in their wallet. Total elapsed time: under five seconds. No app store, no email entry, no password creation, no account confirmation. The pass itself is the registration; there is no separate sign-up step.
The QR code is the workhorse of distribution. The most common placements are the most effective: a small tent card on the counter at eye level next to the register, a smaller version on each table for sit-down service, a QR printed at the bottom of every receipt, a sticker on the bathroom door (a captive-audience moment that converts surprisingly well), a code on the shop's window for foot traffic, a code in the email signature of the shop's newsletter, a code on every social media post that mentions the program. The goal is to place the QR where the customer's eyes already go, not where you wish they would go.
The staff script matters more than the QR design. The line that converts best at the counter is short and pressure-free: "We do loyalty if you want — scan this and the first stamp is on us." The first-stamp-free framing converts about 40% of customers who see the code, against 15-20% with a pitch-heavy script. The customer already has a phone in their hand to pay. Adding one tap to that motion is the smallest possible ask. Anything that makes them stop, reach into a bag, or think for more than a second loses them.
Compared to app installs, wallet pass enrollment runs at 10 to 20 times the conversion rate. The reason is the friction math: an app install requires eight to twelve discrete steps from prompt to first use; a wallet pass requires two taps. Each step in an app install is a place customers drop out, and the compound drop-off is what produces the single-digit install rates that app-based loyalty programs suffer from. See our pillar on loyalty programs for the distribution playbook in full context.
What happens at the counter — the scan experience
Every interaction with the loyalty program happens at the counter, in five seconds or less. Understanding what those five seconds look like from both sides is what separates a program that works from one that gathers friction.
From the customer's side: they tap the pass icon on their phone, the wallet app opens, the loyalty card is already visible (it auto-surfaces if they're physically near the shop, thanks to location triggers). The card displays a barcode. They hold the phone toward the staff member. That's it — the customer has done their part.
From the staff side: they hold a scanner — usually a tablet or phone running the platform's scanner app — toward the customer's barcode. The scan is instant. The dashboard reflects the new stamp or point. The customer's pass updates within two to four seconds, and the new stamp count appears on their screen. If the customer crossed the reward threshold on that scan, the pass transitions to a "reward ready" state visible to both sides. The staff member confirms the redemption with one tap. The customer leaves with a free coffee.
The detail that customers notice — disproportionately to its size — is the real-time update. The stamp count on their phone changes while they are still standing at the counter. They see it happen. They sometimes glance down at the screen and smile slightly. This is not an emotional manipulation; it is the natural human response to seeing progress visualized. Progress that you can watch is more motivating than progress you have to imagine. A paper stamp card hides progress behind the work of counting punches; a wallet pass shows you the count on a backlit screen and updates it in front of your eyes. That difference is part of why wallet-pass programs see materially higher second-visit conversion than paper ones.
The other detail to notice is what doesn't happen. The customer does not open a separate app. They do not have to log in. They do not have to remember anything. The staff does not have to look up an account. There is no "what email did you use last time" awkwardness. The barcode is the identifier; the scan is the entire transaction. The cognitive load on both sides is close to zero, which is what allows the interaction to fit inside the natural payment flow without slowing the line.
Push notifications — re-engagement without an app
Push notifications are the part of wallet passes that most owners discover and immediately under-use. They are the highest-visibility communication channel a small business has access to, free, and they sit on the same lock screen as text messages and bank alerts. Used well, they are the single biggest driver of repeat visits after the program is set up. Used poorly — meaning, too often or with bad content — they cause uninstalls and a permanent loss of the customer relationship.
Mechanically, a push notification on a wallet pass works like this. You change something about the pass — add a stamp, mark a reward as ready, update the strip image, change the reward terms. The change goes from your dashboard to Apple's or Google's notification servers to the customer's phone. The customer's lock screen shows a short message: "Your reward is ready," "New seasonal offer," "Double stamps tomorrow." The customer can tap to open the pass and see the full update. The whole infrastructure is free for the issuer; there is no SMS fee, no app you need to maintain.
What to send: notifications that have a real reason for the customer to look. A new reward earned is the strongest. Points expiring in a week is the second. A seasonal promotion timed to a real moment — the start of summer, a slow Tuesday, a holiday weekend — is the third. A new product the customer might want, sent only to customers whose visit pattern suggests they'd care, is the fourth. The common thread is that each notification has something concrete in it: a reward, a deadline, an offer, a relevant change.
What not to send: notifications without a reason. "Hi, we miss you" is fine occasionally; sent weekly it's spam. "Check out our new logo" is not worth a notification. "We're open today" wastes the channel. The customer's tolerance for wallet-pass notifications is much higher than their tolerance for marketing email, but it is not infinite. The threshold of abuse is the moment they delete the pass — which, unlike unsubscribing from an email, is permanent and silent.
The frequency sweet spot for most small businesses is one to three notifications per month per customer. Active high-engagement customers can tolerate more; lapsing customers should get fewer. The math behind the upper bound is simple: above three per month, opt-out rates climb sharply. Below one per month, the program goes dark and the customer loses the habit of opening the pass.
One feature underused by most small businesses: location-triggered notifications. Apple Wallet and Google Wallet both support showing the pass on the lock screen automatically when the customer is within a few hundred meters of the shop. No notification is sent — the pass surfaces silently, ready to scan. For a shop in a high-foot-traffic location, this passive surfacing produces measurable lift in walk-in repeat visits without the customer ever receiving an active push.
Designing a pass customers want to keep
The pass is brand collateral. It sits in the customer's most-used app, between their boarding passes and their bank cards. How it looks determines whether they think of your shop as one of those tiers of business — premium, considered, worth keeping — or as something more disposable. Most pass design is utilitarian and forgettable. A small amount of design care produces a pass customers screenshot and share, which is the cheapest organic marketing you can run.
The brand basics: your logo, your color palette, a typeface that matches the shop's identity. Most platforms expose a foreground color (the text on the pass), a background color (the dominant pass color), and a logo slot. Use the shop's actual brand palette rather than the platform's default. The pass should look like a continuation of the shop's other surfaces — your signage, your menu, your packaging — not like a generic loyalty template.
The strip image — the large photo area near the top of the pass, present on Apple Wallet passes — is the most underused brand surface in small business loyalty. It can hold real photography. A photo of your best-selling pastry, your storefront on a sunny day, your barista pulling a shot, a seasonal product spread. Real photos beat stock by a wide margin; they make the pass feel like it belongs to a real place rather than a marketing template.
Customer name personalization, when collected, raises engagement noticeably. The pass that says "Sarah's loyalty card" feels meaningfully different from one that says "Loyalty card." If you do not want to ask for the name at enrollment, you can prompt for it on the first reward redemption — by then the customer is committed and willing to share.
Information hierarchy matters. The front of the pass is what gets seen at every glance — current stamp count, reward state, next milestone. The back of the pass is for the long-tail information — full reward terms, your contact details, your address and hours, links to your social. Keep the front aggressively simple; bury the legal and reference content on the back where it is available but not in the way.
At Claus Haus, Léa Moreau rotates the strip image monthly. The summer card carries a photograph of an iced drink; the autumn card carries a pumpkin pastry; the winter card carries the shop's window at dusk. The change is small. The result is that regulars notice the pass even on weeks they didn't earn a stamp, and a small percentage of them screenshot the seasonal art and post it. That last detail produces five to ten new customers per quarter, attributed to the pass design as a marketing channel. The pass is not only a loyalty record — it is a small, recurring touchpoint with your brand.
Dark mode is worth a thought. Both wallet apps respect the customer's system theme, which means your pass design needs to read against both a light and a dark background. Designs that rely on a light background often look poor when the customer's phone is in dark mode. Test both before publishing.
Apple Wallet vs Google Wallet — the differences that matter
For the customer, the two platforms feel almost identical. For the business owner choosing a platform, a few differences are worth understanding before signing up.
The pass format is different under the hood. Apple Wallet uses a file format called PKPass, a signed bundle of design and data. Google Wallet uses a different format based on signed digital objects — a different technical mechanism, same practical result. You will never touch either format directly; the platform you use handles both. But it is worth knowing they are different formats so you understand why a platform needs to support both — they are not the same file shipped twice.
The visual layout is slightly different. Apple Wallet passes have a fixed structure: header on top, large image strip in the upper middle, primary field below the strip, secondary fields beneath that, barcode at the bottom. Google Wallet passes have a similar but not identical structure, with a "hero image" rather than a strip image and slightly different field placement. A platform that designs the pass once for both should auto-adapt; if you are seeing different layouts on iOS and Android that look like accidents rather than intentional, the platform is shipping each format separately rather than translating between them.
NFC support differs. Newer wallet passes can include NFC capability, which means the customer can tap their phone against an NFC reader instead of presenting a barcode. Apple has been gradual about opening this; Google has been more permissive. For the average small business with a barcode scanner, NFC is not a critical feature. For shops considering tap-to-redeem flows, it is worth confirming the platform supports both.
The update mechanism differs slightly. Apple Wallet uses a push-based model: your server tells Apple's servers about a change, Apple delivers it to the phone, the pass updates. Google Wallet supports both push and pull mechanisms, which can be marginally faster in some network conditions. Customer-visible difference: minimal to none. Both update within seconds.
Location-triggered surfacing differs. Apple Wallet's geofence behavior is more conservative; Google Wallet's tends to surface passes more readily. Neither is "right"; they are tuned differently to balance user attention against utility. The practical effect: your pass appears on customers' lock screens slightly more often on Android than iOS when they are near your shop. The difference is small enough that it should not drive platform choice.
The takeaway: any platform worth using handles all of this for you. You design the pass once, you brief it once, you publish it once, and the platform handles the Apple and Google sides without your involvement. If a platform is asking you to think about format conversion or update mechanisms, it is exposing infrastructure that should be hidden.
The data you get for free
Every wallet pass scan produces a timestamped record on your dashboard. Aggregated across customers, those records become the program's intelligence layer — and it arrives without any extra work on your part. Paper cards give you a gut feeling about who your regulars are. Wallet passes give you the names, the dates, and the patterns.
Visit frequency per customer is the foundational metric. The dashboard shows, for any active customer, the number of visits in the last 30 days, the median time between visits, and the trend over time. A customer who used to come twice a week and is now coming once every two weeks is flagged before they fully disappear. That window — between "drifting" and "gone" — is where most retention work has the highest return, and paper-card programs do not surface it at all.
Dormancy detection works on the same principle. The dashboard shows you a list of customers who haven't scanned in a defined window (typically 21 or 30 days). For each, you have their enrollment date, total visits, and last activity. That list is your win-back candidate pool. A personalized push notification — "We saved you a Tuesday treat, come by this week" — converts dormant customers at 15-25% when timed well, against approximately 0% for the same customers if you have no list and no channel to reach them.
Referral tracking closes the growth loop. When a customer brings a friend who scans the referrer's QR, both passes update, and the dashboard records the relationship. Over time you can see which customers are bringing how many new customers, which lets you reward referrers in proportion to their value. The data also makes the referrals visible to your team — the staff who knows that a regular brings three new customers per month treats that regular slightly better, and the cycle reinforces itself.
Redemption patterns surface which rewards drive the most repeat behavior. If you offer two rewards — say, a free coffee at ten stamps and a free pastry at fifteen — the dashboard shows you which redemption produces a higher likelihood of a return visit within seven days. That data drives the next iteration of the program: more of what works, less of what doesn't. None of this analysis is possible on paper; the dashboard makes it visible without any analyst skill required.
The contrast worth naming: with a paper stamp card, your best data is a gut feeling. With a wallet pass, you know. Our quick comparison of digital cards and paper spells out the difference in less depth if a short version is more useful. The first-quarter cost of moving from one to the other is a platform fee in the range of €30-50 per month. The first-quarter benefit is a complete picture of customer behavior that you previously had to guess at. See the retention statistics guide for the benchmark numbers by vertical that make the value of this data concrete.
The data also makes customer abandonment patterns visible — which is the precondition for doing something about them.
What to look for in a wallet pass platform
Not every platform that markets "digital loyalty" is the same product. The criteria below filter the market into the small set of platforms worth evaluating.
True wallet-native. The passes live in Apple Wallet and Google Wallet. The customer never installs an app. If a platform's enrollment flow involves a download from the App Store or Play Store, it is not wallet-native — it is an "app-wrapper" platform pretending to be wallet-native. Enrollment rates on app-wrapper platforms drop back to the 5-15% range that all small-business apps suffer from. This is the single most important distinction in the market.
White-label as a default. The customer should see your shop's name, logo, and color palette on the pass, the QR code, and any landing page they hit during enrollment. If the platform's brand appears anywhere customer-visible, the platform is not built for small business — it is built for the platform's own marketing benefit.
Real-time pass updates. The stamp count change should reach the customer's phone within seconds of the scan at the counter, not minutes. Slow updates break the visual feedback loop that makes wallet passes feel different from paper. Ask for a live demo; if the platform hesitates, the updates are slow.
Multi-language support. Customers should see the pass in their language automatically — typically based on their phone's system language. In any market with linguistic diversity, this is table stakes. Without it, half your customers see your pass in the wrong language.
No customer account required. The customer should be able to add the pass without entering an email, creating a password, or confirming a registration. Each required step lowers enrollment. The pass itself is the account; nothing further should be necessary.
Native push notification capability. Push should ship through Apple's and Google's free notification systems, not through paid SMS gateways. Platforms that charge per notification are usually using SMS underneath, which scales badly with the program's success.
Analytics dashboard. You should see, at a glance, your active customer count, recent enrollments, dormant customer list, scan trends over time, and per-customer history. Bonus if there's an export option for the data you need to take with you if you ever switch platforms.
The comparison page covers how Fideliya stacks up against the main alternatives across these criteria. The coffee shops vertical page covers what calibrates well for high-frequency loyalty businesses.
Getting started — your first wallet pass in under an hour
The realistic time to go from zero to a live program is about an hour. The deliberation usually takes longer than the actual setup.
Step one (15 minutes): design the pass. Upload your logo. Pick your brand colors (foreground and background). Pick a strip image — a real photo from your shop, not stock. Set the customer-visible name of the program ("Stamp Card," "Café Loyalty," whatever feels right). Define the reward — "free coffee after 9 stamps" is a good default. Save.
Step two (15 minutes): set up the program logic. Define your stamp threshold, your reward, and any secondary mechanics (referral bonus, birthday reward, second-visit reward). Don't overcomplicate this on day one — one stamp card, one reward. You can add complexity later once the program is running.
Step three (10 minutes): generate and print QR codes. Download the QR. Print it at a few sizes — a tent card for the counter, a smaller one for tables, a sticker for the window. Most platforms ship printable templates; use them.
Step four (5 minutes): brief the staff. The script: "We do loyalty if you want — scan this and the first stamp is on us." That's it. No technical explanation. Practice once at the counter with a phone so the team sees the flow.
Step five (15 minutes): set up notifications and the first welcome message. Schedule a small welcome notification — "Thanks for joining — here's your first stamp" — to go out automatically on enrollment. Configure a one-month dormancy trigger to catch customers who go quiet.
The 30-day check: at the end of the first month, look at four numbers in your dashboard. Total enrollments. Scan frequency per active customer. Return rate within 14 days. Number of dormant customers. The first quarter is when patterns start to compound — don't pull the plug at week six because the curve hasn't lifted yet. Programs typically need 60-90 days to show measurable retention shift.
For the math on what a working program will mean in revenue terms for your specific shop, the ROI calculator takes your ticket size and visit frequency and surfaces the number that matters. For a side-by-side of how the main wallet-native platforms stack up, the comparison hub covers the trade-offs you'll otherwise have to evaluate one demo at a time.
The pass goes live. The QR code goes on the counter. The staff says the line. Within the first week, the first stamps are added, the first passes are updated, and the first dashboard numbers start coming in. Three months later, you have a customer base you can see — names, patterns, dormancy signals, referral records — and a channel to reach them that costs nothing per message. That is the difference between running a loyalty program and running a paper exercise that hopes to be one.