> 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/configuration/wallet.md).

# Wallet

The Wallet section covers everything related to how passes are configured, designed, secured, and migrated. These settings are brand-specific — each one directly affects what end-users see and how passes behave on Apple Wallet and Google Wallet.

<table data-view="cards"><thead><tr><th>Title</th><th>Summary</th><th data-type="content-ref"></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><h4>Apple &#x26; Google Wallet</h4></td><td>Connect your Apple Developer accound and Google Pay  &#x26; Wallet Console to TWC.</td><td><a href="/pages/oGyeqr2714g6XfR58VOE">/pages/oGyeqr2714g6XfR58VOE</a></td><td><a href="/files/ZUoFTnoY83xrJzRzknMC">/files/ZUoFTnoY83xrJzRzknMC</a></td></tr><tr><td><h4>Template Config</h4></td><td>Create and customize your wallet pass templates : colors, logos, field layout, muti-language support.</td><td><a href="/pages/9y0bkRWFXOyn989tjlPL">/pages/9y0bkRWFXOyn989tjlPL</a></td><td><a href="/files/DRl7DXdBdiH0akHVZHqe">/files/DRl7DXdBdiH0akHVZHqe</a></td></tr><tr><td><h4>Wallet Cards Security</h4></td><td>GDPR and CCPA compliant, EU data residency, end-to-end encryption, strict tenant isolation.</td><td><a href="/pages/4OjceSMZvirhikc0vL5e">/pages/4OjceSMZvirhikc0vL5e</a></td><td><a href="/files/8Lnp0SGK5xxVBwsFrdvZ">/files/8Lnp0SGK5xxVBwsFrdvZ</a></td></tr><tr><td><h4>Import &#x26; Export</h4></td><td>Migrate active passes from another provider, update pass data via flat files or export passes to a new provider.</td><td><a href="/pages/yyGb3SdHQ1hoVZAtIqCV">/pages/yyGb3SdHQ1hoVZAtIqCV</a></td><td><a href="/files/N9u59v8LiAfwq5vrWcmp">/files/N9u59v8LiAfwq5vrWcmp</a></td></tr></tbody></table>

**Apple & Google Wallet** credentials define which entity issues passes on each platform. Rather than using shared or platform-default identities, TWC requires brands to connect their own Apple Developer account and Google Pay & Wallet Console. This ensures passes are distributed under the brand's name, with full control over certificates, push notification tokens, and API credentials. These credentials are a prerequisite for any pass issuance.

**Template configuration** is where the visual and structural identity of each pass type is defined. Templates control colors, logos, images, field labels and values, additional information, and links — for both Apple Wallet and Google Wallet. Dynamic content is handled through Liquid (DotLiquid), which allows field values to adapt per-pass without developer intervention. Templates can also be translated into multiple languages, with individual field translation or bulk export and import via Excel.

**Wallet Card Security** documents the security and compliance posture of the platform. Passes and associated personal data are stored exclusively in the European Union, encrypted at rest and in transit, and isolated per tenant. The platform is GDPR and CCPA compliant. Distribution links are cryptographically signed to prevent tampering. This section is the primary reference for security questionnaires and compliance reviews.

**Import & Export** covers scenarios where passes need to move — either into or out of The Wallet Crew. Existing passes from another provider can be migrated to TWC without requiring end-users to reinstall anything. Pass data can also be updated in bulk via flat files uploaded through SFTP. When switching to a new provider, TWC supports exporting passes with the constraints specific to each platform.

These four areas are independent but work together. Completing the Apple & Google Wallet credentials first is the recommended starting point — without them, no pass can be issued regardless of how templates or security settings are configured.


---

# 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:

```
GET https://docs.thewalletcrew.io/configuration/wallet.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.