主要概念和术语
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
卡券颁发者
卡券发行方是卡券的所有者,并负责向其乘客签发卡券。可以是您、开发者或您代表的组织。
若要成为卡券发行方,您必须先注册为发卡机构。
登机牌类别
您可以将 FlightClass
视为已安排的航班。发卡机构可以对航线和时间的排列组合,创建多个排定的航班。为满足机场特定要求,代表预定航班的每个 FlightClass
都可以包含自己的外观和数据字段。
此外,FlightClass
还可用于启用智能触碰等其他功能。
登机牌对象
“登机牌”对象是“登机牌”类的实例。需要为通过登机牌分发的每位乘客创建新的 FlightObject
实例。
卡券类
“登机牌”类是一种卡券类。卡券类描述相关卡券对象的一般信息(例如样式和外观),不包括乘客详细信息。
其他类型的卡券类包括:
- 会员卡
- 活动门票
- 礼品卡
- 优惠
- 公交卡
- 新冠信息卡
卡券对象
FlightObject
是一种卡券对象。与 FlightObject
一样,卡券对象是相应卡券类的实例。需要为发放登机牌的每位乘客创建一个卡券对象。
卡券对象包含乘客专属信息。例如,它们可用于识别乘客不仅拥有机票的机票,还可用于识别分配给他们的航班上的哪个座位。
服务账号
服务帐号是用于调用 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\u003eBoarding Passes are digital representations of flight tickets, containing passenger and flight-specific information like seat assignments and flight details, issued by registered entities called Issuers.\u003c/p\u003e\n"],["\u003cp\u003eIssuers create Boarding Pass Classes to define the general style, appearance, and data fields for a specific flight or route, like a template for individual Boarding Passes.\u003c/p\u003e\n"],["\u003cp\u003eA new Boarding Pass Object (an instance of a Boarding Pass Class) is generated for each passenger, holding their unique information within the framework of the Boarding Pass Class.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Wallet API integration requires a Service Account, an identity with granted access to the API, and a secure Service Account Key for authentication.\u003c/p\u003e\n"],["\u003cp\u003eBoarding Passes are part of a broader system of digital passes within Google Wallet, encompassing other types such as loyalty cards, event tickets, and gift cards.\u003c/p\u003e\n"]]],["A Pass Issuer, which could be a developer or organization, must register to issue passes. They create `FlightClasses` (scheduled flights) that define appearance and data. For each passenger, a `FlightObject` (instance of the `FlightClass`) is created, containing passenger-specific information. A `Pass Class` defines general pass details, while other pass types include loyalty cards and gift cards. A service account and its key are required for accessing the Google Wallet API. The key must be kept private.\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\nissuing passes to their passengers. This could be you, the developer, or the\norganization that you represent.\n\nIn order to become a passes issuer, you must first register as an Issuer.\n\nBoarding Pass class\n-------------------\n\nA `FlightClass` can be thought of as scheduled flight. An issuer can\ncreate multiple scheduled flights with permutation of routes and timings. Each\n`FlightClass` representing a scheduled flight can contain its own\nappearance and data fields to meet the airport-specific requirements.\n\nIn addition, a `FlightClass` can also be used to enable additional\nfeatures like Smart Tap.\n\nBoarding Pass object\n--------------------\n\nA Boarding Pass object is an instance of a Boarding Pass class. A new\n`FlightObject` instance needs to be created for each passenger that's\ndistributed with a Boarding Pass.\n\nPass Class\n----------\n\nA Boarding Pass 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 passenger details.\n\nOther types of pass classes include the following:\n\n- Loyalty cards\n- Event tickets\n- Gift cards\n- Offers\n- Transit passes\n- COVID cards\n\nPass Object\n-----------\n\nA `FlightObject` is a type of pass object. Like a\n`FlightObject`, a Pass Object is an instance of a corresponding pass\nClass. A pass object needs to be created for each passenger that's issued a\nBoarding Pass.\n\nPass objects contain passenger-specific information. For example, they can be\nused to identify that a passenger 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.\nPermission to access the Google Wallet API needs to be granted to this service\naccount.\n\nService account key\n-------------------\n\nThe service account key is the credential used to authenticate your\napplication as the service account. The service account key is highly sensitive\nand needs to be kept private. If a third party has access to the service account\nkey, they can identify themselves as the service account and perform actions\nthat the service account is permitted to perform."]]