People use their cards and passes in Wallet to make Apple Pay purchases, track their orders, confirm their identity, and streamline activities like boarding a plane, attending a concert, or receiving a discount.
When you integrate Apple Wallet into your app, you can create custom passes and present them the moment people need them, securely verify an individual’s identity so they can access personal content, and offer detailed receipts and tracking information where it’s most convenient. For developer guidance, see Wallet.
Passes are digital representations of information that people can add to Wallet, like event tickets, boarding passes, membership reward cards, and coupons.
Offer to add new passes to Wallet. When people do something thatan action results in a new pass —pass, like checking into a flight, purchasing an event ticket,ticket or registering for a store reward program —program, you can present system-providedsystem UI that helps them addadds the pass to Wallet with one tap (for developer guidance, see addPasses(_:withCompletionHandler:)). If people want to reviewtap. For frequent, predictable actions like checking in for a pass before adding it,flight, you can displayadd passes in the background after a custom view that displays the pass and providesperson grants a one-time authorization, so they don’t need to tap an Add to Apple Wallet button; forbutton each time. Wallet notifies the person whenever a pass is added. If someone wants to review a pass first, you can show a custom view with an Add to Apple Wallet button. For developer guidance, see addPasses(_:withCompletionHandler:), PKPassLibrary.Capability.backgroundAddPasses, and PKAddPassesViewController.
Help people add a pass that they created outside of your app. If people createsomeone creates a pass using your website or another device, suggest adding it to Wallet the next time they open your app. If people decline your suggestion, don’t ask them again.
Add related passes as a group. If your app generates multiple passes, like boarding passes for a multi-connection flight, add all passes at the same timeonce so people don’t have to add each one individually. If people can receiveyour website distributes a group of passes from your website —passes, such as a set of tickets for an event —tickets, bundle them together so that people can download them all of them at one time.once. For developer guidance, see Distributing and updating a pass.
Display an Add to Apple Wallet button to let people add an existing pass that isn’tnot already in Wallet. If peoplesomeone previously declined your suggestion to add a pass to Wallet — or if they removed the pass — a button makes it easy to add itthe pass if they change their minds.mind. You can display an Add to Apple Wallet button wherever the corresponding pass information appears in your app. For developer guidance, see PKAddPassButton. You can also display anAn Add to Apple Wallet badge in an email or on a webpage;is also available for emails and webpages; for guidance, see Add to Apple Wallet guidelines.
Let people jump from your app to their pass in Wallet. Wherever your app displays information about a pass that exists in Wallet, you can offer a link that opens it directly. Label the link something like “View in Wallet.”
Tell the system when your pass expires.passes expire. Wallet automatically hides expired passes to reduce crowding, while also providingand provides a button that lets people revisit them. To help ensure the system hides passes appropriately, set the expiration date, relevant date, and voided properties of each pass correctly; for developer guidance, see Pass.
Always get people’s permission before deleting a passpasses from Wallet. For example, you could include an in-app setting that lets people specify whether they want to delete passes manually or have them removed automatically.allow automatic removal. If necessary, you can displayshow an alert before deleting a pass.
Help the system suggest a pass when it’s contextually relevant. Ideally, passes automatically appear when they’re needed so people don’t have to manually locate them. When you supplyprovide information about when and where your pass is relevant, the system can display a link to it on the Lock Screen when people are most likely to want it. For example, a gym membership card could appear on the Lock Screen as people enter the gym. For certain types of passes, like event tickets, the system can also start a Live Activity. For developer guidance, see Showing a Pass on the Lock Screen. Starting in iOS 18 and watchOS 11, the system starts a Live Activity for poster event ticket style passes when they’re relevant.
UpdateKeep passes as needed.up to date. Physical passes don’t typically change, but a digital pass can reflect updates to events.changes as they happen. An airline boarding pass, for example, can automatically update to display flight delays and gate changes.
Use change messages only for updates to time-critical information. A change message interrupts people’s current workflow,people, so it’s essential to send one only when you make an updatefor updates they need to know about. For example, people need to know when there’s a gate change infor a boarding pass,flight, but they don’t need to know when a customer service phone number changes. Never use a change message for marketing or other noncritical communication. Change messages are available on a per-field basis;field; for developer guidance, see Adding a Web Service to Update Passes.
You define the content and structure of a pass using a combination of pass fields and semantic tags. Pass fields define what information appears on a pass and how it’s arranged. Semantic tags describe pass content to the system, enabling features like surfacing a pass when it’s needed, and featured actions, which are quick links to related content like venue directions or event guides. For poster event and semantic boarding passes, semantic tags are required and enable automatic layout. Include pass fields alongside semantic tags for these pass types too, so the passes display correctly on devices running older versions of iOS.
In some cases, you can provide supplemental information that people can access via sheets linked from the front of the pass. The back of the pass holds settings and information people rarely need to access, like legal text.
For developer guidance, see Wallet Passes.
Pass fields are organized into the following areas:
Logo and logo text fields: Show the brand icon and name; they remain visible when the pass is collapsed in Wallet.
Header fields: Show critical information that remains visible when the pass is collapsed.
Primary field: Shows the most important information people need.
Secondary and auxiliary fields: Show useful, but less critical information.
Footer fields: Show supplemental information, such as pass category (for example, “Family” or “Annual”).
Back fields: Show supplemental details that appear in pass details in Wallet.
Layout varies by pass style. For developer guidance, see Defining the metadata of your Wallet Pass.
Wallet uses a consistent design aestheticvisual style to strengthenbuild familiarity and build trust. Instead of merely replicating the appearance of aits physical item,counterpart, design a clean, simple pass that looksfeels at home in Wallet.
Use Pass Designer to design and preview passes for Apple Wallet. Starting from Apple-provided templates or a blank pass, you can create boarding passes, coupons, event tickets, store cards, generic passes, and poster generic passes. For more information, see Creating a pass with Pass Designer.
Design a pass that looks great and works well on all devices. Passes can look different depending on different devices.the device. For example, when a pass appears on Apple Watch, it doesn’t display all theWatch shows less information and fewer images it displays when it appearsthan on iPhone (for guidance, see Passes for Apple Watch).iPhone. Don’t put essential information in elements that might be unavailable on certain devices. Also, don’t adddevices, and avoid adding padding to images; for example, watchOS crops white space from some images.
Avoid using device-specific language. You can’t predict the device people will use to view your pass, so don’t write text that might not make sense on a particular device. For example, text that tells people to “slide to view” content doesn’t make sense when it appears on Apple Watch.
Make your pass instantly identifiable. Using color — especially a color that’s linked to your brand — can help people recognize your pass as soon as theyguidance, see it. Make sure that pass content remains comfortably readable against the background you choose.watchOS.
Keep the pass front of a pass uncluttered so people can get important information at a glance.uncluttered. Show essential information —information, like an event date or account balance —balance, in the top-right area of the passheader so people can still see it when the pass is collapsed in Wallet. Use the rest of the pass front to provide important information; consider putting extrafor information people need quick access to. Place details people don’t need often on the backadditional pass information sheet.
Make your pass instantly identifiable. Use brand colors and visual elements like images, icons, and full-art backgrounds to help people recognize your pass at a glance.
Ensure sufficient contrast between background and text colors. Pick label colors that keep text legible against both solid backgrounds and background images.
Use language that works on any device. Passes can appear on multiple devices, so use text that makes sense everywhere. For example, “Slide to view” is meaningful on iPhone but doesn’t apply on Apple Watch.
You can choose from a variety of pass styles. Each one defines the appearance and layout of your pass.
The boarding pass style is for travel tickets: airline boarding passes, train tickets, bus tickets, boat tickets, and generic transit passes. Typically, each pass corresponds to a single trip with a specific starting and ending point. Use semantic tags for airline boarding passes; use pass fields for all other transit types. For developer guidance, see Creating an airline boarding pass using semantic tags.
The coupon style is for coupons, special offers, and other discounts. For developer guidance, see Creating a coupon pass.
The event ticket pass style is for entry into events like sporting events, concerts, movies, and plays. Typically each pass corresponds to a specific event, but you can also use a single pass for multiple events, as with a season ticket. An event ticket supports a full-art background to evoke the look and feel of your event. For developer guidance, see Creating a poster event pass using semantic tags.
Non-poster style event tickets use standard pass fields and can use a background image and thumbnail.
The store card style is for store loyalty cards, discount cards, points cards, and gift cards. If an account carries a balance, the pass usually displays it. For developer guidance, see Creating a store card pass.
The poster generic pass style features a full background image and a pass (iOS)field layout distinct from other pass styles, offering a flexible option that supports a wide range of use cases. It’s not tied to a specific category, so you can use it whenever another pass style doesn’t fit.
The generic style is for passes that don’t fit the other categories, such as a gym membership card or in a details screen (watchOS)coat-check claim ticket. For developer guidance, see Creating a generic pass.
Prefer an NFC-compatible pass. People appreciate having
Passes support a contactless pass, because it means that they can just hold their device near a reader. If you support both NFCvariety of image types. Create pass images in PNG format in @2x and a barcode or QR code, the code appears on the back of the pass (in iOS) or in the details screen (in watchOS). In iOS, you can display a QR code or barcode on the front of your pass if necessary for your design.@3x format.
ReduceReserve pass images for visual content. Embedded text isn’t accessible and may not be visible if images don’t display on all devices. For text information, use text fields and semantic tags instead. Use Pass Designer or corresponding APIs to add barcodes rather than embedding them in pass images.
Keep image file sizes for optimal performance.small. People can receive passes via email or a webpage. To make downloads as fast as possible, use the smallest image files that still look great.
Provide an icon that represents your company or brand.a pass icon. The system includesuses it to represent your icon when displaying information about a relevant pass on the Lock Screen. Mail also uses the icon to represent your passScreen, in an email message.Mail, and on passes in Wallet. You can use your app icon or design an icon for this purpose.a separate one.
The system defines several pass styles for categories like boarding pass, coupon, store card, and event ticket. Pass styles specify the appearance and layout of content in your pass, and the information that the system needs to suggest your pass when it’s relevant (for guidance, see Passes).
Although each pass style is different, all styles display information using the basic layout areas shown below:
All passes display a logo image, and some can display additional images in other areas depending on the pass style. To display informationappears in the layout areas, use the following PassFields.top leading corner of passes with pass fields. It’s typically a horizontal text logo representing your brand, optionally combined with a graphic element.
|
|
|
|---|---|---|
|
|
|
|
|
|
|
|
|
|
| |
Height |
|
Avoid inner drop shadows on logo artwork. They can reduce legibility when the logo renders on the pass.
Like the logo, the primary logo appears in the top-leading corner of your pass, but is used exclusively for semantic passes.
Supported pass styles | Airline boarding passes, poster event tickets, and poster generic passes |
Filename | primaryLogo.png |
Minimum width | 30 pt |
Maximum width | 126 pt |
Height | 30 pt |
The secondary logo displays an additional logo for a ticket issuer or event organizer. It appears in the bottom-trailing corner of a poster event ticket.
Supported pass styles | Poster event ticket |
Filename | secondaryLogo.png |
Minimum width | 12 pt |
Maximum width | 135 pt |
Height | 12 pt |
Icons are square and represent your company or brand when your pass appears on the Lock Screen, in Mail, and on passes in Wallet. The system automatically applies rounded corners, so you don’t need to beround them.
Supported pass styles | All |
Filename | icon.png |
Width | 38 pt |
Height | 38 pt |
Strip images appear on coupons and store cards to reinforce your brand or offer. Because text can appear over strip images, ensure sufficient contrast between your text and the image. Keep areas behind text uncluttered, and place important visual elements toward the bottom or trailing edge. Avoid embedding text in the strip image.
Supported pass | Coupon, store card |
Filename | strip.png |
Width | 375 pt |
Height | 144 pt |
Thumbnails are small images, such as a movie poster, that appear on event tickets and generic passes. Thumbnails are square — use rounded corners on your artwork and export as a transparent PNG.
Supported pass styles | Event ticket, generic pass |
Filename | thumbnail.png |
Minimum width | 60 pt |
Maximum width | 90 pt |
Height | 90 pt |
The background image is the visual centerpiece of a pass.
Non-poster pass backgrounds
Supported pass styles | Event tickets |
Filename | background.png |
Width | 343 pt |
Height | 503 pt |
In general, aPoster pass can have up to three header fields, one primary field, up to four secondary fields, and up to four auxiliary fields. Depending on the amount of content you display in each field, some fields may not be visible.backgrounds
|
|
Filename | artwork.png |
Width | 358 pt |
Height | 448 pt |
Position content within the event artwork, provides easy access to additional event information,safe area — on poster generic passes and integrates with system apps like Weather and Maps.
A poster event ticket displays an event logo and background image, and can optionally display a separate ticket issuer or event company logo. The system uses metadata about your event to structure ticket information and suggest relevant actions. You must provide a required set of metadata in SemanticTags for all
The system uses the metadata that you provide to generate a Maps shortcut to the venue directions and an event guide below the ticket when in the Wallet app. The event guide provides convenient access to information like the weather forecast and venue map, and to quick actions like checking the baggage policy and ordering food. You can display a minimum of one and up to four quick action buttons in the event guide; if you include more than four, the system collapses them into a menu. You can optionally include additional ticket information, such as pre-paid parking details, which the system also displays below the ticket.
Create a vibrant and engaging background. As the centerpiece of a poster event ticket, your background image serves as a visual representation of the event. Limit text in your artwork, and create an image that’s easily identifiable to help people quickly find their ticket among other passes in their Wallet app. If your background image is a solid color or includes a solid color in the footer, consider setting a footer background color to better blend the background image with the footer.
Position your background image in the safe area. The system displays ticket information in the header and footer, which overlap the background image. To ensure that the content in your artwork isn’t covered, position it in the safe area.verify placement. For developer guidance, see footerBackgroundColor in Pass.
The footer is only available for airline boarding passes.
| Airline boarding passes |
| footer.png |
Width | 268 pt |
Height | 15 pt |
When you have moresupport order tracking, Wallet can display information about an order a customer placed through your app or website, updating the event that people may find helpful,information whenever the additional information tile below the ticket is a great place to put it. If you have additional information that’s essential to display on the frontstatus of the ticket, keep the text shortorder changes. In iOS 17 and later, you can help people start tracking their order right from your app or website and offer additional ways to avoid cluttering the footer. For developer guidance, see additionalTicketAttributes in SemanticTagsadd their order to Wallet.
Wallet presents a dashboard that displays a customer’s active and PassFields.AdditionalInfoFields.
Continue to support event tickets for earlier versions of iOS. People expect contactless event tickets to work, regardless of their device’s software version. Continue to provide primary, secondary, and auxiliary information in PassFields and image assets for your event ticket. This enables the system to automatically generate the appropriate ticket style for a person’s device; otherwise, your ticket appears empty on devices running earlier versions of iOS.
Use the generic style for a type of pass that doesn’t fit into the other categories, such as a gym membership card or coat-check claim ticket. A generic pass can display logo and thumbnail images, and it can have up to four secondary and auxiliary fields, all displayed on one row.
On Apple Watch, Wallet displays passes in a scrolling carousel of cards.completed orders. People can add your passchoose an order to their Apple Watch even if you don’t create a watch-specific app, so it’s important to understand how your pass can look onview details about it, like the device.items they ordered and fulfillment information for shipping and pickup.
People can tap a pass on their Apple Watch to reveal a details screen that displays additional information in a scroll view. In some cases, people can also tap a specific transaction to get more information.
Each pass style specifies the fields and images that can appear in the basic layout areas shown below:
If some information doesn’t fit within the layout areas, the system displays it in the scrolling details screen.
When you support order tracking, Wallet can display information about an order a customer placed through your app or website, updating the information whenever the status of the order changes. In iOS 17 and later, you can help people start tracking their order right from your app or website and offer additional ways to add their order to Wallet.
Wallet presents a dashboard that displays a customer’s active and completed orders. People can choose an order to view details about it, like the items they ordered and fulfillment information for shipping and pickup.
The Wallet Orders
Make it easy for people to add an order to Wallet. For example, when a customer completes an Apple Pay transaction in your app or website, use PKPaymentOrderDetails (app) or ApplePayPaymentOrderDetails (web) to automatically add the order to Wallet. In iOS 17 and later, you can use AddOrderToWalletButton to display the system-provided Track with Apple Wallet button in relevant areas of your app or website — such as in pages for order confirmation, status, or tracking — or in emails to customers. If a person already added an order to Wallet, trying to add it again opens Wallet and displays the order.
Make information about an order available immediately after people place it. People need to confirm that their order was received, even when payment, processing, and fulfillment are still pending. If you won’t have details until a later time, provide the data you have at the time of the order and supply a status description like “Check back later for full order details.”
Provide fulfillment information as soon as it’s available, and keep the status up to date. When you supply fulfillment data or you change the status of an order, the system updates the order information and can automatically send a notification to customers. The system uses the fulfillment status you report to update the order’s current status to a value like Order Placed, Processing, Ready for Pickup, Picked Up, Out for Delivery, Delivered, or — if something goes wrong — Issue or Canceled. For guidance on describing a status, see Displaying order and fulfillment details.
Supply a high-resolution logo image that uses a nontransparent background. The system displays your logo image in the dashboard and detail view, so you want to make sure that people can instantly recognize it at various sizes. Use the PNG or JPEG format to create a logo image that measures 300x300 pixels. To help ensure that your logo image renders correctly, be sure to use a nontransparent background. For developer guidance, see logo.
Supply distinct, high-resolution product images that use nontransparent backgrounds. The system displays a product’s image — along with descriptive information you supply — in the detail views, order dashboard, and notifications for an order or a fulfillment. When creating a product image, use a straightforward depiction and a solid, nontransparent background. Showing a product in a “lifestyle” context or against a busy background can make the item hard to distinguish at small sizes. For each product, use the PNG or JPEG format to create an image that measures 300x300 pixels.
In general, keep text brief. People appreciate being able to read text at a glance, and the system can truncate text that’s too long.
Use clear, approachable language, and localize the text you provide. You want to make sure that all your customers can read the information in an order. Also, make sure the price you show matches the final price the customer confirmed.
An order gives people ways to contact the merchant and displays details about their Apple Pay purchase, including fulfillment status and per-item information.
Provide a link to an area where people manage their order. When you provide a universal link, people can open your order management area even if they don’t have your app installed. To learn more about universal links, see Allowing apps and websites to link to your content; for developer guidance, see Order.
Clearly describe each item so people can verify that their order contains everything they expect. You can use the LineItem property to provide information like a product’s price, name, and image. An order lists the line items for every item the customer ordered; a fulfillment lists only the line items that fulfillment includes. When appropriate, you can also attach a PDF receipt to an individual transaction related to an order.
Supply a prioritized list of your apps that might be installed on the device. The system uses this list when it needs to display a link to your app within the order details view. For example, if you provide multiple apps and more than one of them is installed on the device, the system displays a link to the installed app that’s highest on your list. If none of your apps are installed on the device, the system displays a link to the first app on your list. For developer guidance, see Order.
Avoid sending duplicate notifications. For example, you can tell the system to avoid sending order-related notifications through Wallet when the customer has one of your associated apps installed.
Make it easy for customers to contact the merchant. Provide multiple contact methods, so people can choose the one that works best for them. At minimum, you need to provide a link to the merchant’s website or landing page, but you can also provide a Messages for Business link, a phone number, an email address, and a link to a support page. When people choose the Contact button in an order, the system displays a menu of the contact methods you supply. For developer guidance, see Merchant.
Help people track their order. A multi-item order can have multiple fulfillments, where each fulfillment is either shipping or pickup. For example, if a customer orders a pair of shoes and a T-shirt, the customer might want to have one item shipped, while picking up the other. Regardless of fulfillment type, you need to supply enough information for people to know where their items are and when to expect them at the destination they specified. In addition to an estimated time of arrival, here’s some information that people particularly appreciate:
A link that opens the carrier’s website to a page with information about a shipping fulfillment. When possible, provide a direct link — in addition to a tracking number — so people can easily view the most up-to-date shipping information. If necessary, display this link on any intermediate order-tracking page you open.
A scannable barcode when one is required to pick up the order in a pickup fulfillment. It’s convenient when people can offer the barcode from within Wallet instead of finding it in an email or webpage.
Clear, detailed instructions that can help people receive or pick up their order.
Keep the fulfillment screen centered on order tracking. For example, if you recommend your app or other services to customers, be sure to prioritize order-tracking information over other content in the screen.
Choose shipping-fulfillment values that match the details you have about the shipping process. If you know the carrier, enter its name in the carrier property; otherwise, leave the default “Track Shipment” value. If you can access details about a carrier’s interim shipping steps — such as when a fulfillment is on the way or out for delivery — indicate each step by using specific status values like onTheWay, outForDelivery, or delivered. In contrast, if you don’t have access to a carrier’s shipping details, use the shipped status. In both cases, provide a tracking link (when one is available) so people can track their order on their own. For developer guidance, see ShippingFulfillment.
Keep customers informed through relevant fulfillment status descriptions. A great status message is approachable, accurate, and clearly related to the status it describes. In addition to supplying information that helps people understand the status of their order, a status message also gives you an opportunity to use your brand’s communication style.
Be direct and thorough when describing an Issue or Canceled status. People generally need to know why there’s a problem and what they can do about it.
On iPhone running iOS 16 and later, people can store an ID card in Wallet, and later allow an app or App Clip to access information on the card to verify their identity without leaving their current context. For example, a person might need to confirm their identity when they apply for a credit card within their banking app. To learn how to support in-person mobile ID verification, see ID Verifier.
To help you offer a consistent experience that people can trust, Apple provides a Verify with Wallet button you can use in your app when you need to ask for identifyidentity verification. The button reveals a sheet that describes your request and lets people agree to share their information or cancel.
Present a Wallet verification option only when the device supports it. If the current device can’t return the identifyidentity information you request, don’t display a Verify with Apple Wallet button. Be prepared to present a fallback view that offers a different verification method if Verify with Apple Wallet isn’t available; for developer guidance, see VerifyIdentityWithWalletButton.
Ask for identity information only at the precise moment you need it. People can be suspicious of a request for personal information if it doesn’t seem to be related to their current action. If your app needs identity verification, for example, wait to ask for this information until people are completing the process or transaction that requires it; don’t request verification before people are ready to start the process or when they’re simply creating an account.
Clearly and succinctly describe the reason you need the information you’re requesting. You must write text that explains why people need to share identity information with your app (this text is called a purpose string or usage description string). The system displays your purpose string in the verification sheet so people can make an informed decision. Here are a couple of examples:
To verify… | To support… | Example purpose string |
|---|---|---|
Identity | Opening an account for which proof of identity is legally required to prevent fraud | Federal law requires this information to verify your identity and also to help [App Name] prevent fraud. |
Driving privilege | Renting a vehicle that requires legal driving privileges | Applicable state law requires [App Name] to verify your driving privileges. |
For each purpose string, aim for a brief, complete sentence that’s direct, specific, and easy for everyone to understand. Use sentence case, avoid passive voice, and include a period at the end.
Ask only for the data you actually need. People may lose trust in your app if you ask for more data than you need to complete the current task or action. For example, if you need to ensure that a customer is at least a certain age, use a request that specifies an age threshold; avoid requesting the customer’s current age or birth date. For developer guidance, see age(atLeast:).
Clearly indicate whether you will keep the data and — if you need to keep it — specify how long you’ll do so. To help people trust your app, it’s essential to explain how long you might need to keep the personal information they agree to share with you. When you use PassKit APIs to specify a duration — such as a particular period, indefinitely, or only as long as it takes to complete the current verification — the system automatically displays explanatory content in the verification sheet. For developer guidance, see PKIdentityIntentToStore.
Choose the system-provided verification button that matches your use case and the visual design of your app. The system provides the following button labels to support various use cases:
Button type | Consider using when… |
|---|---|
Your app can complete the current transaction after you verify a person’s age. An example transaction is making a car available to lease. | |
Your app can complete the current transaction after you verify a person’s identity. An example transaction is a car rental. | |
Verify with Wallet forms one part of a verification process that also requires people to supply additional information not provided by Verify with Wallet, such as a Social Security number or phone number. Examples include opening a financial account or performing a background check. | |
Your app can complete the current verification flow without additional steps, but the “Verify Age,” “Verify Identity,” and “Continue” button labels aren’t appropriate for your use case. An example is an app that helps people sign up for a government service. |
All button labels are also available in a multiline variant that the system automatically uses when horizontal space is constrained. For developer guidance, see PKIdentityButton.Label.
The verification button always uses white letters on a black background. You can choose the style that includes a light outline if you need to ensure that the button contrasts well with a dark background in your app. In addition, you can use the cornerRadius property to adjust the verification button’s corners to match other related buttons in your interface. For developer guidance, see PKIdentityButton.Style.blackOutline.
No additional considerations for iOS, iPadOS, macOS, visionOS, or watchOS.visionOS. Not supported in tvOS.
AsOn Apple Watch, Wallet displays passes in a scrolling carousel of cards. People can add your pass to their Apple Watch even if you designdon’t create a watch-specific app, so it’s important to understand how your pass can look on the device.
People can tap a pass on their Apple Watch to reveal a details screen that displays additional information in a scroll view. In some cases, people can also tap a specific transaction to get more information.
Each pass style specifies the fields and images for your wallet passes, create PNG files and usethat can appear in the following values for guidance.basic layout areas shown below:
|
|
|
|
|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
PassKit (Apple Pay and Wallet)
Date | Changes |
|---|---|
June 8, 2026 | Updated to reflect guidance for iOS 27 and the Pass Designer app. |
January 17, 2025 | Added specifications for pass image dimensions. |
December 18, 2024 | Added guidance for the poster event ticket style. |
September 12, 2023 | Added guidance for helping people add orders to Wallet. |
February 20, 2023 | Enhanced guidance for presenting order-tracking information and added artwork. |
November 30, 2022 | Added guidance to include a carrier name in status information for a shipping fulfillment. |
September 14, 2022 | Added guidelines for using Verify with Wallet, updated guidance on providing shipping status values and descriptions, and consolidated guidance into one page. |