Skip to content
EntryWick documentation

For attendees on their phones, the night before or in the queue.

Wallet tickets

A ticket in Apple Wallet or Google Wallet, added from the ticket page — so the QR a gate scans is on the lock screen, not in an email somewhere.

Who uses it: attendees on their phones, the night before or in the queue.

What they came to do: keep their ticket where they can find it without signal or searching their inbox.

What must be true when they leave: the ticket in their wallet scans exactly like the printed one, and a ticket that has been replaced does not quietly keep working.

Decided

  • "Add to Apple Wallet" and "Save to Google Wallet" appear on a live ticket's page when the organization has wallet tickets turned on and the platform is set up for that wallet.
  • The wallet ticket shows the person's name, the day, the venue and the code, with the same QR as the printed ticket.
  • When a ticket is replaced (a day change, a reissue) or voided, a Google Wallet ticket becomes inactive. An Apple Wallet ticket keeps showing the old code; the gate says it was replaced and names the new one.
  • Ticket emails can link to the ticket page with ticket.wallet_url.
  • An Apple Wallet ticket is not updated once it is on a phone. Apple's PassKit web service (device registrations, push through APNs) is deferred to after GA unless a paying customer needs it (owner, 2026-09-13). Google tickets stay live.

Open

  • Official "Add to Wallet" badges instead of text links.
  • Checked on a real iPhone and Android phone once the platform credentials are in place (owner).