The Passes issuer owns the pass and must issue passes to their customers. This can be you, the developer, or the organization that you represent.
In order to become a Passes Issuer, you must first register as an Issuer.
A Loyalty Class can be thought of as loyalty program. An issuer might create multiple loyalty programs like Standard and Premium, each with their own distinctive style and appearance.
In addition to style and appearance, Loyalty Classes can also be used to enable additional features like Smart Tap, and the Enrollment and Sign In.
A Loyalty Object is an instance of a Loyalty Class. Create a new Loyalty Object instance for each customer that's enrolled in a loyalty program.
A Loyalty Class is a type of Pass Class. Pass Classes describe general information for related Pass Objects such as style and appearance, and don't include customer details.
Other types of Pass Classes include:
- Boarding pass
- Event tickets
- Gift cards
- Transit passes
- Vaccine cards
A Loyalty Object is a type of Pass Object. Like Loyalty Objects, a Pass Object is an instance of a corresponding Pass Class. Create a Pass Object for each customer that's issued a pass.
Pass Objects contains customer-specific information. For example, it can be used to identify that a customer not only has a ticket for a flight, but also identify which seat on the flight they’ve been allotted.
The service account is the identity that's used to call the Google Wallet API. Be sure to grant permission to access the Google Wallet API to this service account.
Service account key
The service account key is the credential used to authenticate your application as the service account. The service account key is highly sensitive and must be kept private. If a third party has access to the service account key, they can identify themselves as the service account and perform actions that the service account is permitted to perform.