How do mobile wallet tickets work?
A mobile wallet ticket is a digital event credential saved to a phone wallet, such as Apple Wallet or Google Wallet. It can show event details and a barcode or, where supported, an NFC-based admission credential. Saving a ticket to a wallet makes it easier to retrieve, but does not by itself prove the ticket is valid for entry.
How is a wallet ticket issued?
The ticketing system creates an entitlement and generates a wallet pass or a signed link to add one. The pass can include event name, date, venue, seat and a representation of an admission credential. Google Wallet’s event-pass documentation describes issuer accounts and class/object structures; supported links can appear on websites, emails or SMS. Apple Wallet uses signed pass packages and a separate pass lifecycle.
What happens at the gate?
NFC is not automatically available just because a pass lives in a phone wallet: it depends on wallet capabilities, issuer setup and compatible access hardware. A standard barcode pass should not be marketed as tap-to-enter without an end-to-end deployment.
How do changes reach the wallet?
Where the platform and wallet support updates, an event time, gate or ticket status can be reflected in the saved pass. Changes to the wallet’s display do not replace server-side admission controls. Operators need to decide what happens if the pass displays stale information while a ticket has been refunded, transferred or revoked.
What should an organiser test?
Test addition from mobile web and email, wallet appearance on supported devices, date/time formatting, notifications, scanner compatibility and a revoked ticket. Include poor connectivity and phones with low battery. Provide an accessible alternative for customers who cannot or do not want to use a wallet.