> 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/configure/how-to-configure.md).

# HOW TO CONFIGURE

The Wallet Crew documentation is organized around three main areas. Each section covers a distinct part of the setup and operations flow.

Before creating passes or connecting external systems, a number of parameters must be set at the platform level. The Configuration section covers everything needed to make The Wallet Crew operational for a brand: from the initial account setup to the visual design of Wallet templates, including the technical credentials required to issue passes through Apple Wallet and Google Wallet under the brand's own identity.

<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>Platform</h3></td><td><a href="https://123508161-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDJrf9G0l7ArnvuwEH0a8%2Fuploads%2FKZu375jWYzCfoXblT2ZE%2Fplatform.svg?alt=media">https://123508161-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDJrf9G0l7ArnvuwEH0a8%2Fuploads%2FKZu375jWYzCfoXblT2ZE%2Fplatform.svg?alt=media</a></td><td><a href="/configure/advanced-configuration/platform.md">Platform</a></td></tr><tr><td><h3>Wallet</h3></td><td><a href="https://123508161-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDJrf9G0l7ArnvuwEH0a8%2Fuploads%2FwYaGmsrO3lvjQAHDr12f%2Fwallet.svg?alt=media">https://123508161-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDJrf9G0l7ArnvuwEH0a8%2Fuploads%2FwYaGmsrO3lvjQAHDr12f%2Fwallet.svg?alt=media</a></td><td><a href="/configure/advanced-configuration/wallet.md">Wallet</a></td></tr><tr><td><h3>Enrolment Form</h3></td><td><a href="https://123508161-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDJrf9G0l7ArnvuwEH0a8%2Fuploads%2F1O7Wv4URDg8nRiLXvkoJ%2Fenrolment-form-config.svg?alt=media">https://123508161-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDJrf9G0l7ArnvuwEH0a8%2Fuploads%2F1O7Wv4URDg8nRiLXvkoJ%2Fenrolment-form-config.svg?alt=media</a></td><td><a href="/configure/advanced-configuration/enrolment-form.md">Enrolment Form</a></td></tr></tbody></table>

**Platform settings** are the starting point. This is where the tenant is initialized — general parameters such as the application title, supported languages, and the favicon displayed on hosted pages. User access and multi-factor authentication are configured here, as well as the API keys used to authenticate backend requests to The Wallet Crew APIs. Brands that want to host enrolment and download pages under their own domain will also find the custom domain configuration in this section.

**Wallet settings** cover the credentials that Apple and Google require to issue passes. Each platform has its own authentication mechanism: Apple Wallet relies on certificates and push notification identifiers managed through the Apple Developer account, while Google Wallet requires access to the Google Pay & Wallet Console and dedicated API credentials. Both must be configured before any pass can be created or distributed.

**Template configuration** defines the structure and appearance of the passes themselves — field layout, colors, images, and dynamic content via the DotLiquid templating engine. Templates can be translated into multiple languages and duplicated or imported across tenants.


---

# 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/configure/how-to-configure.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.
