Platform
The Wallet Crew documentation is organized around four main areas. Each section covers a distinct part of the setup and operations flow.
The Platform section covers the foundational settings that apply across the entire account. These are the parameters to configure first — before creating passes, connecting systems, or inviting team members.
General settings define the basic identity of the account: the application title, the favicon displayed on hosted pages, and the languages available for enrolment and pass download pages. These settings are visible to end-users and should reflect the brand's identity from day one.
User access controls who can log into the back office and with what level of permissions. This is where the administrator account is created, team members are invited, and multi-factor authentication (MFA) is enabled. Keeping access well-defined from the start reduces security risks and avoids confusion when multiple people work on the same account.
API keys are required for any backend integration. Each key is scoped to the account and must be included in every API request sent to The Wallet Crew. Keys can be created, rotated, and revoked from this section. Anyone setting up a technical integration will need at least one active API key before making their first call.
Custom domain allows brands to replace The Wallet Crew's default hosted URLs with their own domain — for enrolment forms, pass download pages, and account-linked Wallet journeys. This is a branding decision as much as a technical one: end-users see the brand's domain throughout the experience, not a third-party URL.
These four settings are independent of each other and can be configured in any order. That said, completing General settings and User access first is recommended, as they affect how the rest of the platform behaves for the whole team.