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
EventClass can be thought of as scheduled event. An issuer may create multiple scheduled events with permutation of event names and timings.
EventClass representing a scheduled event may contain its own appearance and data fields to meet the venue-specific requirements.
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.
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.
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.
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.