重要概念和術語
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
票證核發機構
票證核發機構必須為票證的擁有者，且必須核發票證給客戶。這可以是您、開發人員或您代表的機構。
如要成為票證核發者，您必須先註冊為核發者。
會員類別
會員類別可視為會員方案。發卡機構可以建立多項會員方案 (例如「Standard」和「Premium」)，每種計畫都有各自的獨特風格和外觀。
除了樣式和外觀外，會員類別也可以用來啟用智慧感應、註冊和登入等其他功能。
會員物件
會員物件是會員類別的例項。為已註冊會員方案的每位客戶建立新的 Loyalty Object 例項。
票證類別
會員類別是一種票證類別。票證類別會說明相關票證物件的一般資訊 (例如樣式和外觀)，其中不包括客戶詳細資料。
其他類型的票證類別包括：
- 登機證
- 活動票券
- 禮物卡
- 優惠
- 大眾運輸票證
- 疫苗接種記錄卡
傳遞物件
會員物件是一種「票證」物件。與會員物件一樣，票證物件是對應票證類別的例項。為持有票證的每位客戶建立票證物件。
「傳遞物件」包含客戶專屬的資訊。舉例來說，此標記可用來識別客戶不只具備某段航班的票券，還能找出您已分配的航班座位。
服務帳戶
服務帳戶是呼叫 Google Wallet API 的身分，請務必將 Google Wallet API 的存取權授予這個服務帳戶。
服務帳戶金鑰
服務帳戶金鑰是用來以服務帳戶的形式驗證應用程式的憑證。服務帳戶金鑰的機密性極高，因此不得不對外公開。如果第三方有權存取服務帳戶金鑰，就可以將自己視為服務帳戶，並執行該服務帳戶允許執行的操作。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-08-29 (世界標準時間)。
[null,null,["上次更新時間：2025-08-29 (世界標準時間)。"],[[["\u003cp\u003eThe pass issuer, who can be you or your organization, must register and issue passes to customers.\u003c/p\u003e\n"],["\u003cp\u003eLoyalty programs are represented by Loyalty Classes, which define style, appearance, and features like Smart Tap.\u003c/p\u003e\n"],["\u003cp\u003eA Loyalty Object is created for each customer enrolled in a loyalty program, and it's an instance of a Loyalty Class, which is a type of Pass Class.\u003c/p\u003e\n"],["\u003cp\u003ePass Objects store customer-specific information and are instances of Pass Classes, which can represent various types like boarding passes, event tickets, and gift cards.\u003c/p\u003e\n"],["\u003cp\u003eA service account with a securely stored key is used to authenticate your application with the Google Wallet API.\u003c/p\u003e\n"]]],["Passes issuers register to create loyalty programs (Loyalty Classes) with unique styles and features. Each customer enrolled gets a Loyalty Object, an instance of the Loyalty Class. Pass Classes, including Loyalty Classes, define general pass details. Each customer receives a Pass Object, an instance of a Pass Class, containing customer-specific information. A service account accesses the Google Wallet API, authenticated by a private service account key.\n"],null,["# Key concepts and terminology\n\nPass issuer\n-----------\n\nThe Passes issuer owns the pass and must issue passes to their customers. This\ncan be 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\nLoyalty Class\n-------------\n\nA Loyalty Class can be thought of as loyalty program. An issuer might create\nmultiple loyalty programs like *Standard* and *Premium*, each with their own\ndistinctive style and appearance.\n\nIn addition to style and appearance, Loyalty Classes can also be used to enable\nadditional features like Smart Tap, and the Enrollment and Sign In.\n\nLoyalty Object\n--------------\n\nA Loyalty Object is an instance of a Loyalty Class. Create a new Loyalty Object\ninstance for each customer that's enrolled in a loyalty program.\n\nPass Class\n----------\n\nA Loyalty Class is a type of Pass Class. Pass Classes describe general\ninformation for related Pass Objects such as style and appearance, and don't\ninclude customer details.\n\nOther types of Pass Classes include:\n\n- Boarding pass\n- Event tickets\n- Gift cards\n- Offers\n- Transit passes\n- Vaccine cards\n\nPass Object\n-----------\n\nA Loyalty Object is a type of Pass Object. Like Loyalty Objects, a Pass Object\nis an instance of a corresponding Pass Class. Create a Pass Object\nfor each customer that's issued a pass.\n\nPass Objects contains customer-specific information. For example, it can be used\nto identify that a customer not only has a ticket for a flight, but also\nidentify which seat on the flight they've been allotted.\n\nService account\n---------------\n\nThe service account is the identity that's used to call the Google Wallet API.\nBe sure to grant permission to access the Google Wallet API to this service account.\n\nService account key\n-------------------\n\nThe service account key is the credential used to authenticate your application\nas the service account. The service account key is highly sensitive and\nmust be kept private. If a third party has access to the service account\nkey, they can identify themselves as the service account and perform\nactions that the service account is permitted to perform."]]
