> 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/design/generic.md).

# Generic

What is specific to a generic template: a flexible pass for badges, memberships, warranty cards and pickup credentials, with suggested content per use case.

The generic pass is the most flexible type. Use it when the pass does not fit a dedicated type (loyalty card, gift card, offer or event ticket) but still has to be distributed through Apple Wallet and Google Wallet. If in doubt, start from [Pass types & templates](https://docs.thewalletcrew.io/guides-design/design/pass-types-and-templates.md) and pick **Generic** only as a fallback.

This page covers only what is specific to this type. Every setting is described in the [pass template editor](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/template-configuration.md), which also explains how to save and push changes.

<details>

<summary><strong>Real-world examples</strong></summary>

* A company issues staff badges with the employee name in the header and a barcode that the door readers scan.
* A club issues membership cards that are not part of a loyalty program.
* A retailer issues a pickup credential with the order number and the pickup point.

</details>

## Layout of the two wallets

{% tabs %}
{% tab title="Apple" %}

<figure><img src="https://493872178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F96iMF0cPuLTC7ZRnUWG9%2Fuploads%2Fgit-blob-1dc48a3bb7ee92d125ff87d008fa1a7d3f8ee018%2Fdesign-generic-wallet-crew-generic-architecture-apple-nologo.png?alt=media" alt="Apple generic pass layout"><figcaption><p>Apple generic pass layout.</p></figcaption></figure>
{% endtab %}

{% tab title="Google" %}

<figure><img src="https://493872178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F96iMF0cPuLTC7ZRnUWG9%2Fuploads%2Fgit-blob-5e57430aaba210ffc1d7e5c90a492fa87a77582f%2Fdesign-generic-wallet-crew-generic-architecture-google-nologo.png?alt=media" alt="Google generic pass layout"><figcaption><p>Google generic pass layout.</p></figcaption></figure>
{% endtab %}
{% endtabs %}

Reference documentation: [Apple Wallet passes](https://developer.apple.com/documentation/walletpasses) and the [Google Wallet generic class](https://developers.google.com/wallet/reference/rest/v1/genericclass).

## What is specific to a generic pass

### Suggested content per use case

A generic pass has no built-in meaning, so decide what each field says. These suggestions use the Google fields Title, Header and Subheader, and the matching Apple header and front fields. A generic pass also fits vouchers that are not discounts, such as a free item, a perk or an entitlement.

| Use case                 | Header             | Subheader or detail              | Barcode value                |
| ------------------------ | ------------------ | -------------------------------- | ---------------------------- |
| Staff or partner badge   | Name of the holder | Role, site or company            | Badge or employee identifier |
| Membership card          | Name of the holder | Membership level and valid until | Member identifier            |
| Warranty or service card | Product or service | Valid until                      | Serial or contract number    |
| Pickup credential        | Order number       | Pickup point                     | Pickup code                  |

### On Apple Wallet

* **Header.** Put the information that identifies the pass, such as the holder's name, in the header fields, the only ones visible when passes are stacked.
* **Valid dates.** Use **Expiration date** and **Voided** in the General section to end a pass, for example a one-time voucher.
* **Layout.** A generic pass uses the classic generic layout with an optional thumbnail (no strip). Setting an **Artwork (poster background)** turns it into a poster on iOS 27: see [Pass style and layout](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/template-configuration/apple-tab.md#pass-style-and-layout).

### On Google Wallet

* **General.** Title, Header, Subheader and State.
* **Valid time interval and notifications.** Set a start and an end. The expiry notification (48 hours before the end) and the upcoming notification (24 hours before the start) need that interval: see the Generic settings of the [Google tab](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/template-configuration/google-tab.md#generic).

<figure><img src="https://493872178-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F96iMF0cPuLTC7ZRnUWG9%2Fuploads%2Fgit-blob-abf5706d95689604bf52ef6101cb8bf835dd4d72%2Fgeneric-google-general-section-retake.png?alt=media" alt="General section of the Google tab for a generic pass template, with the Header and Subheader fields"><figcaption><p>Check that Title, Header, Subheader and State are all completed.</p></figcaption></figure>


---

# 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/design/generic.md?ask=<question>&goal=<user_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.
