> 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 Configure a Generic pass template for Apple Wallet and Google Wallet. Use it for flexible membership cards, utility passes, and custom layouts. The Generic pass is the most flexible pass type available. It is designed for use cases that don’t naturally fit into one of the dedicated templates such as loyalty cards, gift cards, offers, or tickets. When a pass doesn’t match a predefined category but still needs to be distributed through Apple Wallet or Google Wallet, the Generic template is likely the right choice. Use a Generic pass for a flexible layout that does not fit a dedicated template (loyalty, gift card, offer, ticket). **Typical use cases:** * Membership cards that are not loyalty programs * Partner or staff badges * Utility passes (warranty card, pickup card, service card) * Vouchers that are not discounts (free item, perk, entitlement) If in doubt, start from [Pass types & templates](/guides-design/design/pass-types-and-templates.md) and pick **Generic** only as a fallback. ### Architecture (Apple vs Google) Apple and Google each provide their own Generic template structure. {% tabs %} {% tab title="Apple" %}

The Wallet Crew generic - Architecture Apple — Apple generic pass template

{% endtab %} {% tab title="Google" %}

The Wallet Crew generic - Architecture Google — Google generic pass template

{% endtab %} {% endtabs %} {% hint style="info" %} **To go further, find all the details of the two versions:** {% endhint %} **Apple** {% embed url="" %} **Google** {% embed url="" %} ### How to configure it on The Wallet Crew The Wallet Crew provides a template designer that is used to personalize the generic passes distributed to customers. Let’s see in detail how to personalize each section. ## Apple **Let’s take a look at the different sections of the Apple template designer.** ### General section The general section has two mandatory fields: * **Description**: a brief description of the pass, that will appear on the back of the card * **Organization name**: the name of the company or brand issuing the pass It is also possible to put a text next to the logo, **activate the sharing of the ticket** so that customers can pass it on to other people, and the **“void feature” for the pass**. The section also **defines the distance** from a relevant latitude and longitude at which the pass is relevant, for **geofencing notifications.**

The Wallet Crew Generic - Apple general — Confirm that Description and Organization name are both filled in before saving.

### Barcode Choose the **type of barcode** that is compatible with the control hardware. The barcode value corresponds to the **identifiers** that allow the pass to be identified in store. Finally, the alternate text can be used to display the barcode data in case the barcode cannot be scanned.

The Wallet Crew generic - Barcode Apple — Check that the barcode type matches what the scanning hardware accepts.

### Colors & Images To change the background color of the pass, simply **add the color code in the fields** provided for this purpose. To add an image, upload it from the device in use. ### Header Fields This section is particularly important in the Apple version, as the generic passes are **stacked on top of each other**. Only the header of the generic pass remains visible. Therefore, it is important that this section catches the eye and encourages clicking on the card, especially by displaying the most important information such as the name of the customer.

The Wallet Crew Generic - Header fields Apple — Check that the header field carries the information that identifies the pass in a stack.

### Front fields The front fields are the fields that are used to **display information in the recto of the pass**, under the strip image. The label is the same for every user (per language), but the value can be customized to display the expiry date, for example.

The Wallet Crew generic - Front fields Apple — Check that each front field has a static label and a dynamic value.

{% hint style="warning" %} **To personalize the front fields, ask the tech team which dynamic value to write.** {% endhint %} ### Backfields This section, located on the back of the pass, includes several useful pieces of information for the customer: * Expiry date * Information regarding the brand * Receipts * The ability to add links, such as a website link

The Wallet Crew generic - Backfields Apple — Check that the brand information and any terms and conditions link are present.

### Other sections On Apple, there are four other sections: * **Locations**: Used for geofencing notifications. * **Beacons**: Also used for geofencing notifications. * **Associated store identifier**: Used to link an application published on the Apple Store * **NFC**: A feature that allows customers to exchange digital content, and connect electronic devices with a touch. {% hint style="warning" %} **Please contact The Wallet Crew to activate these features** {% endhint %} {% hint style="danger" %} **Once the modifications are done, remember to click “save” at the top of the template designer!** {% endhint %} ## Google **The Google template designer is a bit different than the Apple one.** {% hint style="warning" %} **A few things worth knowing before configuring the Google template:** {% endhint %} 1. Some fields such as “General ” and “Header” are **mandatory** 2. Google preconfigures the fields based on their intended values 3. Dynamic values (e.g., {{firstName}}) should be **placed in dedicated dynamic fields**. ‘Label’ fields are intended for static text only. **Let’s take a look at the different sections.** ### General section The general section has four **mandatory fields**: * **General**: the title of the pass. * **Header:** the header of the pass * **Sub Header :** the subheader of the pass, such as location where this pass can be used * **State:** the state of the object.

The Wallet Crew generic - General Google — Check that General, Header, Sub Header and State are all completed.

### Security Configuring a template means deciding **whether the customer can share their pass or not**. Google offers three options: * **Multiple holders**: it means that the customer can share their pass with anyone * **One user all device**: a customer but with several devices (a watch for example) * **One user one device**

The Wallet Crew generic - Security Google — Check that the sharing option selected matches how the pass is meant to be used.

### Colors & Images To change the background color of the pass, simply **add the color code in the fields** provided for this purpose. To add an image, upload it from the device in use.

The Wallet Crew Generic - Colors and images Google — Check that the hero image and logo render correctly against the chosen background color.

#### Additional links, Smart tap and Valid Time Interval **Additional links** can be added to the customer's pass, for example the event website link. The **Smart tap feature** must also be configured, so that customers simply **validate their pass** by tapping their device on a compatible hardware terminal. Finally, the Valid time interval section **defines a start and an end date** for the pass. ### Value added opportunities This section adds a **small section at the bottom of the pass**. This is used to display offers, or news.

The Wallet Crew Generic - Value added opportunities Google — Check that the bottom section content is still current before the pass is distributed.

### Other sections On Google, there are three other sections: * **App links**: Used to add a link for an application * **Homepage**: Used to add the link of the event website * **Locations**: Used for geofencing notifications {% hint style="danger" %} **Once the modifications are done, remember to click “save” at the top of the template designer!** {% endhint %} ### Next steps * For design guidelines, start with [Card design](/configure/advanced-configuration/wallet/template-configuration/cards-design-colors-images-and-fields.md). * To distribute the pass, use [Add to Wallet on a website](/guides-enrolment/enrolment/on-your-website.md). --- # 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/design/generic.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.