重要概念和術語
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
票證核發者
「票證核發機構」是擁有票證的實體，負責將票證核發給客戶。這可以是您、開發人員或您代表的機構。
如要成為票證核發者，您必須先註冊為核發者。
活動票券類別
EventClass 可視為已排定的活動。核發機構可以建立多個已排定活動，且這些活動的名稱和時間排列組合。代表已排定活動的每個 EventClass，都可包含自身的外觀和資料欄位，以符合場地特有的規定。
此外，EventClass 也能用來啟用智慧感應等功能。
活動票券物件
活動票券物件是 EventClass 的執行個體。請為每個與活動票券發布的客戶建立新的 EventObject 執行個體。
票證類別
EventClass 是一種票證類別。票證類別會說明相關票證物件的一般資訊 (例如樣式和外觀)，但不包括客戶詳細資料。
傳遞物件
EventObject 是一種票證物件類型。和 EventObjects 一樣，票證物件是對應票證類別的執行個體。您必須為核發活動票券的客戶建立「票證物件」。
「傳遞物件」包含客戶專屬的資訊。舉例來說，此標記可用來識別客戶不僅有活動票券，也能識別所分配活動的座位。
服務帳戶
服務帳戶即為呼叫 Google Wallet API 的身分。您應將存取 Pass API 的權限授予這個服務帳戶。
服務帳戶金鑰
服務帳戶金鑰是用來以服務帳戶的形式驗證應用程式的憑證。服務帳戶金鑰應視為高度機密，且不會外洩。如果第三方有權存取服務帳戶金鑰，他們便能將自己視為服務帳戶，並執行該服務帳戶允許的動作。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-08-29 (世界標準時間)。
[null,null,["上次更新時間：2025-08-29 (世界標準時間)。"],[[["\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."]]
