> 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/guides-enrolment/overview.md).

# Enrolment Guides

Enrolment defines how a customer gets an Apple Wallet pass or a Google Wallet pass installed. For most projects, enrolment is a key topic. It requires analysis and design.

Enrolment is not just a delivery mechanism. It is the system that connects acquisition, identity resolution, data collection, and pass installation.

Every design choice made in enrolment has downstream effects. It can improve conversion, strengthen data quality, reduce duplicates, and make re-installation reliable after a device change. Over time, these details decide whether a Wallet program becomes a habit or stays a one-off install.

<details>

<summary><strong>Real-world examples</strong></summary>

* **Loyalty acquisition in-store:** a QR code opens an enrolment form and issues a loyalty card.
* **Gift card access after purchase:** an account page exposes “Add to Wallet” to install the gift card.
* **Membership program:** an email link lets customers re-install a member card after device change.
* **Event ticketing:** a post-purchase page or in-app screen triggers ticket installation.

</details>

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3>Enrolment form</h3></td><td><a href="/files/kAqdFSlDdLRywPQQGJqA">/files/kAqdFSlDdLRywPQQGJqA</a></td><td><a href="/pages/TGicq2u9Q05Orb6eoG4h">/pages/TGicq2u9Q05Orb6eoG4h</a></td></tr><tr><td><h3>Website embed</h3></td><td><a href="/files/tsfUngHdMvbS8qY4aXqo">/files/tsfUngHdMvbS8qY4aXqo</a></td><td><a href="/pages/Z5RlzwsQyC52tRTU3B5u">/pages/Z5RlzwsQyC52tRTU3B5u</a></td></tr><tr><td><h3>Email Delivery</h3></td><td><a href="/files/K0epD56Zjlu1kiTY4YKR">/files/K0epD56Zjlu1kiTY4YKR</a></td><td><a href="/pages/Jlu4GvVpp6ZKaEXtlTCa">/pages/Jlu4GvVpp6ZKaEXtlTCa</a></td></tr><tr><td><h3>Mobile App Integration</h3></td><td><a href="/files/Dx6KBrHSgJWC3ZchP8Mw">/files/Dx6KBrHSgJWC3ZchP8Mw</a></td><td><a href="/pages/Vd98rq4EVfeW8dW1TLFB">/pages/Vd98rq4EVfeW8dW1TLFB</a></td></tr><tr><td><h3>Download pages</h3></td><td></td><td><a href="/pages/8mhoewUTcBWgyos9k9ZB">/pages/8mhoewUTcBWgyos9k9ZB</a></td></tr></tbody></table>

## Enrolment channels

The Wallet Crew offers multiple ways to enrol at the best time in the customer journey.

In practice, enrolment is where “Add to Wallet” is exposed, for example through a QR code, a website button, an email link, or an in-app action.

In practice, “best time” usually means a moment where intent is high and identity is easy to resolve. For loyalty and membership, that moment is often the join action. For tickets and gift cards, that moment is often an authenticated surface or a post-purchase screen.

The pages above cover the main enrolment and delivery channels supported by The Wallet Crew.

Some projects require deeper integration to keep enrolment fully embedded in existing web or app flows. In those cases, The Wallet Crew SDK can be used on a website or in a native mobile app, depending on the chosen architecture.

Download pages support delivery after a pass already exists. They display wallet actions for one pass or a list of passes. They do not collect registration data or consent. See [Download pages](/guides-enrolment/enrolment/download-pages.md).

## Other supported patterns

Some projects require additional enrolment patterns. The most common one is **bulk enrolment**. This is used when a Brand already has a customer or member list and wants to issue passes at scale, for example during a migration, for season members, or for corporate programs.

