> 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/guides-design/the-wallet-crew-design-guides.md). # Design Guides Five sections covering the full lifecycle of a wallet pass program, written for the people who run it day to day.
Cover image

:house-crack:

General

Understand how pass types and templates work together. The starting point before configuring any pass in The Wallet Crew.


Generalhttps://493872178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F96iMF0cPuLTC7ZRnUWG9%2Fuploads%2FBa5l6D9E56Wiu9IHH96U%2Fgeneral.svg?alt=media

:user-group-crown:

Loyalty card

Configure a loyalty card template: member ID, tier, points, barcode. Designed for programs that update over the customer lifecycle.Loyalty Cardhttps://493872178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F96iMF0cPuLTC7ZRnUWG9%2Fuploads%2F0HDxuFktc96J8aSBFVEs%2Floyalty-card.svg?alt=media

:tickets-perforated:

Event ticket

Set up an event ticket pass: venue, date, seat, gate, and scannable barcode. Supports real-time updates for schedule changes.Event tickethttps://493872178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F96iMF0cPuLTC7ZRnUWG9%2Fuploads%2FcGNC4W4ZcrAp5QoDwtA1%2Fevent-ticket.svg?alt=media
Cover image

:hand-holding-heart:

Gift card

Issue a stored-value gift card pass: current balance, redemption code, and top-ups. The balance updates in the wallet after each purchase, until it runs out or the card expires.Gift cardhttps://493872178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F96iMF0cPuLTC7ZRnUWG9%2Fuploads%2Fu0AWISX4kG93y4sb9ZuX%2Fgift-card.svg?alt=media

:tags:

Offer

Set up a time-bound coupon or promotion pass: expiry date, conditions, and a redemption code. Typically single-use, with status updates on redemption.Offerhttps://493872178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F96iMF0cPuLTC7ZRnUWG9%2Fuploads%2Ff6r0h44WVcZW8nKATQaP%2Foffer.svg?alt=media
:draw-circle:

Generic

A flexible pass for cases that don't fit standard types: staff badges, membership cards, warranty cards, or pickup credentials.


Generichttps://493872178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F96iMF0cPuLTC7ZRnUWG9%2Fuploads%2F0VP9AANHnz01qeU4OwKY%2Fgeneric.svg?alt=media
#### **Design** Every wallet pass starts with a choice: which pass type fits your use case, and how should it be configured? The Design section walks through the building blocks available in The Wallet Crew, from foundational concepts to ready-to-use templates for common scenarios. **Pass Types & Templates** is the starting point — it explains how types and templates work together before you configure anything. From there, dedicated guides cover each major pass type: **Loyalty Card** templates handle member ID, tier, points, and barcode for programs that evolve over a customer's lifecycle. **Event Ticket** templates manage venue, date, seat, and gate information, with support for real-time updates when schedules change. **Gift Card** templates carry a stored value — current balance, redemption code, and top-ups — with the balance updating in the wallet after each purchase. **Offer** templates cover time-bound promotions with expiry dates, redemption conditions, and status updates once used. For everything else — staff badges, membership cards, warranty cards, pickup credentials — the **Generic** pass type offers a flexible structure that adapts to non-standard cases. Together, these guides give you the full toolkit to design a pass that matches your business model, whether you're building loyalty programs, ticketing, or one-off use cases. --- # 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/guides-design/the-wallet-crew-design-guides.md?ask=&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.