Apple Pay, passes, Wallet, and transaction UX
Apple Pay handles eligible payment authorization without giving the app raw payment credentials. Wallet passes represent tickets, memberships, keys, or status that remains useful after the purchase moment.
Design the capability
- Build a payment request from validated merchant capability, country, currency, line items, shipping needs, and supported networks.
- Treat authorization as one step. The server still owns order validation, fulfillment, idempotency, refund, and reconciliation.
- Use StoreKit for digital goods and services consumed in the app according to current policy. Use Apple Pay for eligible real-world transactions.
- Passes need stable identity, signed updates, relevance policy, privacy review, and a useful expired or revoked state.
Validation boundary
No merchant registration, payment processing certificate, entitlement, gateway, sandbox card, pass signing, Wallet installation, or physical-device transaction occurred.
Series navigation
- Previous: Part 107: StoreKit, subscriptions, offers, and entitlement state
- Next: Part 109: Games, GameKit, SpriteKit, SceneKit, and Metal choices
- Series index: Zero to iOS Hero