> 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/loyalty-card-template-configuration.md). # Loyalty Card Template Configuration Personalize a loyalty card template for Apple Wallet and Google Wallet: colors, images, barcode, header and front fields, and back-of-card content. Whether you are a new client who needs to create the template for the passes that will be distributed to customers, or a master of The Wallet Crew who needs to update an existing template, this article is a guided tour of the template designer. The goal is to configure a pass template that reflects the brand identity, displays the right information to customers, and ensures a seamless experience across Apple Wallet and Google Wallet. ## Architecture Apple and Google have their own loyalty pass templates as you can see below. {% tabs %} {% tab title="Apple" %}

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

{% endtab %} {% endtabs %}

	Cover image
Apple pass	design-loyalty-card-apple-example-loyalty-card-3.png
Apple pass	design-loyalty-card-apple-example-loyalty-card-2.png
Apple pass	design-loyalty-card-apple-example-loyalty-card.png

	Cover image
Google pass	design-loyalty-card-capture-d-e-cran-2026-01-26.png
Google pass	design-loyalty-card-capture-d-e-cran-2026-01-26-3.png
Google pass	design-loyalty-card-capture-d-e-cran-2026-01-26-2.png

{% hint style="info" %} **To go further, find all the details of the two versions:** {% endhint %} **Apple:** {% embed url="" %} **Android:** {% embed url="" %} ### How to configure it on The Wallet Crew The Wallet Crew provides a **template designer** that is used to **personalize the loyalty cards** 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 pass** so that customers can pass it on to other people, the “void feature” for the coupons, and a relevant and expiration date that are used for event tickets. The section also **defines the distance** from a relevant latitude and longitude at which the pass is relevant, for **geofencing notifications.**

### Barcode Choose the **type of barcode** that is compatible with the point-of-sale software. The barcode value corresponds to the **identifiers** that allow the card to be identified by the terminal in the store. Finally, the alternate text can be used to display the barcode data in case the barcode cannot be scanned.

### Colors & Images To change the background color of the card, 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 cards are **stacked on top of each other**. Only the header of the card 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 loyalty points, or other relevant information.

### Front fields The front fields are the fields that are used to **display information in the recto of the card**, under the strip image. The label is the same for every user (per language), but the value can be customized to display the name of the customer or the number of points.

{% 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 loyalty card, includes several useful pieces of information for the customer: * How the loyalty program works * Available rewards * Receipts * Personalized offers and messages * The ability to add links, such as the location of their favorite store, a link to update their account and preferences, access to the terms and conditions, etc.

### 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 “issue” and “program name” are **mandatory** 2. Google preconfigures the fields based on their intended values, so it’s best not to enter the customer’s name in the loyalty points field, for example, even if that is how it should appear on the pass 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 three **mandatory fields**: * **Issuer**: the name of the brand or company that issues the pass * **Program name**: it appears on the front of the pass, and is typically the name of the loyalty program * **State**: the state of the pass (active, expired, completed, inactive)

### Multiple devices and holders 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**

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

### Account The account section holds the **name of the customer** and their **identifier**.

{% hint style="warning" %} **Please note that it is an optional field and that a dynamic value cannot be used on the label field.** {% endhint %} ### Additional links This appears on the back of the card, and can carry the **link of a store or a website**.

### Loyalty Points, Rewards and Rewards Tiers Those fields are used to set up the **loyalty points**, and the **rewards** or **rewards tiers** (status of the loyalty program for example).

### Messages This section, located on the back of the loyalty card, includes several **useful pieces of information** for the customer: * How the loyalty program works * Available rewards * The ability to add links, such as the location of their favorite store, a link to update their account and preferences, access to the terms and conditions, etc.

### Value added opportunities This section adds a **small section at the bottom of the loyalty card**. This is used to display offers, or news.

{% hint style="danger" %} **Once the modifications are done, remember to click “save” at the top of the template designer!** {% endhint %} ## FAQ

Do I need to save my configuration and update all the passes?

Once the template has been edited, there are **two options:** * Saving the configuration without pushing an update on all passes: this is the best option if there are a lot of passes. The configuration can be saved and an update scheduled during the night, to avoid the impact of mass updating. * Saving the configuration and pushing an update: this is the best option for tests, or when only a few passes exist in the environment.

How to modify the configuration for another language?

The design of the pass can be modified for each language. Clicking "general" in the menu allows a language to be added. It then appears on the template designer and can be edited.

--- # 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/loyalty-card-template-configuration.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.