Account Restricted Passes
What are Account Restricted Passes?
A new feature that lets developers associate some pass objects with Google accounts which limits
who can save the pass.
How does it work?
You set the user's email address on the pass object using the Google Wallet API. When the user
attempts to save that pass to Google Wallet, we validate that the account set on the pass object
matches the Google Account of the Google Wallet user saving the pass.
That sounds great! How do I get access to this feature?
We’re testing the feature with a small number of developers. If you are interested,
contact support
in the Google Pay & Wallet Console and
file a support case under Topic: “Google Wallet API Integration”, Subtopic: “Other”
and include in the issue description: “Account Restricted Passes Access Request”.
We’ll let you know when you can access it.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-02-07 UTC.
[null,null,["Last updated 2025-02-07 UTC."],[[["Account Restricted Passes are a new feature allowing developers to link specific pass objects to Google accounts, controlling who can save them."],["This feature functions by validating the Google Account of the user saving the pass against the account associated with the pass object via the Google Wallet API."],["Currently, access to Account Restricted Passes is limited to select developers, and interested parties can request access through Google Pay & Wallet Console support."]]],[]]
