Labs · Ticketing

Ticketing, made easy.

Issue a ticket and scan it, and it is admitted. Scan the same one again and it is refused. Signed, single-use, and checked at the door.

All of it is live: the codes are signed on our server as you go, and the door is a real endpoint. Press a button and see. There is a working camera scanner underneath if you want to prove it, but you shouldn't have to reach for your phone to find out what this does.

1 · The ticket

Every ticket is random, signed on our server, and good for exactly one scan.

2 · The door

Issue a ticket and the door wakes up.

Why it holds up

What the door checks.

Signed, not just random

The code carries a signature of itself. A door scanner can throw out a forgery on the spot, with no network and nothing to look up — which matters when the signal in the foyer is one bar.

Good for exactly one scan

The first scan admits. The second says so. Screenshot it, forward it, print it twice — the door still only opens once.

Readable by a human

No 0/O or 1/I in the alphabet, so a code can be read down a phone line when a camera won't focus. Every scanner needs a fallback that works in the dark with cold hands.

The cinema build runs the other half of this idea: the QR opens a ticket page, and the usher's scanner checks it against the booking — so a refund taken an hour ago is already known at the door. A real build usually wants both. See the cinema.

Talk to us about ticketing