How QR Event Tickets and Check-In Work

Did you know? A QR code on your concert ticket may look like an ordinary black-and-white square, yet scanning it at the entrance can change what happens the next time somebody presents that same ticket. The trick is not that the ink disappears. It is that the ticketing system remembers the scan.

Quick answer: a ticket QR code usually holds a ticket identifier or another value the event’s check-in system can recognise. When staff scan it, the system validates the ticket against the relevant event and records entry. If the same credential is presented again, the system can warn that it has already been used. Some events use changing mobile barcodes instead; not every ticket uses a QR code.

The 30-second guide

Issue a ticket: the organiser or ticketing provider creates a ticket record for the event.
Show a code: the customer receives a machine-readable QR code or barcode linked to that record.
Scan at the gate: authorised staff use the event’s check-in application or scanner.
Check validity: the system determines whether the credential belongs to the right event, date, session and allowed admission state.
Record entry: a successful check-in can mark a one-entry credential as used so another scan raises an alert.

What is actually inside an event ticket?

The printed square does not need to store the venue’s entire guest list, your receipt history or a photograph of your identity card. In a common design, the code contains an identifier that connects to a ticket record held by the ticket provider. Other designs encode a protected credential that software can check. The exact content varies across platforms.

Think of a coat-check ticket: its number helps staff find a matching record. A QR ticket is an electronic version of that idea, but the event system can also track whether a credential has already been accepted.

The code can still be decoded by a camera. But decoding the code and confirming admission are different tasks. A generic camera app might read a string of characters while an authorised event scanner knows how to verify the right ticket database.

Step 1: Buying or registering creates a record

Suppose a science museum offers a timed-entry ticket for 11 am on Saturday. After someone completes registration, the booking system creates a record. It may include the event, chosen time slot, ticket type and the status of the booking. The customer receives a QR code representing that ticket.

For a free school open house, the process may be similar even though no money changes hands. Registration produces a credential, and the check-in system later uses that credential to find or validate the visitor’s booking.

A PDF, email or app-based ticket can all present machine-readable credentials. The important difference is how the provider verifies them, not whether the image is printed on paper or shown on a phone.

Step 2: The scanner checks the event’s rules

At the door, the usher opens the event’s authorised check-in app and points its camera at the code. In systems such as Eventbrite Organizer, a successful scan checks the attendee in and displays a confirmation. A code for another event or an already-checked-in ticket can trigger an error.

Why is that useful? Because a QR symbol alone is just data. Event admission needs context: is this credential valid here and now? Was it issued for a different session? Has the organiser cancelled or transferred it? The ticketing system, not the square, applies those rules.

Step 3: A check-in changes the ticket’s state

Imagine the ticket database has a simple status field: not checked in. When the credential is accepted, the authorised scanning system records the check-in. A second attempted entry using the same credential can then be rejected or flagged for staff.

This is how a copied image can fail to get two people through a gate: both copies may contain the same identifier. Once one copy has been accepted, the other copy is not a second valid ticket. Ticketmaster Singapore explains that its scanner can alert attendants when the same barcode has already been scanned.

Important: a duplicate-alert system does not establish which person rightfully owns a ticket. The first person to present a copied credential may get through before a legitimate buyer arrives. That is why organisers ask customers not to reveal their ticket QR codes or barcodes on social media.

Why screenshots are sometimes rejected

Not every event ticket is a static picture. Some ticketing products display a credential that changes periodically or requires the official mobile ticket in an account or wallet. The provider may design the system to make screenshots or copied images unreliable.

Ticketmaster describes a moving barcode feature in some markets, where the displayed barcode refreshes frequently. Its Singapore help pages also warn that screenshots or photographs of certain mobile tickets are not accepted, while print-at-home tickets may have different presentation rules. The correct method depends on the event and ticket type.

