Mobile Wallet Loyalty: Apple Wallet, Google Wallet, and the Cardless Future

Mobile Wallet Loyalty: Apple Wallet, Google Wallet, and the Death of the Physical Loyalty Card

The physical loyalty card is not dead yet — but it is dying faster than most loyalty program managers have built a plan for. In 2026, 91% of 18-to-26 year olds use digital wallets as their primary payment method. The average US consumer is enrolled in over 15 loyalty programs, up nearly 10% since 2022, while engagement with those programs has dropped 10% over the same period. The loyalty program that still exists primarily as a plastic card, a barcode on a printed receipt, or a portal login is competing for attention in a customer's physical wallet against a habit that most of those customers have already abandoned — and it is losing.

The mobile wallet is not just a digital replacement for the plastic card. It is a fundamentally different loyalty channel. Apple Wallet and Google Wallet passes are persistent — they sit on the device lock screen, surfacing automatically when members are near relevant locations. They are dynamic — points balances, tier status, and available offers update in real time without requiring the member to open an app or log into a portal. They are a direct communication channel — push notifications delivered through wallet passes arrive on the lock screen with near-perfect delivery rates, competing with neither the email inbox clutter nor the app notification fatigue that undermine other loyalty communication channels. And they require no dedicated app download, which removes the single biggest adoption friction point that loyalty programs face with new members.

This article is the practical guide for loyalty program marketers who need to understand what wallet-based loyalty actually involves, how Apple Wallet and Google Wallet passes work technically (without requiring an engineering background), what capabilities the channels unlock for communication and engagement, and what the integration requirements are for connecting wallet passes to existing loyalty platform infrastructure. It is written for the loyalty director or CRM manager who does not have a dedicated engineering team and who needs to understand what is genuinely possible, what requires development resources, and where the third-party platform options fill the gap.

Why Physical Cards Are Dying — and What Is Replacing Them

The physical loyalty card's decline is not driven by consumer disaffection with loyalty programs — it is driven by a fundamental mismatch between where consumers live (their smartphones) and where most loyalty programs currently exist (a physical card in a wallet that never gets opened, or a portal login that requires a remembered password). The friction this creates is commercially significant: 70% of loyalty members are unsure of their points balance even though 93% say they would purchase more often if they received better communication about their rewards. A loyalty program that is invisible between purchase occasions is not building loyalty — it is subsidizing transactions.

The Gen Z data accelerates the urgency. Among the Antavo GCLR 2026 data, Gen Z shows significantly lower attachment to plastic cards (26.5% vs. a global average of 41%), while 43.5% prefer to manage loyalty through a mobile app and 33% over-index on providing phone numbers or email at checkout — signaling comfort with digital identification and instant digital enrollment. The loyalty program that builds its engagement strategy around physical cards is engineering itself into irrelevance with the demographic whose spending power is growing fastest over the next decade.

The replacement is not a dedicated loyalty app — that model has its own adoption problem. The average loyalty app achieves single-digit adoption among enrolled members, because downloading an app is a significant friction barrier that most members will not overcome unless the program's value is immediately obvious. The mobile wallet pass bypasses this barrier entirely: the member already has Apple Wallet or Google Wallet on their device, and adding a loyalty pass takes one tap from an email, SMS, QR code, or website button. No download required. No login required. The card is simply there, the next time they open their wallet.

How Wallet Passes Work: The Technical Basics Without the Engineering Jargon

Understanding the technical mechanics of wallet passes does not require a development background — but it does require a working mental model of what a pass is, where it lives, and how it stays current.

What a Wallet Pass Actually Is

A wallet pass is a structured digital file — think of it as a specially formatted document that Apple Wallet and Google Wallet know how to display, store, and update. For Apple Wallet, these are called PKPasses, generated through Apple's PassKit framework. For Google Wallet, they are called Pass Objects, created through the Google Wallet Objects API. Both are essentially a package of data — the member's name, loyalty ID, points balance, tier status, a barcode or QR code for scanning, and branding assets — wrapped in a format that the respective wallet application can parse and display as a branded card.

