> 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/event-ticket.md). # Event ticket Configure an Event ticket template for Apple Wallet and Google Wallet: branding, visuals, venue, placement, and real-time event information. Whether you are a new client who needs to create the template for the tickets that will be distributed to attendees, 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 ticket template that reflects the brand identity, clearly displays essential event information, and ensures a smooth and secure experience across Apple Wallet and Google Wallet. ## Architecture Apple and Google have their own ticket pass templates as you can see below. {% tabs %} {% tab title="Apple" %}

Architecture - Apple — Check where the event name, date, seat and barcode sit in the Apple ticket layout.

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

Architecture - Google — Check how Google splits the same ticket into venue, placement and confirmation areas.

{% endtab %} {% endtabs %}

	Cover image
Apple ticket	design-event-ticket-image-2026-02-12t154141-948-removebg-preview.png
Apple ticket	design-event-ticket-image-2026-02-12t154147-926-removebg-preview.png
Apple ticket	design-event-ticket-image-2026-02-12t154144-942-removebg-preview.png
Google ticket
Google ticket
Google ticket	design-event-ticket-capture-d-e-cran-2026-02-12.png

{% 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 event tickets** 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, 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.**

Event ticket - General section Apple — 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 event ticket to be identified by the control terminal at the entrance. Finally, the alternate text can be used to display the barcode data in case the barcode cannot be scanned.

Event ticket - Barcode Apple — Check that the barcode type matches what the access-control scanners accept.

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

Event ticket - Header fields Apple — Check that the event date is the value shown in the header field.

### Front fields The front fields are the fields that are used to **display information in the recto of the ticket**, 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 event or the customer's seat.

Event ticket - Front field 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 event ticket, includes several useful pieces of information for the customer: * How to get to the event * Information regarding entrance * Receipts * The ability to add links, such as a link to listen to the artists, access to the terms and conditions, etc.

Event ticket - Backfields Apple — Check that the access information and the terms and conditions link are both 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 “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 Event name 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 ticket * **Event name**: it appears on the front of the pass, and is typically the name of the event * **State**: the state of the ticket (active, expired, completed, inactive)

Event ticket - Google general — Check that Issuer, Event name and State are all completed.

Event ticket - Barcode Google — Check that the barcode value and its alternate text match the ticket identifier.

### 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**

One user one device — Check that the sharing option selected matches the ticketing policy for the event.

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

Event ticket - Colors and Images Google — Check that the hero image and logo render correctly against the chosen background color.

### Venue A section to enter the detail of where the event will take place.

Event ticket - venue Google — Check that the venue name and address match the event listing.

### Placement The gate, row, seat and section of the customer's ticket can each be defined. Each field is optional. {% hint style="warning" %} **To personalize the placement fields, ask the tech team which dynamic value to write.** {% endhint %}

Event ticket - Placement Google — Check that gate, row, seat and section each use a dynamic value.

### Confirmation On the Google template, a confirmation code can also be defined and displayed when the event requires one. This is an optional field; when there is no confirmation code, select "Unspecified".

Event ticket - Confirmation Google — Check that the confirmation code field is either mapped or set to Unspecified.

### Additional links, Smart tap and Valid Time Interval **Additional links** can be added to the customer's ticket, for example the event website link. The **Smart tap feature** can also be configured, so that customers simply **validate their ticket** by tapping their device on a compatible hardware terminal. Finally, the Valid time interval section **defines a start and an end date** for the event.

Event ticket - Smart tap Google — Check the Smart tap setting and the start and end dates of the event validity window.

### Messages This section, located on the back of the event ticket, includes several useful pieces of information for the customer: * How to get to the event * Information regarding entrance * Receipts * The ability to add links, such as a link to listen to the artists, access to the terms and conditions, etc.

Event ticket - Backfields Google — Check that each message has a title and body, and that no placeholder text remains.

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

Event ticket - Value Added Opportunity Google — Check that the bottom section content is still current before the event.

### Other sections On Google, there are four other sections: * **Face Value**: The price of the ticket * **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 %} ## FAQ

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

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/event-ticket.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.