DIZKO
Dizko · InfoHub · How Dizko works

How Dizko works

Scanning tickets at the door with Dizko

Dizko · August 15, 2026 · 4 min read

The door screen lives at /organizer/events/<event>/door. It runs in a normal browser tab and in the installed Dizko app, on iPhone and Android, with no dedicated hardware. Open it, tap to scan Dizko tickets, and point the camera at each QR.

What is on the screen

One surface carries the whole door:

The verdicts

VerdictMeaningWhat to do
AdmittedValid ticket, first scan. Checked in and counted.Let them in.
Already inThis ticket was scanned before. Shows when, and at which gate.First scan wins. Turn the copy away.
Wrong eventA real ticket, for a different event.Redirect them.
ReplacedThe ticket was transferred. This QR retired when the new holder claimed it.The current owner holds the live QR.
Refunded or voidThe order was refunded or cancelled after the ticket was issued.Not valid.
Not foundNot a Dizko ticket, or forged.Turn away.

The useful one is "already in", because it tells you the time and the gate of the original scan. That converts an argument into a fact.

Why the door needs signal

Every scan is verified against the server rather than against a list cached on the phone. That is what stops a screenshot of an already-used ticket getting in, and it is the whole reason the verdicts above can be trusted.

The trade-off is that the scanner needs a connection. Offline, it refuses loudly rather than silently admitting people, which is the correct failure mode but a bad surprise at 22:00. So:

The manual fallback

Cracked screens, dead phones, brightness turned down, a QR printed badly. Every ticket carries a short reference like DZ7K2M9QRT, and the door screen searches by that code and by name. It is slower than scanning, which is exactly why it belongs to the second door person rather than the one holding the queue.

Reversing a mistake

Scanned the wrong person, or admitted someone who then could not come in? Reverse the check-in from the door screen and the headcount corrects itself. Do it immediately, while you still know which ticket it was.

One iOS quirk

The installed app may re-ask for camera permission on each launch. That is Apple's behaviour rather than a bug. A normal Safari tab remembers the permission, so if you are handing a phone to someone at 19:45 and want one less thing to explain, use a browser tab.

Before doors, every time

  1. Issue yourself a comp and scan it. Confirm "admitted".
  2. Scan it again. Confirm "already in".
  3. Reverse the check-in and confirm the count drops.
  4. Search that ticket by short code and by name.
  5. Check the battery and the signal at the door position.

Two minutes, and it removes the entire category of door problems that get discovered in front of a queue.

Questions organizers ask

Does the scanner work on iPhone?

Yes. It uses the browser’s native barcode detection where that exists and a bundled decoder everywhere else, including Safari and the installed app.

What happens if the internet drops mid-door?

The scanner refuses and says so rather than admitting people it cannot verify. Fall back to short-code and name search with a manual count, and fix the connection.

Can two people scan at once?

Yes. Both see the same live state, and the "already in" verdict shows which gate scanned a ticket first, so duplicates are caught across doors.

Do comps scan like paid tickets?

Yes. Complimentary tickets carry a normal QR, use capacity, and appear in the headcount, which is what keeps your door count honest.