# Wallet

Source: https://developer.apple.com/design/human-interface-guidelines/wallet
Skill: hig-technologies
Snapshot: 2025-02-02

---
<!-- hig-doctor:attribution -->
> **Source**: Apple Inc. Canonical content at https://developer.apple.com/design/human-interface-guidelines/wallet.
> This file is a structured index of that content, snapshot 2025-02-02.
> Apple HIG text and imagery are © Apple Inc.; this repository provides organization and cross-referencing for AI agent consumption only.

# Wallet

## Passes

**Offer to add new passes to Wallet.**

**Help people add a pass that they created outside of your app.**

**Add related passes as a group.**

**Display an Add to Apple Wallet button to let people add an existing pass that isn’t already in Wallet.**

**Let people jump from your app to their pass in Wallet.**

**Tell the system when your pass expires.**

**Always get people’s permission before deleting a pass from Wallet.**

**Help the system suggest a pass when it’s contextually relevant.**

**Update passes as needed.**

**Use change messages only for updates to time-critical information.**

## Designing passes

**Design a pass that looks great and works well on all devices.**

**Avoid using device-specific language.**

**Make your pass instantly identifiable.**

**Keep the front of a pass uncluttered so people can get important information at a glance.**

**Prefer an NFC-compatible pass.**

**Reduce image sizes for optimal performance.**

**Provide an icon that represents your company or brand.**

### Pass styles

**Display text only in pass fields.**

#### Boarding passes

  * Example 
  * Layout 

#### Coupons

  * Example 
  * Layout 

#### Store cards

  * Example 
  * Layout 

#### Event tickets

  * Example 
  * Layout 1 
  * Layout 2 

  * Example 
  * Layout 

**Create a vibrant and engaging background.**

**Position your background image in the safe area.**

**Ensure sufficient contrast so that ticket information is easy to read.**

**Consider using the additional information tile for extra event details.**

**Continue to support event tickets for earlier versions of iOS.**

#### Generic passes

  * Example 
  * Layout 1 
  * Layout 2 

### Passes for Apple Watch

  * Boarding 
  * Coupon 
  * Store 
  * Event 
  * Generic 

## Order tracking

**Make it easy for people to add an order to Wallet.**

**Make information about an order available immediately after people place it.**

**Provide fulfillment information as soon as it’s available, and keep the status up to date.**

**Supply a high-resolution logo image that uses a nontransparent background.**

**Supply distinct, high-resolution product images that use nontransparent backgrounds.**

**In general, keep text brief.**

**Use clear, approachable language, and localize the text you provide.**

### Displaying order and fulfillment details

**Provide a link to an area where people manage their order.**

**Clearly describe each item so people can verify that their order contains everything they expect.**

**Supply a prioritized list of your apps that might be installed on the device.**

**Avoid sending duplicate notifications.**

**Make it easy for customers to contact the merchant.**

**Help people track their order.**

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

**Choose shipping-fulfillment values that match the details you have about the shipping process.**

**Keep customers informed through relevant fulfillment status descriptions.**

**Be direct and thorough when describing an Issue or Canceled status.**

## Identity verification

**Present a Wallet verification option only when the device supports it.**

**Ask for identity information only at the precise moment you need it.**

**Clearly and succinctly describe the reason you need the information you’re requesting.**

**Ask only for the data you actually need.**

**Clearly indicate whether you will keep the data and — if you need to keep it — specify how long you’ll do so.**

**Choose the system-provided verification button that matches your use case and the visual design of your app.**

---

<!-- hig-doctor:canonical-footer -->
For the complete guidance, including worked examples and illustrations, see the canonical page: https://developer.apple.com/design/human-interface-guidelines/wallet