> 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/get-started/readme/understand-platform.md).

# Understand the platform

One-page overview of The Wallet Crew, the Wallet as a Service platform for Apple Wallet and Google Wallet passes: what it does and how brand teams use it.

<div data-with-frame="true"><figure><img src="https://3566051324-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWLc8AHXW4tdrAXUBfrYF%2Fuploads%2Fgit-blob-06f63fdc780ed85394f2052998ebf3b6eb4f2dfa%2Fplatform-overview-hero.png?alt=media" alt="Overview of The Wallet Crew platform for wallet pass design, distribution, and lifecycle operations."><figcaption><p>The Wallet Crew connects pass design, distribution, and lifecycle operations in one platform.</p></figcaption></figure></div>

The Wallet Crew is a white-label platform to **create, distribute, and operate wallet passes**. Brands use it for **loyalty cards, coupons, gift cards, tickets, and membership cards** in **Apple Wallet** and **Google Wallet**. Customers save the pass once, then the same pass stays **up to date over time**.

The Wallet Crew acts as a bridge between existing business systems and wallet providers: it does not create a new data silo. Customer profiles, loyalty records, tickets, and transactions remain in their source systems. The Wallet Crew reads from them, transforms the data into wallet-compatible content, and delivers updates when those records change.

Many tasks are self-service. Integration design remains part of the engagement, with The Wallet Crew team involved throughout.

## What problems it solves

Most wallet projects start with the same friction. Customers need something scannable at checkout or entry. App installs stay low. Plastic cards add cost and logistics.

The Wallet Crew ships pass distribution through web, email, or QR. It then keeps that same installed pass accurate with updates over time. This creates one operating layer across Apple and Google while still following each provider’s rules.

Wallet is also not a “marketing-only” channel. A pass is a **digital credential** that customers can present in the moment, even with poor connectivity. Notifications can help, but the core value is simple: the pass remains available, scannable, and current.

## Who it’s for

To find the right pages for each role, see [Find your starting point](https://docs.thewalletcrew.io/get-started/readme/find-your-starting-point.md).

## How it works (high level)

The Wallet Crew follows a simple lifecycle. A team designs a template, distributes an “Add to Wallet” entry point, then pushes updates over time.

1. **Design**: pick a pass type and configure branding, fields, and barcode/QR. Start with [Pass types & templates](https://docs.thewalletcrew.io/guides-design/design/pass-types-and-templates.md), then the [pass template editor](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/template-configuration.md).
2. **Connect data**: link each pass to source systems using stable identifiers, so CRM and POS remain the source of truth. See [Pass data and sync](https://docs.thewalletcrew.io/developers-guides/pass-architecture/pass-data-and-sync.md).
3. **Distribute**: ship pass installation from owned channels. Most deployments start with [On your website](https://docs.thewalletcrew.io/guides-enrolment/enrolment/on-your-website.md) and [Via email](https://docs.thewalletcrew.io/guides-enrolment/enrolment/via-email.md).
4. **Operate and engage**: update passes, trigger notifications, and measure adoption over time. Start with [Push notifications](https://docs.thewalletcrew.io/guides-animation/engage-and-animate/automatisation/push-notifications.md).

## Key capabilities

### Pass templates for Apple Wallet and Google Wallet

Templates are configured once, and The Wallet Crew generates the right Apple and Google payloads.

Most brands start with a core set of templates, then expand over time. A common baseline includes [Loyalty card](https://docs.thewalletcrew.io/guides-design/design/loyalty-card-template-configuration.md), [Offer](https://docs.thewalletcrew.io/guides-design/design/offer.md), [Gift card](https://docs.thewalletcrew.io/guides-design/design/gift-card.md), [Event ticket](https://docs.thewalletcrew.io/guides-design/design/event-ticket.md), and [Generic](https://docs.thewalletcrew.io/guides-design/design/generic.md).

For multi-language programs, labels and content can be translated per template. See [How to translate a template](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/template-configuration/how-to-translate-a-template.md).

### Distribution without forcing a mobile app

Customers can add a pass without a mobile app, which is usually the biggest adoption lever. Most deployments start with web and email, then expand to QR codes in-store or on-site.

Common distribution entry points include [On your website](https://docs.thewalletcrew.io/guides-enrolment/enrolment/on-your-website.md), [Via email](https://docs.thewalletcrew.io/guides-enrolment/enrolment/via-email.md), and, when an app exists, [On your mobile app](https://docs.thewalletcrew.io/guides-enrolment/enrolment/on-your-mobile-app.md).

### Updates, notifications, and location-based experiences

Wallet passes are meant to evolve, so the same installed pass can change after it’s saved.

Typical update scenarios include points and tier refresh after purchase, coupon state changes after redemption, gift card balance updates, and ticket changes.

See [Geolocated notifications](https://docs.thewalletcrew.io/guides-animation/engage-and-animate/geolocated-notifications.md).

### Integrations and APIs

The Wallet Crew sits between distribution channels and source systems.

Teams integrate through built-in connectors, including CRM, POS, and marketing automation tools. The API can also be used for issuance, updates, and lookups. Start with [API reference](https://docs.thewalletcrew.io/api-reference/).

### Operations and in-store/on-site usage

Operating wallet at scale needs targeting and reliable redemption. Metadata, computed from the pass template, is used to target by store, country, tier, or channel.

When staff tooling is needed, operators can use [Pass Scanner](https://docs.thewalletcrew.io/guides-scan/scan/pass-scanner.md) to scan and validate passes.

## What it is (and is not)

The Wallet Crew is not a payment solution: all payment transactions continue to operate within Apple Pay and Google Pay.

## Privacy and security

The Wallet Crew follows a **privacy-first approach** and does not store customer personal data by default. It stores **external identifiers** instead. Those identifiers let The Wallet Crew fetch data and render the pass.

For the security model and the compliance documents, see the [Security overview and trust model](https://docs.thewalletcrew.io/policies/privacy-and-security/security-overview-and-trust-model.md). For what an admin configures, such as signed links, see [Wallet card security](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/wallet-card-security.md).

## FAQ

<details>

<summary><strong>Do customers need to install a mobile app?</strong></summary>

No. Customers can add a pass without a mobile app, from your website, from an email or from a QR code. See [On your website](https://docs.thewalletcrew.io/guides-enrolment/enrolment/on-your-website.md) and [Via email](https://docs.thewalletcrew.io/guides-enrolment/enrolment/via-email.md).

</details>

<details>

<summary><strong>Can a pass be updated after it is installed?</strong></summary>

Yes. The same installed pass can change after it is saved, for example points and tier after a purchase, a coupon state after redemption, a gift card balance or a ticket change.

</details>

<details>

<summary><strong>Do you store personal data?</strong></summary>

Not by default. The Wallet Crew does not store customer personal data by default. It stores external identifiers instead, which let it fetch data from your systems and render the pass.

</details>

<details>

<summary><strong>Can brand-owned Apple and Google issuer accounts be used?</strong></summary>

Yes. Apple and Google require brand-owned issuer credentials in production, and The Wallet Crew issues passes under the brand identity.

Start with [Apple & Google Wallet](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/apple-and-google-wallet.md).

</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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.thewalletcrew.io/get-started/readme/understand-platform.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
