--- title: Defining the metadata of your Wallet Pass framework: walletpasses role: article role_heading: Article path: walletpasses/defining-the-metadata-of-your-wallet-pass --- # Defining the metadata of your Wallet Pass Provide customizable information for your Wallet Pass. ## Overview Overview When designing your Wallet Pass, consider what information is most important to include on the type of pass you’re creating. By defining the metadata of your Wallet Pass, you can optimize the user experience, ensuring that the pass displays all the most helpful information to people. You can even extend the pass experience beyond just the Wallet app, for example, by adding featured actions related to your pass. With metadata, you can: Use semantic tags or pass fields to define what information appears on your pass. Use back fields and custom values to include additional information along with your pass. These fields are ideal for information that may not fit on the design of the pass itself, but that someone may still want to access when looking at their pass. Define your pass actions, which are quick actions that someone can see when looking at your pass in the Wallet app. These actions can include event guides, links to music, links to book a hotel or flight, or even a link to open a relevant location in Maps and get directions. Add semantic tags Passes with semantic tags dynamically lay out pass fields based on metadata that you provide, prioritizing the most important information in specific positions in the layout. Beyond the list of tags required for a pass to function, semantic passes support optional tags for features such as pass actions and the additional information tile. When creating your semantic passes, remember to support backward compatibility by including pass fields in addition to the semantic tags, ensuring that customers on earlier versions of the OS can still view the pass on their devices. Boarding passes Airline boarding passes in iOS 26 and later use semantic tags to display the most relevant information for customers. Semantic tags are broken up into five categories, which display on the pass depending on relevance: Flight details: Includes information such as flight number, departure and arrival information, boarding details, and any flight delays. The system displays the most important flight details in the header fields in the top-right corner of the pass, and the other flight details display below the passenger details. Passenger details: Includes passenger names, loyalty programs and priority status, and any special service requests such as service animals, wheelchairs, carry-on pets, or whether the passenger is an unaccompanied minor. The most relevant of these tags display as badges beneath the customer’s name. Airports: Contains information about the passenger’s departure and arrival airports, including airport codes, city names, time zones, and security codes. Security: Indicates whether the passenger is a member of TSA PreCheck, Global Entry, CLEAR, or other similar programs. Seats: Indicates the type of seat that a passenger booked and includes seat number, row number, level, section, seat type, and description of the seat. For a more detailed guide on boarding passes, see Creating an airline boarding pass using semantic tags. Event tickets Poster event tickets utilize semantic tags to automatically lay out relevant event information in your pass design. Semantic tags are only available for sports and live performance event tickets; all other events utilize nonposter event tickets with pass fields. note: Certain semantic tags are required to display poster event tickets, and if you don’t include them, the system displays a nonposter event ticket instead. For more information, see Add the required semantic tags. For sports event tickets, there are three categories of semantic tags: Event details: General information about the event such as the event name, venue name, date, time, and admission level. The most relevant event details display in the top-right corner of the pass, whereas the other event details display in the bottom left. Match details: Specific to sports event tickets, this section of semantic passes includes information about the sports league, home team, and away team. Match details display in the top-left corner of the pass and typically show the abbreviation of the two teams playing. Seats: These tags include information about the seat number, level, row, section, and any other relevant details. You can also assign a section color to help people easily find their assigned seat or seating area. This color replaces the material strip at the bottom of the pass. For live performance event tickets, there are three categories of semantic tags, which differ slightly from sports event tickets: Event details: General information about the event such as the event name, venue name, date, time, and admission level. The most relevant event details display on the top-right corner of the pass, while the other event details display on the bottom left. Performance details: The name of the performer and their artist ID. For events with more than one artist, you can include multiple artists in this section. These details aren’t displayed on the pass itself, but allow someone to locate more information or find music from the artists with Pass Actions in the Wallet app. Seats: Information about the seat number, level, row, section, and any other relevant details. You can also assign a section color to help people easily find their assigned seat or seating area. This color replaces the material strip at the bottom of the pass. For details about creating a poster event ticket, see Creating a poster event pass using semantic tags. Add custom values In addition to the standard semantic tags, you can also provide your own custom values for a pass. Note, though, that custom fields appear last in the hierarchy of semantic tags, so all other semantic tags appear in the pass design before custom values. These values can only appear on the pass depending on the number of other semantic tags already included. If there’s no space on the pass for your custom values, they instead appear as standalone fields when someone views the pass in the Wallet app. Viewers can click through and see the details of all your custom value fields. Provide content for your pass fields Pass fields are static areas of the pass layout where you can add information with specific attributes related to the pass content. Pass fields have different layouts depending on the pass style. Boarding passes Airline boarding passes before iOS 26 and all other types of boarding passes use pass fields to lay out their content. The header of the pass contains fields for a logo, logo text, and header. You can use the logo and logo text fields to identify your brand. The header field contains information such as gate number and flight details, which someone may want to view at a glance on your pass. The primary fields display airport codes. The auxiliary and secondary fields display all other relevant information, such as dates and times of the trip, flight class, terminals, gates, boarding groups, and seat number. note: Unlike other pass types, on boarding passes, the auxiliary fields appear above the secondary fields. For a more details on boarding passes, see Creating an airline boarding pass using semantic tags. Coupons Setting the coupon pass style provides data that Wallet displays automatically, such as business information, offer expiration date, terms and conditions, store locations, and other helpful information. The pass’s style determines the overall visual appearance of the pass and the template for placement of information on the pass. The following illustration shows the layout and placement of fields for the coupon pass style: For details on creating a coupon, see Creating a coupon pass. Event tickets Nonposter event tickets use pass fields for their layout content. Whereas live performances and sports event tickets may use semantic poster event tickets, other events such as movies, conferences, conventions, workshops, social gatherings, or generic events use pass fields for their layouts. For more information about using pass fields on nonposter event tickets, see Ensure backward compatibility. Store cards A store card pass can display a logo, strip images, and a barcode, and it can have up to four secondary and auxiliary fields, all displayed on one row. The text length in each pass field determines how many fields appear on the front of the pass. If the text is too long, Wallet won’t display all of it. For details on creating a store card, see Creating a store card pass. Generic passes Both the generic pass and the generic poster pass use pass fields, but they have slightly different layouts for the fields. Generic poster passes put the primary focus on the background image of the pass, which is why the layout is slightly different than the generic pass. On a generic pass, the primary fields appear larger in the top section of the pass. They don’t extend across the pass to leave room for the thumbnail image. Generic passes also allow for up to four secondary fields and four auxiliary fields. Unlike other pass types that collapse secondary and auxiliary fields into one section, generic passes keep them separate, allowing for a total of eight displayed fields. For details on how to create a generic pass, see Creating a generic pass. Add any relevant back fields Back fields are available for every pass type, but they don’t appear in the layout of the pass itself. Use this field to provide additional, noncritical information. Back fields are only visible when someone views their pass in the Wallet app and selects Pass Details. Add featured actions You can also include featured actions with your pass. These actions display as cards when viewing your pass in the Wallet app and you can use them for quick calls to action for the viewer. Featured actions make it easy for someone to quickly find relevant information related to your pass, such as directions to a business location, music related to a live performance, or even quick links to book tickets. Each featured action includes an icon, string, and action. You define your icon from available SF Symbols; be sure to pick one that accurately represents the action and that viewers can easily understand at a glance. Also, when choosing a symbol, prefer circular, filled icons. Your string is a brief call to action and your action label informs people what happens when they click the link; for example, your pass may redirect them to a website or the Maps app. Certain predefined featured actions are recommended for specific pass types, such as View Schedule for an event ticket or View Membership Benefits for a membership pass. See the full list of available featured actions below: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ## See Also ### Essentials - [Creating a pass with Pass Designer](walletpasses/creating-a-pass-with-pass-designer.md) - [Creating the Source for a Pass](walletpasses/creating-the-source-for-a-pass.md) - [Building a Pass](walletpasses/building-a-pass.md) - [Distributing and updating a pass](walletpasses/distributing-and-updating-a-pass.md) - [Pass](walletpasses/pass.md) - [PassFields](walletpasses/passfields.md)