The member never sees the underlying file. They see a branded card in their wallet with their loyalty information displayed in the layout the brand has defined. When the brand's system sends an update — a new points balance after a purchase, a tier upgrade, an expiring reward — the pass refreshes automatically. The member sees the current information the next time they open their wallet. The update happens silently, in the background, without any action required from the member.

Apple Wallet: PassKit Framework

Apple Wallet passes are generated through Apple's PassKit framework, which requires the brand (or their technology partner) to hold an Apple Developer account, a valid Pass Type ID certificate, and a signing key. These credentials are used to generate signed PKPass files that Apple's system trusts. In practice, very few loyalty program teams generate passes directly through PassKit — the process requires code-level implementation — but dozens of SaaS platforms (PassKit, Badge, Stell, Passtastic, and others) abstract this complexity into a no-code or low-code interface that allows marketers to design, issue, and update passes without writing code.

Key Apple Wallet capabilities for loyalty: passes can display up to five fields of dynamic data (points balance, tier status, expiration, recent activity, and a promotional message are typical); passes support a single push notification channel tied to the pass; geofencing allows up to ten store locations per pass, which trigger a lock screen notification when the member enters the defined radius; and passes support both barcode and NFC redemption at point of sale.

Google Wallet: Wallet Objects API

Google Wallet passes (formerly part of Google Pay) use the Wallet Objects API to create digital passes that live in the Google Wallet app on Android devices. The structure uses a Class (the template defining the brand's pass design and default values) and an Object (the individual member instance with their specific data). Updating a pass requires an API call that patches the Object — points balance, tier level, and field values update across all existing passes without re-issuance.

Google has been actively expanding wallet pass capabilities in 2025 and 2026. Key 2025 updates relevant to loyalty programs include: expanded Nearby Passes Geofence Notifications covering all standard pass types (up to 10 merchant locations per category), triggering lock screen notifications when members enter the defined radius; email ingestion integration that automatically adds loyalty passes to Wallet from Gmail when Smart Features are enabled; and the 'Bounceback' pilot program that enables post-payment enrollment prompts — when a customer taps to pay at a participating merchant, they see an immediate prompt to enroll in the loyalty program, converting the payment moment into an enrollment moment.

The Fundamental Difference From App-Based Loyalty

The critical difference between wallet-based and app-based loyalty is the activation requirement. A loyalty app requires the member to: discover the app, navigate to the app store, download it, install it, create or log into an account, grant notification permissions, and remember to open it between visits. Each step is a dropout opportunity; most loyalty programs that have measured this funnel find that fewer than 15% of enrolled members complete all steps and become active app users.

A wallet pass requires one action: tap 'Add to Wallet' from an email, SMS link, QR code, or website button. The pass installs instantly. Notification permissions are often already granted for the wallet application. The member sees the pass the next time they open their wallet to pay for anything — not just at your store. The persistent visibility this creates across all payment occasions is the core commercial advantage of wallet-based loyalty.

Push Notifications Through Wallet Passes: Best Practices and Limits

Push notifications delivered through wallet passes are the channel's most commercially valuable feature and its most misused one. The commercial data is compelling: 48% of shoppers have made a purchase as a result of receiving a push notification, and 71% of 18-to-34 year olds specifically say they see value in receiving loyalty offer notifications through wallet passes. The channel's near-perfect delivery rate — notifications arrive on the lock screen regardless of whether the member has the wallet app open, and do not compete with email inbox volume — makes it significantly more reliable for time-sensitive loyalty communication than email.

What Wallet Push Notifications Can Deliver

Wallet push notifications can trigger on: points balance updates after a qualifying purchase (confirming the earn and showing the new balance); tier advancement notifications (congratulating the member and showing the new benefits); reward expiration reminders (alerting members that an earned reward is approaching expiration); time-sensitive promotional offers (a bonus event window, an exclusive product drop, a flash redemption opportunity); and re-engagement triggers (a notification to a member who has not visited in a defined period, referencing their current balance).

The Notification Discipline Rule

The most common mistake loyalty program managers make with wallet push notifications is treating them like an email blast channel — sending notifications for every minor event regardless of relevance or timing. Wallet push notifications that feel promotional rather than informational, arrive at inconvenient times, or communicate things the member does not need to know will be turned off. Once a member disables notifications for a pass, they cannot be re-enabled by the brand — the member must manually re-enable them. The engagement window that makes wallet notifications valuable depends on keeping that notification permission active.

The operating principle: send push notifications when the member needs to know something right now. A points confirmation immediately after a transaction, a reward expiration warning 48 hours before an offer expires, a tier upgrade notification in the moment it triggers, a geofence notification when the member is near the store with a current offer — these are communications the member values receiving in real time. A weekly points balance summary, a general promotional announcement, or a notification that there is 'a new offer in your wallet' that requires opening the pass to discover is the kind of communication that erodes the channel's value.

Geofencing: The Location-Triggered Notification

Geofencing is the capability to define a geographic radius around specific locations — store addresses, event venues, competitor locations — and trigger a push notification when a member with an installed pass enters that radius. The notification appears on the lock screen without any action from the member; it is triggered by the device's location services processing the defined geofence boundary.

The commercial use cases for loyalty geofencing are substantial: alerting members to a current in-store offer when they are within walking distance; triggering a visit incentive when a member who has not visited recently passes near the store; sending a competitive counter-offer when a member enters a competitor location's geofence. Google Wallet's October 2025 update extended Nearby Passes Geofence Notifications to all standard pass types at up to 10 merchant locations per pass category, making this capability more accessible than it has previously been.

The limit: Apple Wallet allows up to 10 geofence locations per pass. Google Wallet allows up to 10 locations per pass category. For retail brands with hundreds or thousands of store locations, this means geofencing applies only to the 10 most commercially relevant locations per member — typically the member's nearest stores or their most frequently visited locations, identified through purchase history.

Loyalty Platform Integration: What Your Existing Stack Needs to Support

Wallet passes are a channel layer that sits on top of an existing loyalty platform, not a replacement for it. The wallet pass displays data that lives in the loyalty platform — points balances, tier status, expiration dates, promotional offers — and must be kept current as that data changes. This creates an integration requirement between the loyalty platform (the system of record for member data) and the pass management layer (the system that issues and updates passes).

The Minimum Integration Requirements

A loyalty platform that can support wallet-based passes needs to expose the following data and events via API or webhook: member enrollment events (triggering pass issuance when a new member joins the program); points balance updates (triggering a pass field update when a transaction posts to the member's account); tier changes (triggering a pass update when a member advances or drops tiers); reward expiration (triggering a push notification when an earned reward approaches expiration); and promotional offer changes (updating the offer field on the pass when new promotions become active for a member).

In practice, most modern loyalty platforms support these data outputs through webhooks — event-driven signals that fire when specific member events occur and that can be consumed by a pass management platform to trigger the appropriate update. The technical configuration requires either a developer resource to build the webhook integration or the use of a pass management platform that offers native connectors to common loyalty platforms.

Pass Management Platforms: What They Do

For loyalty program teams without dedicated engineering resources, pass management platforms (PassKit, Badge, Stell, Passtastic, and similar) handle the complexity of Apple PassKit certificate management and Google Wallet API authentication, leaving the marketing team responsible only for pass design, distribution, and communication strategy. These platforms typically offer: a visual pass designer that produces Apple- and Google-compliant pass templates; an API for issuing individual passes when members enroll; a dashboard for managing the installed pass base; push notification tools for sending targeted communications; and geofencing configuration interfaces.

The integration point between the loyalty platform and the pass management platform is the member data feed: when a member earns points, the loyalty platform should trigger an update to the pass management platform, which then updates the pass and sends the confirmation notification. Most pass management platforms support this via inbound webhook or API call.

Designing Wallet Passes for Maximum Engagement

Wallet pass design is constrained by the display rules of each platform — Apple and Google both define which fields appear, how many characters are supported, and what layout options are available. Within those constraints, design decisions significantly affect engagement.

The Fields That Drive Behavior

Both Apple Wallet and Google Wallet passes support a primary field (the most prominent data point, typically points balance or available reward), secondary fields (tier status, expiration date, or promotional message), and an auxiliary or back-of-pass section for additional program information. The primary field should show the member's most actionable current status — not their membership number or their join date, but the number they need to understand what they can do right now. 'You have 2,340 points — redeem for $23 off' is more engagement-driving than '2,340 points' because it translates the balance into immediate value.

The promotional field — typically displayed below the primary loyalty information — is the pass's dynamic content opportunity: the offer or message that changes based on current promotions, member status, or behavioral triggers. This field should be updated whenever there is something materially new to tell the member — a current bonus event, an approaching expiration, a personalized recommendation based on purchase history. A pass with a promotional field that never changes is a pass that stops driving behavior.

Barcode vs. NFC: Redemption Technology Choice

Wallet passes support both barcode/QR code redemption (the barcode is displayed on the pass face and scanned at point of sale) and NFC redemption (the member taps their phone to an NFC reader, which reads the pass directly without requiring the screen to be unlocked). The choice between them is primarily driven by the point-of-sale infrastructure the brand's stores or partners support. Barcode redemption is universally supported by standard barcode scanners; NFC requires compatible readers and typically an integration between the wallet pass and the payment terminal. For most loyalty programs without full NFC POS infrastructure, barcode/QR redemption is the practical starting point.

Distribution: How Members Get Their Passes

Members add wallet passes through one of four distribution methods: a link in a post-enrollment email or SMS; a QR code displayed in-store, on packaging, or on a receipt; a website button on the loyalty enrollment page; or NFC tap enrollment (the member taps their phone to an NFC tag at the store, which opens the pass enrollment flow). Google's email ingestion integration (launched in 2025) adds a fifth method for Android users: when a loyalty pass invitation email arrives in Gmail with Smart Features enabled, Google automatically prompts the user to add the pass to their Wallet without the user needing to tap through any link.

The distribution method affects enrollment conversion rate. Email links typically achieve 15–25% open-to-add conversion; QR codes at POS typically achieve 5–15% conversion from scan-to-add; website buttons embedded in the post-enrollment confirmation flow achieve the highest conversion (50–70%) because the member's intent to join the program is already established. Post-payment enrollment through Google's Bounceback pilot represents the most commercially interesting emerging distribution channel — capturing enrollment at the exact moment of transaction, when the member's intent to engage with the brand is at its peak.

Conclusion

The mobile wallet has become the most direct, persistent communication channel a loyalty program can occupy — and most loyalty programs are not yet there. A digital pass that lives on the member's lock screen, updates their balance in real time after every qualifying transaction, surfaces automatically when they walk past the store, and delivers time-sensitive notifications without competing for inbox attention is not a feature upgrade to a loyalty program. It is a structural improvement in how the program communicates with its members at every touchpoint between purchase occasions.

The practical barrier to implementing wallet-based loyalty is lower than most loyalty teams assume. Pass management platforms have abstracted the technical complexity of Apple PassKit and Google Wallet API into accessible interfaces that do not require dedicated engineering teams. The integration requirement — connecting the loyalty platform's member events to the pass management layer — is achievable with standard webhook connections that most modern loyalty platforms support. The primary investment is program design: deciding what the pass communicates, when to send notifications, which locations to geofence, and how to embed wallet enrollment into the existing member journey.

The programs that move to wallet-native delivery first will have a sustained engagement advantage: members who carry a brand's pass see it every time they open their wallet, and that persistent visibility compounds over time into the habit of engagement that physical cards never generated and dedicated apps rarely achieved.