Stay organized with collections
Save and categorize content based on your preferences.
Some passes that you can create with Google Wallet may contain sensitive user data. These passes have extra protection to help keep your users data safe and are managed differently in the Wallet API. The generic private pass vertical should be used in cases where sensitive data (as defined in the Wallet API Acceptable Use Policy) is included in your Pass.
The generic private pass vertical supports use cases such as:
Health Insurance Cards
National Identification Cards
Other Government IDs
Some countries and jurisdictions require that sensitive data is managed in a particular way. As such, the list of use cases highlighted here may vary depending on your country or other regulations. If your user data is subject to legal regulation in your country of origin (e.g. the Health Insurance Portability and Accountability Act in the United States), it will have to use the generic private pass vertical and may be subject to additional review.
What is different?
Generic private passes use a self-contained method for defining and distributing the pass. As the developer, you define the pass layout and contents in a single JSON Web Token that is then distributed directly to the user for them to save it into their Wallet.
Passes which process sensitive data (known as generic private pass) may be subject to additional privacy controls during onboarding. We do not allow the APIs to be used for processing sensitive data in Google Wallet without explicit permission from Google, as described in the as defined in the Wallet API Acceptable Use Policy.
Request access
If your pass contains sensitive data, contact support in the Google Pay and Wallet Console and request for access. If you are unsure if your pass contains sensitive data, please contact support.
You will be required to provide the following:
Eligibility Document verifying your identity and attesting you are a valid entity
A URL to your logo
A URL to your website
Get started
After you have received approval to issue generic private pass, get started with your implementation to add passes to Google Wallet.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-02-20 UTC."],[[["Google Wallet has extra protection for passes containing sensitive user data, like health insurance or national ID cards, using the generic private pass vertical."],["These passes are managed differently, requiring developers to define the layout and contents in a JSON Web Token distributed directly to the user."],["Using the Google Wallet APIs for sensitive data requires explicit permission from Google and may involve additional privacy controls during onboarding."],["Developers must request access through Google Pay and Wallet Console support and provide verification documents to be eligible to issue generic private passes."],["After approval, developers can begin implementation by referring to the provided 'Get started' resources."]]],["Generic private passes, designed for sensitive user data like health insurance or national IDs, require a specific approach within Google Wallet. Developers define the pass layout and content in a JSON Web Token distributed directly to the user. Access to create these passes is restricted and requires explicit permission from Google. To request access, submit an eligibility document, logo URL, and website URL via the Google Pay and Wallet Console. Once approved, developers can implement the pass using the provided guidelines. Passes that use private information may be subject to additional privacy controls.\n"]]
