What Is a Google Wallet Pass? How Digital Passes Work on Android

A Google Wallet pass is a digital card hosted on Google's servers and displayed inside the Google Wallet app on Android devices. Loyalty cards, event tickets, membership cards, coupons and boarding passes all live here — accessible from the home screen or lock screen without opening a separate app. For businesses, Google Wallet is the Android equivalent of Apple Wallet: a direct, persistent channel to your customer's device.

With 94% of smartphones globally shipping with NFC capabilities, and Google Wallet expanding to 50+ new countries in 2025, the addressable audience for wallet passes has never been larger. Understanding how Google's pass model works is the first step to taking advantage of it.

The Issuer Model: Classes and Objects

Google Wallet uses a REST API-first architecture that differs meaningfully from Apple's file-based model. Where Apple has you create a .pkpass bundle for each individual pass, Google separates the concept of a pass into two layers.

A pass class (sometimes called an "issuer class") defines the template: your branding, the layout, the fields you want to display, and any default values. Think of it as the mould. You create one pass class per programme — one for your loyalty scheme, one for your event series, one for your membership tiers.

A pass object is a specific instance of that class, created for an individual customer. It inherits the template from the class but carries customer-specific data: their name, points balance, member number, ticket row and seat. You create one pass object per customer per programme.

This two-layer model makes bulk operations clean. If you want to update branding across all 50,000 loyalty cards, you update the class once. If you want to update a single customer's points balance, you PATCH their object.

Key Pass Types in Google Wallet

Google Wallet supports five principal pass types, each with a defined schema.

Loyalty passes — the primary type for retail and hospitality. Displays points balance, tier name, rewards programme name and a barcode for in-store scanning. The loyalty object includes fields for programme logo, hero image and account details.

Event tickets — event name, date, time, venue, seat and a QR code or barcode for admission scanning. Google surfaces these on the lock screen in the hours before the event, mirroring Apple's time-based relevance behaviour.

Boarding passes — flight number, departure and arrival, seat, gate and boarding time. Used by airlines and transit operators.

Offers — promotional content with a redemption code, offer title and expiry. Equivalent to Apple's coupon type.

Generic passes — the most flexible type. A catch-all for membership cards, gift cards and any pass that doesn't fit the structured types above. Google's generic pass supports a header, a hero image, a barcode and several text fields, giving designers considerable latitude.

How a Customer Saves a Google Wallet Pass

The distribution mechanism for Google Wallet passes is a JWT-signed "Save to Google Wallet" URL. Here is the flow: you create a pass object via the Google Wallet API, sign a JSON Web Token containing a reference to that object, and append the JWT to a standard Save to Google Wallet URL. The customer taps the link or button, Google validates the JWT, and the pass is saved to their wallet.

You can surface this link in several ways: as a button on a web page, inside a transactional email, as a QR code on a printed receipt, or triggered automatically after a purchase in your app. The customer never needs to create a Google account during the save flow — if they're already signed into their Android device, the pass saves in one tap.

Live Updates: Real-Time Pass Changes

One of Google Wallet's most powerful capabilities is real-time pass updates. Because passes are server-hosted objects rather than files on the device, you can modify a pass object via the API and the change propagates to every device that has saved that pass — instantly.

Update a customer's loyalty points after a purchase, change an event venue two days before the show, or activate a personalised discount for a lapsed member. The customer sees the updated pass without doing anything.

Alongside data updates, Google Wallet supports the addMessageRequest — a push notification delivered directly to the pass, appearing on the lock screen. Wallet push notifications see open rates of around 69%, compared to roughly 20% for marketing email. That gap is the commercial case for investing in wallet distribution.

Google Wallet's Global Expansion

Google Wallet launched its NFC payment capability in the US and quickly expanded across Western Europe. In 2025, Google announced availability in 50+ additional countries, making it a genuinely global distribution channel for the first time. For businesses operating across multiple markets — or planning to — this expansion removes the previous constraint of building separate distribution strategies for different regions.

Pair this with the fact that Android holds a global majority of smartphone market share and the scale of the Google Wallet channel becomes clear. A single loyalty programme distributed via Google Wallet and Apple Wallet together covers virtually the entire smartphone-carrying population of your customer base.

The Technical Overhead of Doing It Yourself

Issuing Google Wallet passes without a platform requires authenticating with the Google Wallet API via a service account, creating and managing issuer accounts, building the pass class creation workflow, generating and signing JWTs for each pass object, handling the PATCH API calls for updates, and managing the addMessageRequest flow for push notifications. Each step is documented, but the engineering effort adds up quickly.

The service account credentials need secure storage, key rotation and monitoring. The JWT signing logic needs to be correct — a malformed token results in a failed save for the customer. And the update pipeline needs to be reliable: a failed PATCH means a customer sees stale data.

How Issuepass Handles Google Wallet for You

We abstract the entire Google Wallet API behind a straightforward interface. Design your pass template in our editor, define your data fields, and import your customer list. We create the pass classes, generate the pass objects, sign the JWTs and produce the "Save to Google Wallet" links — all without you touching the API directly.

When you update a customer's data — via our dashboard or through the Issuepass API — we PATCH the corresponding Google Wallet object immediately. Push a notification through our campaign tool and we handle the addMessageRequest delivery. Everything is managed in one place, covering both Apple Wallet and Google Wallet from a single template.

Start free and issue your first Google Wallet pass today — no API credentials or service accounts required.