Industry problems

How does ticket scanning work without internet?

Ticket scanning works without internet when each part of the entry process has what it needs on the device. The attendee shows a ticket saved in a phone wallet rather than one loaded from email, the scanner checks it against a list or issuer key it downloaded before doors opened, and scanners share their check-ins with each other locally or merge them once the connection returns. Whatever cannot be checked on the spot, such as a duplicate admitted at another gate, is resolved afterwards.

TL;DR

Offline entry works when each part has a fallback: the ticket stored in a phone wallet, the scanner holding a ticket list or issuer key, and scanners sharing check-ins. Without sharing, a ticket reused at another gate is caught only after scanners sync. Give each check-in an ID, never drop a scan when merging, and let the platform reconcile later.

Learning objectives

After reading this article you will be able to:

  • Explain why a wallet pass works at the gate when an emailed ticket may not
  • Compare downloaded ticket lists with signed tickets checked against a stored key
  • Describe how scanners sharing check-ins locally catch a ticket reused at another gate

Event entry failure points without internet

Event entry can fail at the attendee’s phone, at the scanner, or at the shared record of check-ins, because getting someone through a gate involves three things working together:

  1. The attendee’s phone has to show the ticket.
  2. The scanner has to decide whether the ticket is valid for this event.
  3. The shared record of check-ins has to tell every scanner which tickets have already been used.

In a connected venue, all three can lean on the internet. A ticket in an email or on a web page may need to load from a server, a scanner app may ask the ticketing platform about each code, and the platform keeps one list of check-ins for every device. When a venue’s network saturates or its uplink fails, each of the three needs its own fallback. How do stadiums cope when phone networks saturate? covers why that happens on busy days.

Offline tickets in phone wallets

The simplest fix for showing a ticket with no signal is on the attendee’s side: store the ticket on the phone before arrival. Apple describes the Wallet flow as a user adding a pass to the Wallet app on their device, then holding the device near an NFC reader or scanning a barcode on the pass. Google notes that links to an event ticket work offline when the Google Wallet app is installed.

Wallet tickets come in a few forms, and each puts a different demand on the gate:

  • A static barcode that the scanner reads like any printed code.
  • A rotating barcode, which Google says changes periodically, typically every minute, with the reader programmed to accept only the most recent one. That limits screenshot sharing, but the reader has to be set up to know which code is current.
  • NFC tap, which on Google Wallet uses Smart Tap and needs terminals that support it.

Google also lets an issuer require a screen lock before a pass is shown, to protect the holder’s access to it.

Offline ticket validation on the scanner

To check a ticket with no connection, the scanner needs the answer on the device. There are two ways to do that: download the list of valid tickets before the doors open, or issue tickets that carry the issuer’s signature so the scanner can check them with a stored key. How are tickets checked at a gate with no internet? goes through the signed-ticket approach step by step.

A scanner app does more than read a code. Eventbrite’s organizer app, for example, offers three scan behaviours: check attendees in, check them out, or validate only, which shows whether a code is valid for the event without changing anything. In the default mode it shows an error if a code is already checked in or not valid for the event, and staff can search for an attendee and check them in by hand.

Shared check-in records across gates

Scanners know a ticket was used at another gate only through the shared record of check-ins, and that record of who is already inside is the hardest part to keep offline. Eventbrite describes running check-in on several devices at once, with data syncing automatically so that every team member has the current attendee list and duplicate entries are prevented. That sync is what lets the north gate reject a ticket already used at the south gate. Without a connection, each scanner knows only its own scans.

The approaches compare like this:

ApproachValid ticket check offlineRepeat scan at the same gateRepeat scan at another gate
Live lookup on every scanNoOnly while onlineOnly while online
Ticket list downloaded to each scannerYes, against the listYesNo, until scanners sync
Signed tickets checked with a stored keyYes, by signatureYesNo, until scanners sync
Either of the above, plus local sharing between scannersYesYesYes, for scanners that can reach each other

Scanner-to-scanner check-in sharing

If scanners pass each check-in to the scanners near them, directly over a short-range radio or through a relay device, a ticket used at one gate shows as used at the others within moments, with no internet involved. That is the last row of the table, where local software helps. Gates that cannot reach any other scanner fall back to the downloaded list or signature check, and their records merge when they reconnect.

Two design choices keep it safe. Each check-in needs its own ID, so a record that arrives twice, once directly and once by relay, is counted once (see message deduplication). And the merge rule must never drop a scan, so a ticket admitted at two gates during a gap is visible once the records meet. The article on checking tickets at a gate, linked above, explains both in more depth.

The rest is planning on the ground. Scanners at neighbouring gates need to be within radio range of each other, or have a staff phone between them that can relay. Staff need a clear rule for what a scanner shows when it is working alone, so a gate does not stop admitting people just because it cannot see the others. And the ticketing platform stays the system of record: local sharing narrows the window in which a copied ticket can get in twice, and the platform reconciles everything once the connection returns.

Frequently asked questions

Should attendees screenshot their tickets in case the venue has no signal?

A ticket saved to Apple Wallet or Google Wallet is already stored on the phone. A screenshot fails if the ticket uses a rotating barcode, because Google says the reader accepts only the most recent code.

Can staff check people in by name if scanning fails?

Eventbrite's organizer app lets staff search for an attendee by name and check them in manually. Offline, that works only if the scanner holds a copy of the attendee list, and the copy is only as current as its last sync.

Do Google Wallet event tickets work offline?

Google notes that links to an event ticket work offline when the Google Wallet app is installed.

What is a rotating barcode on a ticket?

It is a barcode that Google says changes periodically, typically every minute, with the reader programmed to accept only the most recent one. That limits screenshot sharing, but the reader has to be set up to know which code is current.

Can one ticket get in at two gates while scanners are offline?

Yes, during the gap, because without a connection each scanner knows only its own scans. Scanners that share check-ins locally catch a reused ticket at gates that can reach each other, and a merge rule that never drops a scan makes a double admission visible once the records meet.

How do you stop a check-in being counted twice when it arrives by two paths?

Give each check-in its own ID, so a record that arrives twice, once directly and once by relay, is counted once.

Sources

Build it with Offline Protocol

The shared state guide covers replicated documents that devices edit locally and merge when they reconnect, including which merge rule each collection uses, which is how a group of scanners can keep one record of check-ins.

Read the shared state guide