How passes in Google Wallet work
Unlike the pkpass format used by Apple Wallet, Google Wallet cards function fundamentally differently on a technical level. Instead of storing a file within the app, Google Wallet - except for the Generic Private Pass format - is based on a server-based service. This means the primary difference is that the card definition in Google Wallet is stored on a Google cloud service.
As a Pass Service Provider, Passcreator uses the Google Wallet API to generate the cards and provide them for download. When you click the “Add to Google Wallet” button, the card is linked to your Google account and synchronized across all your devices. Updates and push notifications are also managed via the Google Wallet API.
What are Google Wallet passes?
Google Wallet cards are digital representations of physical cards or documents that can be stored on Android devices. Unlike Apple Wallet, which uses the pkpass format, Google Wallet is based on a flexible JSON format that is created via an API.
The cards are divided into different types, including::
- Loyalty Cards - e.g., customer cards
- Gift Cards
- Event Tickets - e.g., concert or sports tickets
- Boarding Passes - for air travel
- IDs & Membership Cards - e.g., student IDs, club memberships
How do Google Wallet passes work?
Google Wallet cards consist of structured data defined using a JSON structure. This is created and managed via the Google Wallet API. Businesses can provide cards either through direct integration into their app or via a generated "Add to Google Wallet" button.
The basic process is as follows:
- Registration with Google - Businesses must register to use the Google Wallet API.
- Creating the card structure - The provider defines the layout and content in a JSON file.
- Distributing the cards - Users receive cards via email, websites, apps, or QR codes.
- Storing in Google Wallet - Users add the card with a single click and have it readily available.
Technical Fundamentals of Google Wallet passes
- JSON Format: All Google Wallet passes are defined as JSON objects.
- API-Based Creation: Cards are generated via the Google Wallet API.
- Cloud Synchronization: Passes are synced through the user’s Google account and can be accessed on multiple devices.
- Dynamic Updates: Pass content can be updated later without requiring the user to add a new card. Push notifications can also be sent.
- Barcode Support: Google Wallet cards support QR codes, barcodes, and NFC for contactless interactions.
Distribution of Google Wallet passes
Google Wallet cards can be distributed via URLs in the browser or on websites. Users click on an "Add to Google Wallet" button, which contains a JSON Web Token (JWT). This token either includes the card data itself or a reference to an existing card.
A JWT always contains a cryptographic signature to ensure that the data cannot be tampered with.
Why Are Google Wallet Cards Convenient?
Google Wallet passes provide a flexible and modern solution for digital cards. Thanks to API-based creation and cloud-based management, businesses can update their cards at any time and enhance them with additional features. For users, this means a convenient and secure way to keep their essential cards readily available - directly on their Android device.
Google Wallet is also the most widely used wallet app on Android worldwide, making it the de facto standard for wallet cards on Android.
With Passcreator, you can easily create digital passes without dealing with technical complexities. Our no-code editor for wallet passes is available instantly - try it for free and create your first Google Wallet card in no time!