> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/policies/glossary.md).
# Glossary
Define The Wallet Crew terms, including tenants, environments, enrolment forms, pass templates, and digital wallet passes.
Use this glossary to interpret terms used in The Wallet Crew back-office and guides. Each definition explains the concept, its purpose, and where to find more detail.
Real-world examples
* A retail Brand uses one tenant for a loyalty programme.
* An event organiser issues one pass for each attendee.
* A marketing team uses a redirect QR code for each store campaign.
## Core concepts
### Brand
A Brand is the organisation using The Wallet Crew to create and manage wallet passes. A Brand can be a retailer, event organiser, ticketing provider, or partner.
### End user
An end user is a Brand’s customer. End users receive, add, and use passes in Apple Wallet or Google Wallet.
### Tenant
A tenant is an isolated workspace for one Brand or wallet programme. It contains its own templates, passes, configuration, data, and team access.
Most Brands use one tenant. Separate Brands, countries, or programmes can use separate tenants when they need independent data, credentials, or teams.
### Environment
An environment separates testing from live operations. The Wallet Crew provides **QA** for testing and **production** for live customer use.
QA and production are fully isolated. A pass created in QA never appears in production. Configuration can be copied between environments when required.
Read [Key concepts](/get-started/readme/key-concepts.md) for a detailed explanation of tenants and environments.
### Back-office
The back-office is The Wallet Crew’s secured administration console. It is where authorised team members manage tenant configuration, templates, passes, integrations, and user access.
## Enrolment and distribution
### Enrolment form
An enrolment form is a hosted page that collects customer data and creates or retrieves a customer profile. It can then issue a wallet pass.
“Customer registration” may describe the same journey in older material. One programme can use several forms for different campaigns, stores, or events.
Learn how to configure an [enrolment form](/guides-enrolment/enrolment/enrolment-form.md).
### Redirect
A redirect is a managed URL or QR code that opens an enrolment form. Redirects can include store or campaign-specific data while pointing to the same form.
This supports distinct entry points without duplicating the enrolment experience. See [Redirects](/guides-enrolment/enrolment/enrolment-form/redirect.md) for setup guidance.
## Integrations and data
### Connector
A connector links The Wallet Crew with another system, such as a CRM, loyalty platform, ticketing system, point-of-sale system, or marketing platform.
Connectors can create or update passes, retrieve data, and send wallet events. See the [connector catalogue](/connectors/wallet-pass-connectors.md) for supported systems.
### Pass data provider
A pass data provider is a source of information used to populate a pass. It can retrieve data from a connector or another configured source when a pass is rendered or refreshed.
This keeps the pass aligned with the source system without duplicating its data model.
### External identifier
An external identifier is a stable value from another system, such as a CRM customer ID, loyalty number, or booking reference. It links a pass to the relevant record in that system.
External identifiers help operations teams find the right pass. They do not guarantee that one identifier matches only one pass.
## Wallet passes
### Pass template
A pass template is the reusable model for one kind of wallet pass. It defines the design, displayed fields, barcode format, and personalisation rules.
A template does not belong to one customer. It is reused to issue many individual passes, such as a loyalty card or an event ticket.
### Pass
A pass is one digital card, ticket, or voucher issued to one customer. It is created from a template and can be added to Apple Wallet or Google Wallet.
A pass can exist before it is installed. When its information changes, The Wallet Crew can update the pass in the customer’s wallet.
Use the [pass list](/guides-monitoring/monitor/pass-list.md) to find and inspect individual passes.
### Pass type
A pass type defines the intended wallet use case and layout. The Wallet Crew supports five main types:
* **Loyalty card** — stores points, rewards, or membership information.
* **Event ticket** — provides event details and a barcode for entry.
* **Gift card** — displays stored value and redemption information.
* **Offer** — presents a time-bound promotion or coupon.
* **Generic** — supports use cases outside the standard types.
For template selection and platform behaviour, see [Pass types and templates](/guides-design/design/readme-1.md).
### Pass layout
A pass layout controls how information appears in Apple Wallet and Google Wallet. It determines the placement of fields, images, colours, labels, and barcode content.
The layout belongs to the template. Individual passes supply the customer-specific values.
### Installation status
Installation status records whether an end user has added a pass to Apple Wallet or Google Wallet. A pass can be created without being installed.
This status supports operational checks, reporting, and distribution follow-up.
## FAQ
What is the difference between a template and a pass?
A template is the reusable blueprint. A pass is an individual instance issued from that blueprint for a customer.
What is the difference between QA and production?
QA is for testing. Production serves live customers. Both environments are isolated to prevent testing from affecting live passes.
Can one enrolment form serve several stores?
Yes. Use separate redirects for each store or campaign. Each redirect can point to the same enrolment form.
Can one customer have several passes?
Yes. A customer can hold several passes, such as one loyalty card and multiple event tickets. Each pass remains a separate record.
What is the difference between a connector and a pass data provider?
A connector integrates The Wallet Crew with an external system. A pass data provider is the configured source that supplies information for a pass. A connector can provide data to a pass data provider.
## Get help
For platform questions or incidents, start with the documentation agent. If further help is needed, use [The Wallet Crew support options](/policies/support-options.md).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.thewalletcrew.io/policies/glossary.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.