> 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/pass-architecture.md).

# Pass architecture

Understand how wallet passes are structured, rendered and isolated in The Wallet Crew: pass data model, connector sync, render triggers and security.

This section explains how The Wallet Crew structures pass data, renders wallet artifacts, and isolates tenants and environments.

<details>

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

* A loyalty program needs to understand which values stay on the pass and which values stay in the CRM.
* A ticketing integration needs to understand when connector data is fetched and why a gate update is not instant.
* A security review needs to confirm tenant isolation, environment separation, and outbound IP behavior.

</details>

## In this section

| Question                                                                                 | Page                                                                                                                  |
| ---------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| What does a pass record contain, where does pass data come from, and when is it fetched? | [Pass data and sync](https://docs.thewalletcrew.io/developers-guides/pass-architecture/pass-data-and-sync.md)         |
| How is the wallet artifact built, and why did a render fail?                             | [How a pass is rendered](https://docs.thewalletcrew.io/developers-guides/pass-architecture/how-a-pass-is-rendered.md) |
| Which IPs, environments, and isolation rules apply?                                      | [Security and infrastructure](https://docs.thewalletcrew.io/developers-guides/pass-architecture/infrastructure.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 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/developers-guides/pass-architecture.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.
