Stay organized with collections
Save and categorize content based on your preferences.
Pass Issuer
The Passes issuer is the entity that owns the pass and is responsible for issuing passes to their customers. This could
be you, the developer, or the organization that you represent.
In order to become a Passes Issuer, you must first register as an Issuer.
event ticket class
A EventClass can be thought of as scheduled event. An issuer may create multiple scheduled events with permutation of event names and timings.
Each EventClass representing a scheduled event may contain its own appearance and data fields to meet the venue-specific requirements.
In addition, EventClass can also be used to enable additional features like Smart Tap.
event ticket object
A event ticket object is an instance of a EventClass. A new EventObject instance should be created for each customer
that is distributed with a event ticket.
Pass Class
A EventClass is a type of Pass Class. Pass Classes describe general information for related Pass Objects (such as
style and appearance), and do not include customer details.
Pass Object
A EventObject is a type of Pass Object. Like EventObjects, a Pass Object is an instance of a corresponding Pass
Class. A Pass Object should be created for each customer that is issued a event ticket.
Pass Objects contains customer-specific information. For example, it can be used to identify that a customer not only
has a ticket for a event, but also identify which seat on the event they’ve been allotted.
Service account
The service account is the identity that is used to call the Google Wallet API. Permission to access the Passes API should be
granted to this service account.
Service account key
The service account key is the credential used to authenticate your application as the service account. The service
account key should be considered highly sensitive and kept private. If a third party has access to the service account
key, they will be able to identify themselves as the service account and perform actions that the service account is
permitted to perform.
[[["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-09-04 UTC."],[[["\u003cp\u003eThe Passes issuer is the entity responsible for creating and distributing passes to customers, requiring prior registration.\u003c/p\u003e\n"],["\u003cp\u003eEvent Ticket Classes represent scheduled events, enabling customization for venue needs and features like Smart Tap.\u003c/p\u003e\n"],["\u003cp\u003eEvent Ticket Objects are individual instances of Event Ticket Classes, issued to each customer with specific ticket details.\u003c/p\u003e\n"],["\u003cp\u003ePass Objects and Classes function similarly, with Objects storing customer-specific information like seat assignments.\u003c/p\u003e\n"],["\u003cp\u003eA Service Account and its Key are essential for authenticating your application with the Google Wallet API and should be kept secure.\u003c/p\u003e\n"]]],["An Issuer, after registering, creates `EventClass` instances for scheduled events, defining their appearance and data. For each customer, an `EventObject` is generated as an instance of the `EventClass`, containing customer-specific details like seat allocation. `EventClass` is a type of Pass Class, and `EventObject` a Pass Object. A service account, granted access to the Passes API, is used to call the API, and a sensitive service account key authenticates applications as the service account.\n"],null,["# Key concepts and terminology\n\nPass Issuer\n-----------\n\nThe Passes issuer is the entity that owns the pass and is responsible for issuing passes to their customers. This could\nbe you, the developer, or the organization that you represent.\n\nIn order to become a Passes Issuer, you must first register as an Issuer.\n\nevent ticket class\n------------------\n\nA `EventClass` can be thought of as scheduled event. An issuer may create multiple scheduled events with permutation of event names and timings.\nEach `EventClass` representing a scheduled event may contain its own appearance and data fields to meet the venue-specific requirements.\n\nIn addition, `EventClass` can also be used to enable additional features like Smart Tap.\n\nevent ticket object\n-------------------\n\nA event ticket object is an instance of a `EventClass`. A new `EventObject` instance should be created for each customer\nthat is distributed with a event ticket.\n\nPass Class\n----------\n\nA `EventClass` is a type of Pass Class. Pass Classes describe general information for related Pass Objects (such as\nstyle and appearance), and do not include customer details.\n\nPass Object\n-----------\n\nA `EventObject` is a type of Pass Object. Like `EventObjects`, a Pass Object is an instance of a corresponding Pass\nClass. A Pass Object should be created for each customer that is issued a event ticket.\n\nPass Objects contains customer-specific information. For example, it can be used to identify that a customer not only\nhas a ticket for a event, but also identify which seat on the event they've been allotted.\n\nService account\n---------------\n\nThe service account is the identity that is used to call the Google Wallet API. Permission to access the Passes API should be\ngranted to this service account.\n\nService account key\n-------------------\n\nThe service account key is the credential used to authenticate your application as the service account. The service\naccount key should be considered highly sensitive and kept private. If a third party has access to the service account\nkey, they will be able to identify themselves as the service account and perform actions that the service account is\npermitted to perform."]]
