Wallet pass App Review checklist

Choose the correct pass type and issuer

Name whether the pass is a boarding pass, event ticket, coupon, store card, membership card, transit-style credential, or generic pass. The type affects fields, user expectation, relevance, and expiration behavior.

Issuer identity should be obvious. If the app creates passes for third-party merchants, venues, schools, or employers, keep a rights and authorization record for each issuer brand shown on the pass.

Audit every visible field

• Primary and secondary fields should match what a scanner, gate, cashier, or staff member expects.
• Dates, locations, seat numbers, loyalty balances, and coupon terms should stay current.
• Barcode or NFC payloads should not expose unnecessary private data.
• Images should be authorized and readable in light and dark contexts.
• Expiration and voided states should be visible when the pass is no longer valid.

Plan pass updates before launch

If a pass can change, the app and server need a reliable update path. Apple documentation describes adding a web service for pass updates. A stale boarding time, invalid coupon, or old membership status can be worse than no pass.

AppReviewReady interpretation: record which fields are static, which fields update, who owns the update feed, and what support does when a pass in Wallet disagrees with the app.

Test Wallet pass states

1. Add the pass from the app and from any web or email route used in production.
2. Update a field, expire the pass, void it, and remove it.
3. Test multiple passes with the same grouping identifier and different accounts.
4. Verify privacy labels and policy cover pass fields, scans, location relevance, and update calls.
5. Check no pass remains useful after account deletion or ticket cancellation where access should end.

Give review a Wallet pass route

Use fictional passes for review unless a real pass is unavoidable. The reviewer should not need a real flight, venue entry, or loyalty account to verify behavior.

Also test what happens after a pass is shared, screenshotted, or presented offline. If fraud prevention depends on live validation, the pass UI and scanner workflow should make that dependency clear.

For location-relevant passes, verify the relevance information does not imply tracking beyond the pass use case and matches privacy disclosures.

Support should know whether pass issues are app, issuer, or scanner problems.

Wallet pass review path:
Pass type: [ticket, coupon]
Issuer: [name]
How to add: [steps]
Fields that update: [list]
Barcode/NFC purpose: [scanner use]
Expiration behavior: [state]
Sample pass data: [fictional]