Wallet passes are digital cards, tickets, coupons, or credentials stored in Apple Wallet or Google Wallet on a customer's phone. Unlike a mobile app, passes install with a tap from a link or QR code and can update after installation.
What customers experience
After adding a pass, the customer sees it on their wallet shelf and lock screen when relevant. Updates such as points, gate changes, or offers appear without reopening a website or app.
What teams need to operate passes
Production programs usually require: signed pass files for each wallet, a way to distribute passes (links, QR, API), an update channel when fields change, and optional location or time triggers for notifications.
Apple Wallet vs Google Wallet
Both wallets support loyalty, offers, tickets, and generic passes, but the underlying APIs differ. A platform that publishes to both from one template reduces duplicate work.
Next steps
Start with one pass type and one distribution channel, validate scan or redemption, then add API automation and notification rules.