What new metadata is required in pass?

To ensure your pass receives the new treatment in Wallet and Apple Pay, you need to include specific metadata in the pass JSON. Here are the key requirements:

1. Semantic Tags: These are machine-readable metadata that help the system better understand the data provided in the pass. You should use semantic tags wherever possible to surface pass information in the event guide and on the pass itself.

2. Preferred Style: Specify the preferred style in the pass JSON to render the new ticket style.

3. Required Pass Bundle Content: Continue to include the primary, secondary, and auxiliary fields in your pass JSON to ensure compatibility with older OS versions.

4. Newly Introduced Assets: Include an artwork asset and a secondary logo in the pass bundle. The artwork asset is used if you want previous OS versions to continue rendering your pass with the strip image or the background asset if you want the same background on all OS versions.

5. Event Information: Provide the event start date and time, and use the seats dictionary to populate entry and seating information. For events spanning multiple days, provide a relevant time interval.

6. Additional Metadata: Include semantically tagged URLs for tappable tiles, venue location using latitude and longitude coordinates, and performer names or artist IDs for music integration experiences.

For more detailed information, you can refer to the session What’s new in Wallet and Apple Pay (10:24).

Relevant Sessions

• What’s new in Wallet and Apple Pay
• What’s new in privacy
• Streamline sign-in with passkey upgrades and credential managers