主要概念和术语
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
卡券颁发者
卡券发行方是卡券的所有者，负责向其客户签发卡券。可以是您、开发者或您代表的组织。
若要成为卡券发行方，您必须先注册为卡券发行方。
活动门票等级
EventClass 可以视为已安排的活动。发卡机构可以组合事件名称和时间来创建多个已安排的活动。为满足场地特定要求，代表预定活动的每个EventClass可以包含自己的外观和数据字段。
此外，EventClass 还可用于启用智能触碰等其他功能。
活动门票对象
活动门票对象是 EventClass 的实例。您应为随活动门票分发的每位客户创建一个新的 EventObject 实例。
卡券类
EventClass 是一种卡券类。卡券类描述相关卡券对象的一般信息（例如样式和外观），不包含客户详细信息。
卡券对象
EventObject 是一种卡券对象。与 EventObjects 一样，卡券对象是相应卡券类的实例。应为每一个发放活动门票的客户创建一个卡券对象。
卡券对象包含特定于客户的信息。例如，它可用于识别客户不仅拥有活动门票，还可用于识别为活动分配了哪个座位。
服务账号
服务帐号是用于调用 Google Wallet API 的身份。应向此服务账号授予访问 Passs API 的权限。
服务账号密钥
服务帐号密钥是用于以服务帐号的身份对应用进行身份验证的凭据。您应将服务帐号密钥视为高度敏感并确保其私密性。如果第三方有权访问服务帐号密钥，则将能够将自己标识为服务帐号，并执行服务帐号允许执行的操作。
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-08-29。
[null,null,["最后更新时间 (UTC)：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."]]
