Guide
How to stop fake and duplicate tickets at the door
When an organizer says "I want to stop fake tickets", they are almost never talking about sophisticated forgery. Real fraud at the door is much more boring and much more frequent: the same ticket, used twice.
A note before you start: ENTRÁ is an Argentine ticketing platform. It sells tickets for events held in Argentina, priced in Argentine pesos (ARS). What this guide says applies to any ticketing platform; when it describes how ENTRÁ works, it means in Argentina.
Someone sends a screenshot of the QR on WhatsApp so a friend can get in. Someone resells a ticket they already used. Someone forwards the purchase email to three people. In all three cases the code is legitimate: what fails is not the paper, it is the control.
The problem is not the paper, it is the control
A ticket printed by the best printer in town can be photocopied. A QR can be screenshotted. No format is secure on its own. The only thing that makes a ticket secure is a code that is unique, single use and validated against a database shared by every door.
That is the difference with a paper list: a list does not stop the same ticket from being used twice, leaves no record of what time each person came in, and creates queues at volume.
What the scanner has to reject (and how)
Serious access control does not just say "yes" or "no". It has to say why it rejects, because each case is handled differently at the door. At ENTRÁ the scanner tells these cases apart:
- Ticket for another event. The QR is valid, just not here. It happens more than you would think when an organizer runs several dates.
- Cancelled or refunded ticket. The ticket existed, but it is no longer valid.
- Already used. The most common case. The system returns
DENEGADO · YA UTILIZADO(denied, already used) and how long ago that code came in. - Not valid today (multi-day events). The ticket is fine, but that day is not enabled for it.
- Already entered today (multi-day). The ticket works on each enabled day, but once per day: it is not burned all at once.
That "came in 8 minutes ago" looks like a detail and it is the most useful piece of information of all: it gives door staff something concrete to say, and turns an argument into a fact.
Every attempt is logged
Every scan, accepted or denied, goes into the event's entry history: which code, which ticket type, what time and what result. It is useful for three things:
- Solving it on the spot: seeing where and when the code that now shows up as a duplicate came in.
- Having evidence if someone complains later.
- Spotting patterns: if lots of duplicates show up for the same ticket type or the same sale, there is something to look into.
Losing the internet cannot bring down the door
This is the question that separates serious control from the rest. At ENTRÁ the scanner marks the ticket as used in its local cache instantly, so the next scan of the same QR sees it as used even without a connection, and it syncs with the server on its own when the connection comes back.
That said: a contingency is a plan, not a feature. An event with thousands of people saturates the mobile network. You should still bring backup connectivity and test it before the doors open, not when there is already a queue.
Give your audience a legitimate way
Many of the screenshots going around are not bad faith: it is people who cannot go and want to pass the ticket on. If you do not give them a way to do it, they will do it anyway, badly.
That is why it matters to enable official transfer: when a ticket is transferred, the old code is invalidated and a new QR is generated for the person receiving it. The old screenshot stops working on its own. It is how you cut fraud without fighting your audience.
Technology is half of it: the protocol is the other half
The system tells you the QR is a duplicate. What happens next is down to your operation, and it is worth having it written down before the event:
- Who decides. So door staff do not have to improvise or go looking for someone.
- Where it gets sorted out. A spot to the side, out of the line. A rejection argued at the door holds up everyone behind.
- What you tell the person. With the data from the history: what time that code came in and through which door.
- What happens with the case. Who it is escalated to, what gets recorded.
Quick checklist
- A unique code per ticket, single use.
- Validation against a shared database for every door.
- Rejections that give the reason, with the time of the previous entry.
- A history of every attempt, accepted and denied.
- Works offline, with backup connectivity tested.
- Official transfer enabled.
- A written door protocol the team knows.
Frequently asked questions
How do you stop people getting in with a screenshot of someone else's ticket?
With a single use QR validated against a central database. The screenshot holds the same code as the original, so whoever arrives first gets in and the second scan is rejected. At ENTRÁ, an Argentine ticketing platform, the scanner returns DENEGADO · YA UTILIZADO (denied, already used) together with how long ago that code came in, which is what door staff need to handle it without an argument.
Does it matter whether the ticket is printed or shown on a phone?
No: what gets validated is the code, not the format. A printed PDF and a phone screen carry the same code and behave the same way. What makes it secure is that the code is unique, single use and validated against a database shared by every door.
What happens if the internet goes down at the door?
At ENTRÁ access control keeps working offline: the scanner marks the ticket as used in its local cache instantly, so the next scan of the same QR sees it as used even without a connection, and it syncs with the server on its own when the connection returns. Even so, a serious event brings backup connectivity: a contingency is a plan, not a feature.
How does door control work for multi-day events?
The ticket is validated per day: the system checks that the day is one of the days enabled for that ticket and that the person has not already come in that day. If the day does not match, it is rejected; if they already came in today, it is rejected as a duplicate. The ticket is not used up all at once: it works on each enabled day.
Running the door at an event in Argentina?
Every ticket issued by ENTRÁ is a unique, single use QR, with access control built in at no extra cost: you scan from a phone, the system rejects duplicates showing what time that code came in, and everything is logged. Write to us and we will show you how it works.
Ask us on WhatsApp