Bulk enrolment can be triggered from the back-office (CSV or Excel import). It can also be automated via API or via file-based integration such as SFTP, depending on the project scope. For migration projects, see [Pass migration](https://docs.thewalletcrew.io/configuration/wallet/import-and-export/pass-migration).

The output of bulk enrolment is typically a **pass link** per customer. The Brand can distribute that link through its own channels. The end-to-end sending can also be delegated to The Wallet Crew, when required.

Bulk enrolment separates pass generation from pass distribution. This keeps rollouts flexible at scale. If passes must be handed over outside The Wallet Crew, see [Export passes from TWC to another provider](https://docs.thewalletcrew.io/configuration/wallet/import-and-export/pass-migration/export-passes-from-twc-to-another-provider).

## Why enrolment design matters

Enrolment is part of the product experience. It defines the “front door” to a wallet program. It also defines the rules to identify a customer and decide which pass should be installed.

#### Start from the value moment

The right design usually starts with the moment where the pass becomes valuable. The chosen channel should match that moment.

* In-store acquisition → QR + enrolment form
* Authenticated purchase or account access → website embed or native app integration
* Existing pass delivery → download page
* Migration or legacy program seeding → bulk enrolment
* Re-install or device change → email delivery as a resilient fallback

Renewal and re-install moments should be treated as first-class flows. They drive long-term adoption and reduce support load.

#### Choose an identity strategy early

Identity design is the next constraint. A matching key is needed to avoid duplicates and ensure the right pass is returned. Email is common, but it is not always stable. Phone number, membership number, ticket order ID, or a CRM identifier can be better keys depending on the program.

When enrolment relies on a form, identity resolution and eligibility checks are often implemented through [Social sign-in](/guides-enrolment/enrolment/enrolment-form/social-sign-in.md) and [Validation rules](/guides-enrolment/enrolment/enrolment-form/validation-rules.md).

#### Keep data collection minimal

Data collection should stay minimal at enrolment. Fields that are not required for issuance can be collected later. This typically improves completion rate while keeping data quality high.

When consent is captured during enrolment, align consent wording and storage with the Brand privacy policy, the [Privacy and security](https://docs.thewalletcrew.io/policies/privacy-and-security) policies, and the [Data Processing Agreement model](https://docs.thewalletcrew.io/policies/privacy-and-security/data-processing-agreement-model).

## Recommended approach

Most projects converge to a simple approach: one primary channel, plus one fallback channel.

The primary channel should match where the program “lives” for customers. Loyalty and membership often live in-store or in campaign acquisition, which makes QR → form a strong default. Tickets and gift cards often live in authenticated environments, which makes website or app distribution a strong default.

The fallback channel is usually email delivery, because it is resilient across devices and platforms. It is also a strong re-install path when a pass is deleted or when a customer changes phone.

## FAQ

<details>

<summary><strong>Is there a difference between enrolment and distribution?</strong></summary>

In this documentation, there is no difference.

Both terms refer to the same topic: choosing the entry point (QR, web, email, app), resolving identity when needed, and delivering the Apple Wallet / Google Wallet installation experience.

</details>

<details>

<summary><strong>Which channel works best for loyalty and member cards?</strong></summary>

An enrolment form is usually the best starting point.

It supports data capture, eligibility rules, and identity. It also supports in-store QR acquisition and staff-assisted flows.

</details>

<details>

<summary><strong>Which channel works best for tickets and gift cards?</strong></summary>

A logged-in website surface or an in-app surface is often the cleanest path.

It avoids re-collecting data and it uses the existing account context to resolve identity.

</details>

<details>

<summary><strong>Why keep email delivery if a website or app exists?</strong></summary>

Email is a strong fallback for desktop and for device changes.

It also reduces support load, because it creates a self-service re-install path.

</details>

<details>

<summary><strong>What does “bulk enrolment” mean in practice?</strong></summary>

Bulk enrolment means issuing passes for an existing list of customers or members.

It is typically used for migrations, seeding a loyalty base, corporate memberships, or season programs. It usually produces a pass link per customer, then distribution happens either through Brand channels or through a delegated send operated by The Wallet Crew.

</details>


---

# 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/guides-enrolment/overview.md?ask=<question>&goal=<endgoal>
```

`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.