> 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/navigate/guides.md). # Guides The Wallet Crew guides cover the full lifecycle of an Apple Wallet and Google Wallet program. They help Brands move from pass design and configuration to distribution, geolocated engagement, monitoring, and scan validation.
Real-world examples * A retail Brand configures a loyalty card, publishes an enrolment form, then triggers geolocated notifications near stores. * A ticketing Brand configures wallet credentials, distributes tickets by email, then validates entry with real-time scans. * A gift card program synchronizes balances, monitors pass activity, and keeps the same installed pass current over time.
### Browse the core guides Each guide below covers one operational area. Start with Configuration when the wallet project is still being set up. Start with Design or Enrolment when the technical foundation already exists.

:paintbrush:

Design

Define how the pass looks and behaves in Apple Wallet and Google Wallet. Structure the layout, branding, fields, links, and barcode without moving core business data out of existing systems./spaces/96iMF0cPuLTC7ZRnUWG9/files/qdIqE5TBBPY4EdPrF2PP

:gear:

Configuration

Prepare the wallet foundation before launch. Configure issuer accounts, certificates, custom domains, template settings, and operational defaults for secure production use./spaces/DJrf9G0l7ArnvuwEH0a8/files/s9rxAemSbsPmCa9nDuc4

:layer-plus:

Enrolment

Control how customers add a pass to their phone. Compare hosted forms, website embeds, email flows, QR codes, and in-app entry points to improve conversion and data quality./spaces/lFokgwgJiwLXu7G8MVSJ/files/cZKS1reW7O3wVarjo9zU

:bell-ring:

Engage & animate

Keep the installed pass useful after it is saved. Use pass updates, push notifications, geolocated alerts near stores or venues, and privilege logic tied to time, balance, or counters./spaces/97ZAXMtqOjhvBBCfpmcE/files/Sl5PoYQ2k0d6X4fhFwq1

:chart-line:

Monitoring

Track what happens after issuance. Review installation status, pass activity, privilege usage, and synchronization signals needed to operate wallet programs at scale./spaces/EsokFUBfsbM9mlwavmMB/files/qCOJ673uQWwaBH2rpMJ1

:barcode-read:

Scan & validate

Validate passes at a gate, POS, counter, or service desk. Use real-time scans to read the pass, display the right privileges, and prevent duplicate or invalid redemption./spaces/iqBD4M0nHFMaFeKR75p9/files/P0nzScB9jPYqm12wYMmw
### How to use this page This page works as the shortest route into the operational guides. It is useful when the goal is already known, such as configuring Apple Wallet certificates, launching an Add to Wallet flow, enabling location-based notifications, or validating passes in store or at event entry. ### FAQ
Where should a new wallet project start? Most projects start with Configuration, then move to Design and Enrolment. That sequence reduces launch risk because wallet credentials, domains, and provider access are validated before distribution starts.
Which guide covers location-based wallet experiences? Use Engage & animate for geolocated notifications and other post-install triggers. That area also covers push notifications and privilege logic that changes over time.
Which guide covers in-store or event validation? Use Scan & validate when the pass must be checked at a door, POS, counter, or service point. That guide covers staff-facing scan flows and real-time redemption control.
--- # 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/navigate/guides.md?ask=&goal= ``` `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.