> 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 andLoyalty templates work together. The starting point before configuring any pass in The Wallet Crew.


/pages/1Y9SQXpCfnWP5gAnv8m3/files/weh5l8BbCbhvLQ6ls2y1

:user-group-crown:

Loyalty card

Configure a loyalty card template: member ID, tier, points, barcode. Designed for programs that update over the customer lifecycle./spaces/96iMF0cPuLTC7ZRnUWG9/pages/1GWExrYIqrVx4rDGznyu/files/CqC6grBjKa5xbaclV6Em

:tickets-perforated:

Event ticket

Set up an event ticket pass: venue, date, seat, gate, and scannable barcode. Supports real-time updates for schedule changes./spaces/96iMF0cPuLTC7ZRnUWG9/pages/n9Zihv9BSO1ZtnDvEc8Q/files/hZuZXywBplqNZZ0x1He2
Cover image

:hand-holding-heart:

Gift card

Set up a time-bound coupon or promotion pass: expiry date, conditions, and a redemption code. Typically single-use, with status updates on redemption./spaces/96iMF0cPuLTC7ZRnUWG9/pages/pXFx6BySfF0t4YT8jiV3/files/RD44AcRBINzUGeJvsMcc

: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./spaces/96iMF0cPuLTC7ZRnUWG9/pages/c7sqOTHuDOx7FTEIf5fR/files/ESVdgr7QmI0sav0hH4lr
:draw-circle:

Generic

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


/spaces/96iMF0cPuLTC7ZRnUWG9/pages/TgdsO8PUTUHlpoxB0u5M/files/oowYwZaATTjLycodgPzA
#### **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** and **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 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/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 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.