主要概念和术语
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
卡券发行方
卡券发行方是卡券的所有者，且必须向其客户签发卡券。可以是您、开发者或您代表的组织。
若要成为卡券发行方，您必须先注册为卡券发行方。
会员卡类
会员卡类可以视为会员卡。发卡机构可以创建多个会员回馈活动，如标准和高级，每个会员回馈活动都有自己独特的风格和外观。
除了样式和外观之外，会员类还可用于启用更多功能，例如智能触碰、注册和登录。
会员卡对象
会员卡对象是会员卡类的实例。为参加会员回馈活动的每个客户创建一个新的会员卡对象实例。
卡券类
会员卡类是一种卡券类。卡券类描述相关卡券对象的一般信息（如样式和外观），不包括客户详细信息。
其他类型的卡券类包括：
- 登机牌
- 活动门票
- 礼品卡
- 优惠
- 公交卡
- 疫苗接种卡
卡券对象
会员卡对象是一种卡券对象。与会员卡对象一样，卡券对象是相应卡券类的实例。为发放卡券的每个客户创建一个卡券对象。
卡券对象包含特定于客户的信息。例如，它可用于识别客户不仅拥有机票的机票，还可用于识别他们已分配到航班上的哪个座位。
服务账号
服务帐号是用于调用 Google Wallet API 的身份。
请务必向此服务账号授予访问 Google Wallet API 的权限。
服务账号密钥
服务帐号密钥是用于以服务帐号的身份对应用进行身份验证的凭据。服务帐号密钥具有高度敏感性，必须保证私密性。如果第三方有权访问服务帐号密钥，则可以表明自己是服务帐号，并执行服务帐号可以执行的操作。
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-08-29。
[null,null,["最后更新时间 (UTC)：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."]]
