A QR code event ticket is a square code on a participant’s ticket that your staff scan at the entrance. The scan looks up that person’s registration and shows whether the ticket belongs to this event and has been paid for. The code only points to a record, and the record gives the answer.
That is why a good check-in plan covers people, phones and network, and not just the code.
How a QR ticket gets created
On Laces, the ticket is created by the registration itself. The organizer never makes or sends tickets by hand.
- A participant opens your event link in a browser. They need no app and no account.
- They choose a ticket, enter their details and pay. On a free ticket, there is nothing to pay.
- Once the payment is confirmed, they see an order code and a ticket page straight away.
- An email follows with their ticket and receipt. The ticket can be shown on a phone or printed.
If one person pays for a group, each person on the order gets their own ticket. The QR codes on those tickets all lead to the same order, so the scan lists the names and staff tap the right person. Your participants can read the full journey on how to register and pay, which is a good page to send them before event day.
Why a free QR code generator isn’t enough
If you searched for a QR code ticket generator, be careful. A free generator turns a link into a picture. It can’t tell you who paid, it gives everyone the same image, and anyone can copy it. A QR code that opens your website is an advert, not proof of admission.
A ticket needs a record behind it, one for each registration. To create and sell QR tickets on Laces, you set up your ticket types and prices in the app, get your organization cleared, and share your event link or event QR code. The tickets are created as people register, so there’s nothing to generate, print or send.
Keep personal details out of the code itself, on any system. A Laces ticket’s QR code holds a link with the order code, and no name or phone number. Anyone with that code can open the ticket page, so ask people not to post their tickets online.
For country details, see the guides to selling tickets in Uganda, Kenya, Ghana, Rwanda and Zambia.
What happens when staff scan a ticket
A team member opens the Laces app, points the camera at the code and reads the result. A valid scan records the person’s arrival automatically, so there is no second button to press. If your event also hands out kit, that handover stays a separate, deliberate tap. Once the kit has gone, the ticket still reads as verified, with a note saying so.
Here is what staff can see, and what they should do next.
| The app says | What it means | What to do |
|---|---|---|
| Ticket verified | Paid and valid for this event | Check the name and let them in |
| Payment not complete | The registration was never paid for | Send them to the help desk |
| Entry cancelled | Cancelled or refunded | Send them to the help desk |
| No ticket for that code | Nothing in this event matches, or they have the wrong event | Check the event, then search by name or phone |
| Could not read that code | The code is damaged or covered | Try again, or type the order code |
| Not a Laces ticket | They showed some other QR code, such as a poster | Ask for the code on their ticket or email |
| Could not check that ticket | The lookup did not go through | Try again. This is not a refusal |
The last row matters most in a queue. A failed lookup says nothing about the person standing in front of you, so train staff not to turn anyone away because of it.
Screenshots and forwarded tickets
A screenshot of a ticket will usually scan. So will a photo of someone else’s screen. What protects you is the record behind the code, and a person who reads the screen.
A second scan of the same ticket does not turn red on Laces. The screen still says the ticket is verified, and it shows a label such as “Checked in 10:42” with the time of the first arrival. Your staff need to know what that label means:
- If the person says this is their first time through the gate, an earlier check-in time is a warning sign.
- Compare the name on the screen with the person in front of you where your event needs it.
- Send the case to the help desk rather than arguing in the queue.
- If you allow people to leave and come back, tell staff, so a repeat scan is not treated as fraud.
- A scan doesn’t check the date on a day ticket, so staff need to read the ticket name at a multi-day event.
The scan shows the name and ticket type, so gate staff do not need to open the wider registration list. Our guide to preventing duplicate or fake tickets goes further into door rules.
Plan for network at the gate
Scanning on Laces looks the ticket up over the internet, so the phone needs a data connection at the moment of the scan. Without one, the app shows “Could not check that ticket” and asks staff to try again. Do not plan a gate on the hope that the signal will hold.
Visit the venue at the same time of day as your event, and test the data on your actual phones. Then:
- Carry SIM cards from more than one network, because coverage differs by venue.
- Choose a hotspot phone and keep it charged and close to the gate.
- Decide in advance what staff do if the network fails completely. Name the person who makes that call, and print a paper backup list.
Prepare the gate: a short checklist
A week before
- Get your organization’s payment approval if you do not have it yet. Registration stays closed until then, even on free tickets.
- Invite your gate team by email. Each volunteer is tied to this one event.
- Work out how many lanes you need. Our guide to checking in 1,000 attendees shows the sum.
- Tell participants to keep the ticket email handy and arrive with a charged phone or a printout.
The day before
- Install the app on every scanning phone and sign in. The phone will ask for camera permission once, so grant it now and not at the gate.
- Scan a real ticket on every phone that will be used. Use a free test ticket if you want to avoid a payment.
- Charge every phone, and pack power banks.
On the day
- Set up one help desk apart from the scanning line. A hard case should never hold up the people behind it.
- Use one queue per scanner, and make it obvious where each one starts.
- Keep shade over the scanners if you can. Glare on a participant’s screen is a common cause of failed scans.
- Put your event’s QR code at the entrance, so walk-ups can register and pay on their own phone while registration is open. Laces does not record cash, so if you also accept it, keep a separate signed list and reconcile it yourself.
When someone has no scannable ticket
Cracked screens and lost emails are normal on any event day, so give staff the way through in advance.
Staff can type an order code into the app, or search by name or phone. If a participant cannot find their email, they can look the order up at Find your ticket using their order code. Tickets are delivered by email, and Laces asks for the email address twice at registration to reduce mistyped addresses.
To see how scanning fits with orders, payments and the participant list, read managing registrations, payments and attendance in one place.
Frequently asked questions
Can a screenshot of a QR ticket be used?
Usually yes, it will scan. If the same ticket has already been checked in, the screen shows the time of that first arrival, so staff can spot a repeat.
Does a QR code prove payment by itself?
No. The app checks the code against the registration record, and an unpaid registration shows “Payment not complete”.
Can volunteers scan tickets?
Yes. Invite your team to scan at the door, and hand a volunteer the scanner for one event and nothing else. Volunteers do not see your revenue.
Does scanning work without internet?
No. The check-in scan looks the ticket up online, so the phone needs a data connection. If the lookup does not go through, the app asks staff to try again.
Do participants need the Laces app?
No. Participants register in a browser and show the ticket from their email or ticket page. Only your team uses the app.
Run your next check-in with a scan
Creating an event on Laces is free. Each participant gets a QR ticket by email, and your team scans it with the app.
Read next
For organizersHow to Manage Event Registrations, Payments and Attendance in One PlaceHow to run event registrations, payments and attendance from one record: the workflow, team access, numbers to track, exports and handling exceptions.4 Nov 2026 · 6 min read
For organizersHow to Sell Event Tickets Online in Uganda Using Mobile MoneySell event tickets online in Uganda: set up your tickets, get cleared to collect mobile money, share one link, scan at the door and withdraw your earnings.4 Nov 2026 · 6 min read
For participantsHow to Register for an Event on Laces: Step-by-StepHow to register for an event on Laces: the details you enter, how to pay, where your ticket goes, and what to do if something goes wrong. No app needed.4 Nov 2026 · 6 min read
