> 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

## Pass architecture

This section explains how The Wallet Crew structures pass data, renders wallet artifacts, and isolates tenants and environments. It is the reference section for the pass data model, render pipeline, and infrastructure boundaries.

<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

* [Structure](/developers-guides/pass-architecture/structure.md)
* [Pass data and sync](/developers-guides/pass-architecture/pass-data-and-sync.md)
* [How a pass is rendered](/developers-guides/pass-architecture/how-a-pass-is-rendered.md)
* [Infrastructure](/developers-guides/pass-architecture/infrastructure.md)

### How to use this section

Start with [Structure](/developers-guides/pass-architecture/structure.md) when the goal is to understand the pass record itself.

Continue with [Pass data and sync](/developers-guides/pass-architecture/pass-data-and-sync.md) when the goal is to understand how connector data, additional data, and render triggers work together.

Use [How a pass is rendered](/developers-guides/pass-architecture/how-a-pass-is-rendered.md) when the goal is to debug wallet output or render failures. Use [Infrastructure](/developers-guides/pass-architecture/infrastructure.md) when the goal is to review hosting, environments, isolation, or outbound connectivity.

### FAQ

<details>

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

Start with the page that matches the question being answered. Most implementation work starts with the data model. Most troubleshooting work starts with data sync or rendering.

</details>

<details>

<summary><strong>Does this section describe product usage or platform internals?</strong></summary>

It describes the platform model behind pass behavior. It is the reference layer behind the integration guides.

</details>

<details>

<summary><strong>When is the infrastructure page needed?</strong></summary>

Use it for network allowlisting, environment reviews, tenant isolation questions, and security or architecture validation.

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