The technology is already in your customers' pockets. Apple and Google Wallet come pre-installed on virtually every smartphone and are opened daily to carry boarding passes, event tickets, and loyalty cards. A wallet pass is not a digital version of a plastic card. It is a live, location-aware channel that pushes to the lock screen, responds to where someone is, and generates first-party data from real-world interactions. No app required. No login. One tap to add. This guide covers what wallet passes are, how they work, and the range of what brands are already doing with them.
Most brands have no direct relationship with the people buying their products. They know aggregate numbers. Sell-through rates. Redemption averages. But they do not know who, exactly, walked into a store and picked something off a shelf. That data lives with the retailer, or the aggregator, or nowhere at all.
A wallet pass changes that. It is a small, persistent presence in a consumer's phone that a brand controls directly. Not through an app they have to persuade someone to download. Not through an email buried under forty others. Through Apple Wallet and Google Wallet, which are already on virtually every smartphone, used daily to carry boarding passes, loyalty cards, and event tickets.
What is a wallet pass?
A wallet pass is a digital file that lives in Apple Wallet or Google Wallet on a consumer's phone. It can look like a loyalty card, a membership, an event ticket, a coupon, a gift card, a voucher, or a branded stamp card. But the visual form is the least interesting thing about it.
Unlike a static card or printed voucher, a wallet pass is a live object. It updates in real time. It pushes notifications to the lock screen without asking the consumer to open an app or check an inbox. It responds to location. When a consumer walks near a partner store, the pass can surface automatically. When they scan a product, the pass can update. When a loyalty tier changes, the pass reflects it instantly.
The consumer sees a card in their phone. The brand has a direct channel to an individual that did not exist before.
How a wallet pass works
A wallet pass is built on an open standard that Apple and Google both support, though their implementations differ in some details. At the technical level, it is a structured data file, signed with a certificate, distributed via a link, QR code, or NFC tap.
From the consumer's side, the process takes seconds. They scan a QR code, tap a link in an email, or hold their phone near an NFC point. A prompt appears: Add to Wallet. One tap. The pass is there. No app store. No login screen. No account to create.
From that point, a brand can push notifications to the lock screen, update the pass content (a loyalty balance, a remaining voucher value, an event time change), and trigger location-based messages when the consumer enters a defined area. Everything runs through the wallet infrastructure the consumer already uses.
On the brand's side, every interaction generates data. Scans, redemptions, notification opens, location triggers. For a brand that previously had no visibility beyond delayed aggregate retail numbers, this is a different kind of relationship.
Apple Wallet and Google Wallet serve different phone ecosystems but work the same way from a brand's perspective. A well-built pass programme issues to both, so the consumer experience is consistent regardless of device. The practical difference is technical: Apple uses its own .pkpass standard; Google uses its own object format. A specialist pass platform handles both so brands build once and reach everyone.
What makes it different from other channels
Apps require a download. Only a fraction of people who encounter a brand will download its app, and of those, only a fraction will keep it. Mobile apps lose 75% of their users within the first three days of install. Retail apps have a 68% abandonment rate. The app is a high-friction commitment most consumers will not make, and the ones who do mostly leave almost immediately.
Email lands in a promotional tab. Open rates sit between 15 and 25 percent on a good day, before accounting for filtering and inbox fatigue. Email has its place, but real-time location-aware engagement is not it.
SMS gets read, but it generates resistance. People guard their phone numbers. Opt-in rates are lower, and the channel carries a perception of intrusiveness that limits what brands can do without eroding goodwill.
A wallet pass sits in a different category entirely. It requires no ongoing permission negotiation. It is not competing against hundreds of other notifications. It does not ask the consumer to download anything, remember a password, or maintain a relationship they did not ask for. It is already there, in the wallet they open to pay for their coffee.
The reach is built in. The relationship is direct. The data is first-party and owned by the brand.
What you can do with one
The practical range is wider than most marketers initially assume.
Take notifications. A wallet pass pushes to the lock screen without an app. The message appears in the same place a flight reminder does, without asking anything new from the consumer.
Then there is location. When a consumer enters a geofenced area, whether that is a store, an event venue, or a partner location, the pass can surface and push a relevant message. The consumer did not open anything. The pass responded to where they were.
Content updates in real time, too. A loyalty balance updates when a purchase is made. An event pass updates if the start time changes. A voucher tracks remaining value. The consumer always has the current version without doing anything.
A pass can also run a stamp-card mechanic, unlock content after a set number of scans, or reveal a reward when a threshold is reached. For an FMCG brand running an on-pack activation, this is a direct-to-consumer engagement layer built into the product itself.
And underneath all of it: first-party data from real-world interactions. Every scan, redemption, and notification response is tied to an individual. For brands used to aggregate retail data delivered weeks after the fact, this changes what they can know and when they can know it.
The passes that work best are not thought of as digital cards. They are thought of as channels. A live, updateable, location-aware presence in a consumer's pocket that a brand owns and controls.
Who is already using them
Events and ticketing have the longest history here. Airlines put boarding passes in Apple Wallet years ago. Sports teams and festivals use wallet passes to replace printed tickets and push pre-event messages. The infrastructure is proven. The consumer behaviour is already set.
Retail loyalty is the second major area. A loyalty card in a wallet is more useful than a plastic card in a drawer. The wallet version pushes relevant offers, tracks points in real time, and triggers messages near store entries. The consumer has everything they need without thinking about it.
Hotels, airlines, tour operators, ticketing platforms, membership clubs, and brand marketing teams across retail and FMCG are all building wallet programmes. What they have in common: a direct channel that requires nothing new from the consumer and generates data the brand actually owns.
Why now
Apple and Google Wallet have been around for years. The question of timing is fair.
Start with scale. Over 1.3 billion people worldwide carry Apple Wallet or Google Wallet on their phone. The audience is not a bet on future adoption. It is already there.
The personalisation data makes the case for a direct channel sharper still. 80% of shoppers prefer brands that offer personalised experiences, and they spend 50% more with those brands. The wallet pass is one of the few channels that can deliver that personalisation without asking the consumer to download anything.
Loyalty numbers tell the same story from a different angle. The average person is enrolled in 17 loyalty programmes but only active in half of them. The gap is not a motivation problem. It is a friction and relevance problem. A loyalty pass already in the wallet is there when someone pulls their phone out at the till. A card they forgot they had is not.
On engagement: push notifications generate click-through rates of around 28%, compared to 1-2% for email. For brands measuring campaign performance, that gap is hard to ignore.
The technical capability has matured alongside the audience. Location services, NFC tap-to-add, real-time push, and pass management have reached a level of reliability that makes consumer-grade wallet programmes feasible without a dedicated engineering team. And awareness is shifting. Until recently, most marketing teams associated Apple Wallet with boarding passes. The range of what the wallet can do for brand engagement was not common knowledge. That is changing.
The consumer side has been ready for a while. The wallet is already there, already trusted, already opened daily. The gap has been on the brand side: knowing what was possible and having a practical way to act on it.
Getting started
A wallet pass programme does not require a development team or a lengthy integration project. The starting point is usually a single defined use case. A loyalty card. An event ticket. A membership. A promotional voucher.
From there, the work is about what the pass should do, what data it should collect, and how it connects to what already exists. CRMs, POS systems, loyalty engines, ticketing tools. A pass programme can connect to existing infrastructure rather than replacing it.
For platform and API users, the integration path is documented and the infrastructure handles the heavy lifting. For brands and marketing teams who want to run wallet programmes without a technical team involved, campaign management tools handle it directly.
One thing worth understanding before choosing how to build: Apple and Google both update their wallet specifications regularly. Passes that work today need to keep working as those platforms evolve. A specialist pass platform manages that on a brand's behalf, absorbing Apple and Google requirement changes so the programme does not break when either company ships an update. It is one of the less obvious reasons to use purpose-built infrastructure rather than building pass management in-house.
The capability is already in your customers' pockets. The question is what you do with it.
Ready to build your first wallet pass programme? Talk to the Passform team
