Attendees add the ticket to
Apple Wallet or Google Wallet in one tap.
The confirmation page shows an Add to Apple Wallet and Add to Google Wallet button. Attendee taps, the pass lands in their wallet with name, seat, event, date, venue, QR code — coloured with your tenant brand. Push notification 24h and 1h before the event. Pass surfaces on the lock screen when the phone gets near the venue.
Everything staff need at the gate. Nothing they don't.
Four steps from tap to scan.
.pkpass file downloads, Wallet app opens, one confirmation tap to add. Google: signed JWT URL opens pay.google.com's Save flow, one tap to add.What's needed on the tenant side.
Wallet passes are a framework — off by default. Once credentials are dropped into config/wallet.php, the buttons appear on every confirmation page across the tenant.
Because the reminder that lives on the lock screen actually gets read.
No-show rate on paid events runs 8-15% in India. Every organiser we ship for tries to fix it with a WhatsApp reminder day-before and morning-of, and it makes a dent — but only for the fraction of the audience that reads that WhatsApp thread. Email reminders do less. SMS does less again. All of it is fighting for a slice of attention that already lives elsewhere.
The wallet reminder wins because the OS delivers it. There's no channel to opt out of, no unread inbox that hides it. 24 hours before Product Summit 2026, the phone lock screen just shows: "Product Summit 2026 tomorrow · Grand Hyatt, Bengaluru." The attendee glances, remembers, plans. 1 hour before, another notification. When the phone gets within a few hundred metres of the venue coordinates, the pass surfaces on the lock screen with the QR ready to scan.
On our first tenant that shipped wallet passes to a 500-attendee paid conference, no-show dropped from 12% to 7%. That's 25 extra bums in seats. On a sponsor-facing event, 25 more chances for the sponsor to have the conversation they paid for.
Also: pulling out a wallet pass at the gate is faster than scrolling through Gmail for the confirmation email. Median check-in time dropped from 1.8s to 1.1s. Doesn't sound like much until you're running a queue of 400 people.