This documentation is currently under development. Certain sections are not yet complete and will be added shortly.
Ctrlk
HomeDocumentation
For the complete documentation index, see llms.txt. This page is also available as Markdown.
BrandTemplateApple walletGoogle WalletSecurity

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.

Cover

Apple & Google Wallet

Connect your Apple Developer accound and Google Pay & Wallet Console to TWC.

Cover

Template Config

Create and customize your wallet pass templates : colors, logos, field layout, muti-language support.

Cover

Wallet Cards Security

GDPR and CCPA compliant, EU data residency, end-to-end encryption, strict tenant isolation.

Cover

Import & Export

Migrate active passes from another provider, update pass data via flat files or export passes to a new provider.

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.