KoratA Korat event ticket is one entry right tied to the holder's account, not an image or a PDF that can be copied and forwarded endlessly — every scan at the door checks against the real database, and knows whether that ticket has already been used. Events is a tile every business type gets, so a restaurant selling places at a supper club keeps its kitchen display alongside it, and the same QR mechanism issues queue tickets at a counter.
Reserving a place, and priced zones
Nothing on an organiser's page proves who they are either — trust badges state evidence and never a verdict, and pay-before-entry sits on top of that. An event that splits tickets into zones — say, different prices for different seating — always forces a zone choice before booking; the system never picks a zone on a customer's behalf when one is required, so nobody ends up with the wrong-priced ticket by accident.
Pay-before-entry events — a slip an organiser checks
For events set to require payment before entry, a buyer attaches a transfer slip to the booking, and the organiser reviews that slip and confirms entry themselves. This is not an automatic charge through a payment gateway — money never passes through Korat at all, as the payments guide sets out — it's an evidence-attachment step an organiser checks before a ticket becomes usable at the door.
Door check-in — re-scan detection, and an ID check when it matters
Door staff scan a ticket's QR code to check someone in. The system answers clearly whether that scan just admitted someone for the first time or the ticket was already checked in before — two different answers staff have to actually read, not just whether the scan succeeded or failed, so nobody gets in twice on one ticket. For events serving alcohol where the system can't read an age from the ticket or the age doesn't clear the bar, staff are told to ask for ID at the door as well; the age rules behind that are per country and held as data, not typed into a screen.
Transferring a ticket
A ticket holder can transfer their own ticket to someone else if the organiser has allowed transfers for that event — a transfer request has a time limit and expires on its own if nobody responds. The recipient has to accept before ownership actually changes. Selling tickets carries no monthly fee; what a shop package and the add-on plugins each include is on the plans page. An organiser can turn transfers off for the whole event, and once turned off, no new transfer request can be started at all.
Payment for a pay-before-entry event is a slip the organiser reviews themselves — not an automatic charge or a payment-gateway connection.
A ticket that's already checked in cannot be reused. The system gives a clearly different answer for "admitted" versus "already checked in," specifically to stop one ticket admitting two people.
Ticket transfers only work for events the organiser has explicitly allowed. An event with transfers turned off has no way to hand a ticket to someone else at all.