So do not assume ‘any picture of my QR code is my ticket’. Read the delivery instructions. A valid PDF ticket, an authorised wallet pass and an in-app dynamic credential can look superficially similar while requiring different handling at the entrance.

How can the scanner work when the venue’s internet is weak?

Outdoor festivals, packed stadiums and basement halls are not always friendly to mobile networks. Some check-in platforms support modes where tickets and check-in data can be available locally for staff, with updates synchronised when connectivity returns. Other systems require live online validation.

Offline scanning introduces an engineering challenge. If two separate gates cannot exchange check-in state immediately, they could both accept a copy before their records are synchronised. Good event systems define procedures for online validation, offline operation, conflict handling and staff escalation. The exact safeguards vary by provider and event.

This is a fascinating lesson in computer science. The barcode can be perfectly readable at both gates while the distributed database still has to decide who has already entered.

A school event example: one registration, one check-in

Imagine a school registration desk welcoming 300 families. Parents receive a QR ticket after signing up. Staff scan the code, check the appropriate session and mark attendance. If someone cannot open their email, authorised staff may look up the registration manually, following the organiser’s procedures.

The organisers should separate attendance evidence from broader questions such as identity, payment status and consent. A successful scan establishes that a credential was presented and accepted. It does not automatically prove every person named on a booking arrived, and it should not be treated as a universal identification document.

Why ticket transfers should use official tools

Suppose you bought two tickets and want a friend to use one. Sending an image might not transfer the underlying ownership record, especially when the code changes or tickets are linked to an account. An official ticket-transfer function may update the valid credential or its authorised holder.

Follow the provider’s current instructions for the specific event. Keep original purchase confirmation and account access. If two people arrive with competing copies, staff may need proof of purchase and account verification before resolving the dispute.

A five-minute learning experiment

Draw three columns on a sheet of paper: ticket record, code presented and gate result. Create three fictional records, A, B and C, all marked ‘unused’. Now simulate scans: A at the correct gate; A again; B at the wrong event; and C at the right gate. Decide which should succeed and which need an error.

Next imagine two gates operating offline. Both receive the same copy of ticket C before they can share updates. What extra system design would you need to prevent or resolve conflicting admissions? The exercise shows why reliable software must handle both information and timing.

Questions people often ask

Does a QR code automatically make a ticket genuine?

No. A QR code can be copied or generated by anyone. The authorised ticketing system must validate the credential against its own records or rules.

Can two people enter with a screenshot of the same ticket?

Ordinary one-entry systems can flag reuse, but an unauthorised first scan may still cause trouble for the legitimate holder. Some mobile tickets reject screenshots entirely.

Why won’t my phone’s camera tell me whether the ticket is valid?

Your camera can read the encoded pattern. Ticket validation requires the organiser’s authorised application and records, not just an ordinary QR scanner.

What if my phone battery dies before entry?

Follow the event’s stated delivery and admission policy. Some tickets can be printed, others require a live mobile credential, and many organisers provide a ticket-resolution counter. Check before travelling.

The idea to remember

A ticket QR code is a key to a record; the check-in system decides whether the key is valid and unused. The square makes entry quick. The database and admission rules provide the control.

Keep learning with How a Square Stores Words, Links and Numbers, Static vs Dynamic QR Codes Explained and Scan Safely and Spot QR Code Scams.

Sources and further reading

Eventbrite: Check in Attendees With the Organizer App — validation, check-in and duplicate warnings.
Eventbrite: Prevent Attendees From Sharing Tickets — how repeat scans are handled.
Ticketmaster Singapore: Protecting Your Ticket Barcode — copied credentials and first-scan entry.
Ticketmaster Singapore: Ticket Delivery and Entry — mobile, print-at-home and screenshot policies.
Ticketmaster: Why Some Barcodes Move — an example of refreshing credentials.

Explore the How QR Codes Work series

Each guide explains a different part of the same everyday technology. Choose what you would like to understand next.

How QR Codes Work | How Event Tickets and Check-In Prevent Reuse