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, from airlines and banks to sports teams and 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, a stamp count or point balance, the reward they are working toward, and a barcode they can present at the counter. The pass has a front (what shows by default) and a back (how the program works, its terms, and the latest message you sent). 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. When a customer goes 30 days without a visit, the Overview counts them under Due back. 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 most customers who see the QR code walk away carrying a pass. Get it wrong, by routing them through an app store or an account to create, and almost none of them do. No trustworthy published figure exists for either rate, so watch your own counter for a week: that number is yours, and it is the only one that can tell you anything.
The correct flow is three taps. The customer points their phone camera at a QR code at the counter. Their phone opens your join page, with a preview of the card. They give a name and an email on one short form, with the phone optional, and tap "Add to Wallet". The card is in their wallet. No app store, no password creation, no account confirmation. That short form is the registration; there is no second sign-up step and nothing to install.
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 gives the customer something before it asks for anything, which is why it beats a script that opens with the reward ladder. 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 an app install, wallet pass enrollment asks for almost nothing. The friction is the whole explanation: an app install runs through the store, the download, the open, the account and the permission prompt before a customer has earned anything, and every one of those is a place to stop. A wallet pass has the scan and the add. Published conversion rates for either side of that comparison come from companies selling one of them, so the honest claim is structural rather than numeric: fewer steps, fewer exits. 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 (if the shop has pinned its address, the phone may already be suggesting it as they walk in). 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, Fideliya's scanner running in the browser on a tablet or phone, toward the customer's barcode. The scan is instant. The dashboard reflects the new stamp or point. The customer's pass updates, 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 customers notice, out of all proportion 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.
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, which means 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. Something about the pass changes: a stamp is added, a reward becomes ready, you change its design, or you send a message. Fideliya updates the pass through Apple's or Google's servers, and the change can arrive with a short line on the lock screen, such as "Your reward is ready" or a message you wrote, like "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. A reward one visit away is the second. The third is a seasonal promotion timed to a real moment, such as the start of summer, a slow Tuesday or a holiday weekend. A new product, sent to the audience it suits (customers seen in the last 30 days, or those who have been away longer), 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, and unlike unsubscribing from an email, that is permanent and silent.
Our recommendation, offered as a starting point rather than a measurement, is a small handful of messages a month. Fideliya includes 1 broadcast a month on Free, 3 on Pro and 10 on Enterprise, and the line a stamp or a reward puts on the pass is not one of them. Active high-engagement customers can tolerate more; lapsing customers should get fewer. The reasoning runs in both directions: send too often and the pass becomes something to silence, send too rarely and the program goes dark and the customer loses the habit of opening it. Where your own ceiling sits is something only your own opt-out rate can tell you.
One feature underused by most small businesses: the location pin. When a business pins its address, Fideliya writes that point into every pass, up to ten branches. On an iPhone, the pass can then appear on the lock screen near the shop with a line that names it, such as "Café Lina is nearby"; on Android, Google Wallet can show a notification that opens the pass. Neither is a message you send, and neither is a promise: the phone decides when, Google decides how close, and a customer can turn the suggestion off. It is a reminder at the door, not a broadcast.
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 and your color palette. Fideliya gives you a logo slot, a background color (the dominant pass color), a foreground color (the text on the pass) and a label color. Use the shop's actual brand palette rather than the platform's default. The pass should look like your signage, your menu and your packaging carried onto the phone, not like a generic loyalty template.
The strip image, the large photo area near the top of an Apple Wallet pass, is the most underused brand surface in small business loyalty, and on Fideliya it is a Pro feature. 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.
The customer's name belongs on the pass. Every Fideliya customer joins with a name, and the pass carries it on the front, so the card that says "Sarah" is Sarah's and nobody else's.
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 holds the long-tail information: how the program works and its terms, the latest message you sent, and, when you set them up, directions to the shop and a link to leave a review. Keep the front simple; the reference content lives on the back, where it is available but not in the way.
One pattern worth copying: rotate the strip image with the season. A summer card carrying a photograph of an iced drink, an autumn card carrying a pastry, a winter card carrying the shop's window at dusk. The change is small. The effect is that regulars notice the pass in the weeks they didn't earn a stamp, and some of them screenshot the seasonal art and post it. The pass is not only a loyalty record. It is a small, recurring touchpoint with your brand, and it is the only one that lives where the customer keeps their boarding passes.
Dark mode is worth a thought. The pass keeps the colors you set, while the wallet around it follows the customer's system theme, so a pale pass sits in a dark wallet on some phones and a dark pass in a light one on others. Look at your pass on a phone in each mode 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. The mechanism differs; the practical result is the same. 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. For Apple Wallet, Fideliya tells Apple's servers that a pass changed, and the phone fetches the new version. For Google Wallet, Fideliya updates the pass on Google's servers, and Google brings the phone up to date. Either way the customer does nothing: the card on their phone changes on its own.
Behaviour near the shop differs, and neither platform publishes the details. On an iPhone, a pass near one of its locations can be suggested on the lock screen, and the customer can switch that off pass by pass. On Android, Google sends a notification to people who have notifications on and have given Google Wallet precise, always-on location access; Google decides how close they need to be and how long they need to stay. Fideliya does not know which happens more often, so 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 is the foundational metric. Each customer's record holds their visits with their dates, so a regular who used to come twice a week and now comes once a fortnight shows it in their own history, and on Pro, How often they come shows the pattern across all your customers. The line Fideliya draws for you is 30 days, under Due back. The window between "drifting" and "gone" is where most retention work has the highest return, and paper-card programs do not surface it at all.
The Overview counts the customers who have not been in for over 30 days under Due back and names them, and the Customers page's Inactive filter opens the same people, each with their record. That list is your win-back pool. A message to them, "We saved you a Tuesday treat, come by this week", is one you can only send because the list exists, and Send them a message sits beside it. The comparison that matters is not against some published win-back rate. It is against the alternative, which is having no list, no channel, and no way of knowing those customers stopped coming.
Referrals close the growth loop, on Pro. The QR on a customer's pass doubles as their referral link: a friend who scans it with their phone camera joins through it, and when that friend makes their first visit, both earn the bonus you set. Fideliya counts the referrals on each pass and names your top referrer, and the Overview's Latest lists each referral as it lands. The data also makes the referrals visible to your team. The staff member who knows a regular brings three new customers a month treats that regular slightly better, and the cycle reinforces itself.
Redemptions show whether the reward works. Your offer, on the Analytics page, gives each pass its own card: how far along your customers are, the three closest to the reward, how long a first reward takes, and how many rewards are waiting to be claimed. That data drives the next iteration of the program: a goal nobody reaches is too far away, and a reward nobody claims is not worth the trip. 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 published, flat platform fee: Fideliya's free tier is €0 and covers 20 customers, and Pro is €49.99 a month, or €39.99 a month billed yearly. The first-quarter benefit is a complete picture of customer behavior that you previously had to guess at. See the retention statistics guide for what is worth measuring on your own books, and why the benchmark numbers circulating in this category are not.
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 one, and it inherits every drop-off an app install has ever had. This is the single most important distinction in the market, and it is the one a vendor will blur if you let them: ask to watch a real customer enroll, on a real phone, and count the steps yourself.
Your brand in front. The customer should see your shop's name, logo, and color palette on the pass, the QR code, and the page they join on. On a Fideliya pass the platform's name appears once, as a line on the back of the card, and white-label removes it as a one-time purchase.
Real-time pass updates. The stamp count change should reach the customer's phone. 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. The pass should read in your customers' language. Fideliya passes come in English, French, Spanish and Arabic, with Arabic laid out right to left: you choose the language for each pass, and its labels, dates and notifications follow it on every phone. In any market with linguistic diversity, this is table stakes.
No customer account to create. The customer should add the pass without creating a password, installing an app or confirming a registration. Each extra step lowers enrollment. Fideliya asks for a name and an email on one short form, which is how you know who your regulars are; the pass itself is the account.
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, who came in, who came back, who joined, who is due back, the trend over time, and each customer's history. Fideliya exports the data as CSV on Pro, which is what you take with you if you ever switch platforms.
The comparison page covers how Fideliya stacks up against the main alternatives across these criteria. The vertical pages for coffee shops, spas, hair salons, and gyms cover what calibrates well for each kind of loyalty business.
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). On Pro, add 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 (a smaller reward partway to the goal, or a referral bonus on Pro). 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): write your first message. Every new customer gets a welcome email when they join. After that, you write: a short message to everyone holding the card, sent now or scheduled for later. Fideliya sends no reminder on its own, so the customers who go quiet are the ones you reach from Due back, with Send them a message.
The first-month check: look at four numbers in your dashboard. New customers. Visits against Customers in. Returning. Due back, on the Overview. Free reads the last seven days; Pro reads the whole month at once. The first quarter is when patterns start to compound, so don't pull the plug at week six because the curve hasn't lifted yet. A loyalty program is a repeat-visit mechanism, and it cannot show you a repeat-visit effect faster than your customers' own visit cycle allows.
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, who is due back, who brought whom) and a channel to reach them, with broadcasts included in every plan each month. That is the difference between running a loyalty program and running a paper exercise that hopes to be one.