A ticket should not be buried in an email. A loyalty card should not be forgotten in a drawer. And customers should not need to download another app simply to access something they have already purchased.
Apple Wallet and Google Wallet passes solve these small but persistent frustrations. They place event tickets, loyalty cards, memberships, vouchers and access passes somewhere customers already know how to find: their phone’s wallet.
The result is not merely a more modern card. It is a faster, more useful and more continuous customer experience.
The wallet is becoming everyday infrastructure
Digital wallets are no longer a niche feature used only for contactless payments. Juniper Research estimated that 4.4 billion people used digital wallets worldwide in 2025 and expects that figure to exceed six billion by 2030.
McKinsey found that in-store digital-wallet usage in the United States increased from 19% in 2019 to 28% in 2024. More tellingly, one in five digital-wallet users surveyed in the United States and Europe said they often leave home without a physical wallet.
These figures primarily measure payments, but they reveal a broader behavioral change: customers increasingly treat the wallet on their phone as the default place for items they need while moving through the physical world.
That makes it a natural home for:
- Event and conference tickets
- Loyalty and punch cards
- Membership cards
- Coupons and vouchers
- Visitor, day and access passes
- Season tickets and recurring credentials
Unlike a PDF, email attachment or screenshot, a wallet pass can remain connected to the business that issued it.
Customer retention often begins with removing friction
Businesses frequently approach retention through rewards, campaigns and personalization. Those things matter, but the experience usually fails at a more basic level first.
The customer cannot find the ticket. The barcode is too small. The membership number is in an old email. The event time changed, but the original confirmation did not. The loyalty card was never brought to the store.
Salesforce research found that almost 60% of consumers prefer using fewer touchpoints to obtain information or complete a task. It also found that poor service would prevent 43% of consumers from purchasing from a company again, while more than a third said inconvenient or clumsy experiences could cause a brand to lose them.
A wallet pass removes several of these touchpoints:
- The customer opens Apple Wallet or Google Wallet.
- The relevant pass is immediately recognizable.
- The barcode, membership details or current status is ready to use.
- Updated information can appear on the same pass.
No account search, attachment download or separate application is required.
That reduction in effort may appear minor. Across hundreds or thousands of customer interactions, however, it determines whether a process feels effortless or poorly designed.
A wallet pass remains useful after it is issued
Traditional tickets and membership cards are static. Once distributed, their information is effectively frozen.
Wallet passes can be dynamic.
Apple describes Wallet passes as interactive items that can remain up to date, integrate with notifications, Maps and Live Activities, and display multiple upcoming events through one ticket. Apple Wallet can also surface a relevant pass on the Lock Screen based on its configured time and location.
Google Wallet can send upcoming event reminders, display nearby-pass notifications and notify customers when supported information changes. Event-ticket updates can include the venue, start time, gate, section, row or seat.
This changes the role of the pass. It is no longer only proof of admission or membership. It becomes a lightweight service channel.
An event organizer can update a gate or start time. A loyalty program can display a new points balance. A membership pass can reflect a renewed tier. A voucher can show its validity period or current redemption status.
The customer continues referring to the same item instead of receiving a new document every time something changes.
Visible loyalty is more likely to be used
Many loyalty programs do not fail because the rewards are unattractive. They fail because customers forget the program exists.
A loyalty card inside the phone’s wallet reduces that visibility problem. It can show the customer’s name, points, tier, membership number, available reward or next milestone at the moment it is needed.
Google Wallet supports updates and notifications for fields such as loyalty-point balances and reward tiers. Apple’s loyalty passes can also be updated according to customer activity and presented automatically in supported contactless scenarios.
This creates a useful retention loop:
Purchase → visible progress → achievable reward → repeat visit
The impact of loyalty programs is not theoretical. EY’s loyalty research found that 58% of surveyed consumers reported increasing their spending to a moderate or significant extent because of loyalty programs.
The wallet pass does not create loyalty by itself. It makes the value of a well-designed loyalty program easier to see, access and redeem.
Event satisfaction starts before the customer arrives
For an attendee, an event ticket is one of the first operational interactions with the organizer.
A difficult ticketing experience creates uncertainty before the event has even started. A clear mobile ticket does the opposite: it reassures the attendee that the purchase succeeded, communicates where and when to arrive, and provides an obvious credential at the entrance.
Wallet-based event tickets are particularly effective because they can support the complete ticket lifecycle:
Google Wallet can automatically remind users three hours before an event, while Apple Wallet can surface passes when their configured date and location become relevant.
For recurring events, season tickets and membership-based venues, the same pass can support more than a single transaction. Apple has continued expanding Wallet in this direction, including support for multiple upcoming events within one poster event ticket.
Personalization without building another app
Personalized customer experiences are valuable, but they can become counterproductive when they require excessive data collection, complicated onboarding or another application download.
Wallet passes offer a narrower form of personalization. A business can personalize the information that is directly useful to the pass holder:
- Attendee name and seat
- Membership level
- Current point balance
- Validity dates
- Remaining redemptions
- Assigned entrance or location
- A customer-specific barcode
- Relevant links and instructions
This is often enough to make the experience feel individual without attempting to turn every customer interaction into a large app ecosystem.
The principle should be utility before promotion. A pass earns its place in a customer’s wallet when it helps them complete a task. Excessive or irrelevant notifications will undermine that trust.
Where wallet passes deliver the most value
Apple and Google Wallet passes are especially useful when the customer needs at least one of three things:
Fast access: The credential must be found and presented quickly, as with event tickets and access passes.
Repeated use: The customer returns to the same card, as with loyalty, membership and punch cards.
Changing information: Details may need to be updated after issuance, such as points, status, timing, seating or validity.
They are less useful when the information is unlikely to be needed again or when the process requires extensive functionality better suited to a website or application.
A wallet pass should not be treated as a miniature app. Its advantage is precisely that it is focused.
The operational challenge behind wallet passes
The customer sees a simple card. The issuer still needs to manage designs, wallet-specific formats, individual pass data, distribution links, updates, barcodes, security, scanning and integrations.
This is where a wallet-pass platform such as Passlet becomes useful.
Passlet lets organizations design templates for Apple Wallet and Google Wallet, issue personalized passes individually, from CSV files or through a REST API, and distribute them using add-to-wallet links. Issued passes can be updated remotely and validated using Passlet’s Scanner app or an existing integration.
For a small event, that may mean designing tickets in a dashboard, importing an attendee list and emailing each attendee a wallet link.
For a larger loyalty or membership system, Passlet can connect to an existing CRM, checkout, website or internal platform. Its API supports automated issuance, updates and scanning, while webhooks communicate pass lifecycle and redemption events back to other systems.
The important point is not the technology itself. It is that businesses can offer a native wallet experience without building and maintaining separate Apple Wallet and Google Wallet infrastructure from scratch.
A practical wallet-pass strategy
A successful implementation starts with the customer journey rather than the visual design.
First, identify the moment where customers currently experience friction. That may be finding a ticket, proving membership, remembering a reward or receiving updated information.
Next, decide what the pass must communicate at a glance. Keep the front focused on the information needed at the point of use. Place secondary instructions and links in the pass details.
Finally, determine what should happen after issuance. Consider whether the pass needs to be updated, scanned, redeemed once, used repeatedly or connected to another system.
A good pass answers three immediate questions:
- What is this?
- When or where can I use it?
- What do I do next?
Everything else is secondary.
Wallet passes turn transactions into ongoing experiences
Customer satisfaction is rarely transformed by one spectacular feature. It is built through small moments that consistently work as expected.
The ticket is easy to find. The loyalty balance is current. The updated information arrives before it causes confusion. Entry takes seconds. The reward can actually be redeemed.
Apple Wallet and Google Wallet passes improve these moments by placing useful, current information in a familiar and immediately accessible location.
For businesses, that creates an opportunity to remain present after the initial transaction without demanding another app download or forcing customers through another account portal.
For customers, it simply feels easier.
And ease is one of the strongest foundations for satisfaction, repeat usage and long-term retention.
Frequently asked questions
How do I integrate Passlet with my existing systems?
Passlet exposes a public REST API so that it can be integrated seamlessly into any CRM, loyalty program platform, or other systems. Should you need help integrating Passlet or don't have any developer experience, we are happy to help. Shoot us a message!
How do wallet passes improve customer retention?
Wallet passes make loyalty benefits, memberships and repeat-use credentials easier to access than a traditional app ecosystem. They can also stay updated, helping businesses provide a more consistent experience after the initial purchase.
Can wallet passes be updated after customers install them?
Yes. Properly configured Apple Wallet and Google Wallet passes can receive updated information after issuance. Supported updates vary by wallet and pass type.
Do customers need to download a separate app?
Generally, no separate brand application is required. Customers add the pass to the wallet already available on their phone using an add-to-wallet link or button.
What can businesses create with Passlet?
Passlet supports Apple Wallet and Google Wallet event tickets, loyalty and punch cards, memberships, vouchers, day passes and access credentials. Passes can be designed, issued, distributed, updated and scanned from a dashboard or through an API.
