> 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/developers-guides/integration-guides/wallet.md).

# Wallet

## Wallet

Wallet work in The Wallet Crew follows a simple lifecycle. A pass is created through the Cinto SDK, a connector event, or `POST /passes`. Use `POST /passes` for backend-driven flows. After creation, templates control what appears in Apple Wallet and Google Wallet.

<details>

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

* A loyalty pass is created during account signup, then refreshed after each purchase.
* A ticket pass is created from an order event, then updated when gate or seat data changes.
* A membership pass is created after registration, then kept current through connector data and pass-level overrides.

</details>

### Choose the right creation flow

#### Enrolment flows

Use [Enrolment flows](/developers-guides/integration-guides/wallet/enrolment-flows.md) when pass creation happens during signup, checkout, registration, or another user-facing journey. This is the usual pattern when a web flow, app flow, or hosted form controls issuance.

#### Connector-triggered pass creation

Use [Connector-triggered pass creation](/developers-guides/integration-guides/wallet/connector-triggered-pass-creation.md) when an upstream system decides eligibility and creates the pass from an event. This is common for CRM, ticketing, or subscription-driven issuance.

{% hint style="info" %}
Pass creation is supported through the Cinto SDK, connectors, and `POST /passes`. Use `POST /passes` for backend-driven flows. See [Pass lifecycle → Creating a pass](/developers-guides/integration-guides/wallet/pass-lifecycle.md).
{% endhint %}

### Build and maintain the pass

Once a pass exists, the next step is usually to decide how wallet fields are populated and refreshed. [Update pass data in templates](/developers-guides/integration-guides/wallet/update-pass-data-in-templates.md) explains how stored values and connector data reach the template. [Templating engine](/developers-guides/integration-guides/wallet/liquid-templating.md) documents the supported Liquid behavior used in those templates.

If the pass data model needs a refresher first, use [Pass data and sync](/developers-guides/pass-architecture/pass-data-and-sync.md).

### Pages in this section

* [Enrolment flows](/developers-guides/integration-guides/wallet/enrolment-flows.md) explains user-facing pass creation.
* [Connector-triggered pass creation](/developers-guides/integration-guides/wallet/connector-triggered-pass-creation.md) explains source-driven pass creation.
* [Update pass data in templates](/developers-guides/integration-guides/wallet/update-pass-data-in-templates.md) explains how to update existing passes and display the right values.
* [Templating engine](/developers-guides/integration-guides/wallet/liquid-templating.md) explains supported Liquid syntax, filters, and error behavior.

### FAQ

<details>

<summary><strong>Can passes be created directly with the API?</strong></summary>

Yes. Pass creation is supported through the Cinto SDK, connectors, and `POST /passes`. Use `POST /passes` for backend-driven flows. See [Pass lifecycle → Creating a pass](/developers-guides/integration-guides/wallet/pass-lifecycle.md).

</details>

<details>

<summary><strong>Which page should be read first?</strong></summary>

Start with the creation flow that matches the project. Then continue with the update guide and the templating reference.

</details>

<details>

<summary><strong>When is the templating reference needed?</strong></summary>

Use it when a template must render dynamic values, conditions, or formatted output. The update guide is usually the better starting point for day-to-day work.

</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/developers-guides/integration-guides/wallet.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.