> 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/configure/advanced-configuration/wallet/template-configuration/apple-tab.md).
# Apple tab
Configure how passes of a template look and behave in Apple Wallet: style, poster layout, barcode, colors, images, fields, locations, NFC and event guide.
The Apple tab defines everything Apple Wallet renders for passes of the template. Apple Wallet uses a fixed set of pass styles, each with its own zones for images and fields, so the sections available on this tab depend on the type of the template and on the layout chosen. The style is decided by the type of the template; the mapping is in [Settings by type](/configure/advanced-configuration/wallet/template-configuration.md#settings-by-type).
The Apple tab, with its sections on the left and the Apple Wallet preview on the right.
## Pass style and layout
### Poster layout
The poster layout is the full-height design introduced with iOS 27, built around a large artwork. **Use new poster layout** turns it on for Customer card, Event ticket and Stamp card templates. Generic templates always show the poster settings and are drawn as a poster once an artwork is set; Gift card and Offer templates never use the poster layout. Sections and fields that exist only in the poster layout carry a **Poster - iOS 27+** chip.
Turning the option off removes the poster-only settings. When some were filled, a confirmation ("Turn off the poster layout?") lets them be kept off or restored; turning the option back on before saving also restores them.
Older iPhones keep showing the classic layout, which is why the classic settings, such as the strip image, stay configured next to the poster ones. The preview switches between the two layouts from its view menu.
## General
This section holds the identity and validity of the pass in Apple Wallet.
* **Logo text**: text displayed next to the logo. **Event logo text** replaces it on poster event tickets.
* **Description** (required, localizable): a brief description of the pass, used by the iOS accessibility technologies.
* **Organization name** (required).
* **Grouping identifier**: groups related passes together on the Lock Screen and in Wallet.
* **Sharing prohibited**: disables sharing of the pass.
* **Use new poster layout**: see [Poster layout](#poster-layout).
* **Suppress strip shine**: prevents the sheen older iOS versions add to the strip image.
* **Use automatic colors** (poster layout): iOS derives the foreground and label colors from the artwork, instead of the configured colors. Untick it to force the brand colors.
* **Suppress header darkening** (poster layout): prevents iOS from darkening the header of the poster to improve legibility.
* **Voided**: indicates that the pass is void, for example a one-time coupon already redeemed. Wallet moves a voided pass to Expired.
* **Relevant date**: when the pass becomes relevant, for example the start time of a movie. Recommended for event tickets.
* **Expiration date**: when the pass expires. Wallet moves an expired pass to Expired.
* **Max distance**: the maximum distance in meters from a location within which the pass is relevant.
## Barcode
The barcode is what a scanner reads at the checkout or the entrance. The section sets its **Type**, its **Barcode value** (usually an identifier of the pass) and an **Alternate text**, displayed near the barcode, for example a readable version of the value in case the barcode does not scan.
Supported types are QR, PDF417, Code128 and Aztec on every iOS version. Code 39, Codabar, EAN-13 and ITF / I2of5 require iOS 27; a QR code fallback is automatically included for older devices. Check that the in-store terminals can read the chosen format on a phone screen.
When the barcode value is used to find the pass with Pass Scanner, turn on [Persist scannable data](/configure/advanced-configuration/wallet/template-configuration/general-tab.md#scannable-data) on the General tab.
## Colors
Colors keep the pass consistent with the brand and readable:
* **Background**, **Foreground** (values) and **Label** colors;
* **Footer background** (poster layout).
The preview checks the contrast between values or labels and the background, and reports it below 3:1. The check is skipped when automatic colors are on.
## Images
The images available depend on the type and layout. The helper text of each image in the editor gives its exact size and how Wallet crops it.
| Image | Used by |
| ------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Icon** (required) | All passes. Shown in notifications, in emails with the pass attached and on the lock screen. |
| **Logo** | All passes, top left of the classic layout. Wallet fits it into 286 × 50 points. |
| **Strip** | Customer card, Stamp card, Gift card, Offer and Event ticket, behind the primary field. Not shown by generic passes and posters, but kept for the classic layout. |
| **Thumbnail** | Generic passes, and event tickets without a strip. |
| **Background (classic event ticket)** | Classic event tickets. Wallet blurs it behind the card. |
| **Artwork (poster background)** | Poster layout: the full-height background. |
| **Logo (poster layout)** | Poster layout, top left. |
| **Secondary logo** | Poster event tickets, bottom right. |
### Stamp images
Stamp card templates add one image per stamp count under **Images → Stamp images**: an **Apple strip** for each count and, when the poster layout is on, an **Apple poster** artwork for each count. The number of images, their sizes and the other rules are on the [Stamp card](/guides-design/design/stamp-card.md#stamp-images) page.
## Fields
Fields carry the text of the pass. Apple Wallet places them in zones that depend on the style and layout:
* **Header fields**, visible even when passes are stacked in Apple Wallet;
* **Front fields**: Primary, Secondary and Auxiliary fields;
* **Summary fields** (poster passes other than event tickets): shown below the barcode, where they take the place of the primary fields. The classic layout keeps its own primary field over the strip, so both are configured;
* **Footer fields** (poster layout);
* **Additional info fields** (poster event tickets): shown in the "Additional ticket information" page. With the classic layout, iOS 27 groups them in an "Additional Pass Info" tile and earlier versions show nothing, so anything every device must display goes in front or back fields;
* **Back fields**, shown in Pass Details.
Each field has a **Label**, a **Value** and a **Text alignment**. The label is the same for every holder (per language); the value can be customized, for example with the name of the event or the customer's seat. **Format** shows the value as a number (decimal, percent, currency…) or a date and time, formatted on the holder's phone in their language; turned off, the value shows as written. **Notify on change** shows an alert on the holder's device when the value changes; its change message must contain `%@`, which is replaced with the new value. For most cases, an automation with a notification is preferable.
## Locations and beacons
**Locations** (label, latitude, longitude, altitude) and **Beacons** (Bluetooth Low Energy beacons, with a UUID, major and minor identifiers) make the pass relevant near a store or venue. The label of a beacon is the text displayed on the lock screen when the pass is relevant, for example "Store nearby on 1st and Main". **Max distance** in the General section limits the distance from a location.
## App and store identifiers
**Associated store identifiers** are the App Store identifiers of the apps associated with the pass (for example 123456789); a link to launch the app is shown with the pass. Poster event tickets also have **Auxiliary store identifiers**, for apps linked to the ticket.
## Action links (event guide)
Poster event tickets can show an **event guide**: a page of useful actions around the event. The **Action links** section lists them: transfer, sell or manage the ticket, add-on experiences, order food, merchandise, purchase parking, parking information, directions, transit information, accessibility, bag policy, and the venue's email, phone and website.
Apple Wallet shows the event guide only when all conditions are met:
1. the ticket is drawn as a poster: it uses the poster layout, with an artwork and an event name, plus both team abbreviations for a sports event or a performer for a live performance;
2. the semantic tags set the venue doors-open date or the tailgating policy;
3. at least one action link is set.
A poster event ticket missing an artwork or a required semantic tag is drawn with the classic layout instead. The preview checks name what is missing.
## NFC
NFC-enabled passes can send their information to a compatible terminal, for example a reward card read during an Apple Pay transaction. The section sets the NFC **Message**. It requires an NFC-compatible Apple certificate: otherwise the section is shown as "NFC (certificate not compatible)". When NFC is not set up for the tenant, the section says so and links to the setup; passes are issued without NFC until it is. With an NFC message, Wallet moves the barcode off the front: it is only in Pass Details.
## Featured actions
Featured actions appear as cards below the pass in Wallet, at most two per pass. They are ignored on iOS 26 and earlier, so important links are best duplicated in back fields. Each action has an **Action type**, a **URL** (web link, deep link, `tel:` link or maps link) or, for "Go to location", an Apple Maps **Place**, and an optional **Icon (SF Symbol)**.
Available types: View schedule, Watch trailer, Listen to music, Call, Go to location, Add to balance, Order delivery or pickup, Shop online or in-app, View membership benefits, Book an appointment, Book a car, Book a flight, Book a stay, View Offers & Rewards.
Poster event tickets use the event guide instead of featured actions. The **Place** of "Go to location" is searched in Apple Maps or pasted as an Apple Maps link or Place ID; the Apple Place ID is stored and checked with Apple Maps.
## Semantic tags
Semantic tags describe the pass in a structured way so that Apple Wallet can use the information, for example to draw a poster event ticket and its event guide. They are grouped into Event details, Venue, Media (Apple Music), Sports (event ticket), Amounts, Wi-Fi networks, Seats and Event date info.
## FAQ
Why does the event ticket not use the poster layout on the phone?
See [Action links (event guide)](#action-links-event-guide). The preview checks name what is missing.
Why is the event guide not shown?
See [Action links (event guide)](#action-links-event-guide). The preview checks name what is missing.
---
# 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/configure/advanced-configuration/wallet/template-configuration/apple-tab.md?ask=&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.
