ZeyPOS Ticket Control

On event night, there are two scenes at the door: paper lists, “I already took it, bro” arguments, a line out front... or ZeyPOS Ticket Control. The staff member’s phone turns into a verification device: QR scanned, green light on, “Welcome.” Every ticket is single-use, and every entry is logged by the second and by the staff member. It’s the last and most critical link in the ticket chain, from sale to door.

Two seconds at the door: scan, go

The camera reads the QR, and the result appears instantly on screen: valid, used, cancelled, unpaid, invalid — all five with separate, clear warnings. Verification happens on the server with atomic locking: even if the same ticket is scanned at two different doors in the same second, only one gets through. The argument doesn’t end at the door. It ends in the system.

Single-use QR — the end of duplicate tickets

Each ticket is generated with a unique, unpredictable code and burns on first scan: its status instantly flips to “used,” with the time and the staff member who scanned it stamped in. A screenshot shared around cannot get the ticket through the door a second time. If you buy three tickets, you get three separate tickets and three separate QRs — there’s no opening for scams like “one ticket, three entries.”

Greeting by name = silent second check

Door screen — the night’s control panel

• Event selector + live countdown to the event
• Instant counters: sold / entered / no-show / remaining
• Entered and No-Show lists — “who came, who’s still expected” at a glance
• Archive of past events

The staff member only sees the door

The person at the door logs in as an “Event Staff” role: they verify tickets, they see the list — that’s it. No access to revenue, reports, or the dashboard. You hand your overnight staff member a phone, not your system. That’s a deliberate design choice.

Ticket sales on POS rails — five channels, one pool

In ZeyPOS, tickets are not a separate system. They’re a special product flowing through your existing sales rails: the waiter adds it to a table bill while the guest is dining, the cashier sells it at the register, it’s sold at the kiosk, the customer buys it themselves from the QR menu, or a remote customer buys by bank transfer. All five channels write to the same ticket pool — no double sales, no mixed-up lists. And the critical difference: card details are never stored anywhere. There’s no “Should I enter my card number on a ticket site?” fear in ZeyPOS, because the payment goes through the business’s own cash register.

Remote sales: bank transfer + declaration + approval

For customers who can’t come in, the flow is ordered and secure: the customer enters name and phone on the ticket page, receives IBAN instructions with a personal payment code, makes the transfer, and says “I’ve paid.” At that moment, a notification lands on the owner’s phone; the owner checks the bank, approves with one tap — and the ticket is generated that second and sent to the customer’s WhatsApp. No ticket is issued before the money is seen, and the customer never gets surprised at the door.

Tickets on WhatsApp — paper disappears, the phone doesn’t

Once payment is complete, the customer gets a WhatsApp message; on the “my tickets” page, all QRs issued to their phone are ready. The security is subtle: everyone sees only their own tickets — no one gets another guest’s QR. If needed, a thermal receipt can also be printed: both digital and physical.

The owner watches from their pocket

In the owner app, there’s an event module: on the home screen, a countdown card for the upcoming event, sold/entered/no-show/remaining counters, channel breakdown (ZeyPOS in-house / bank transfer / external), and a pending transfer badge. Tickets sold on other platforms can also be entered manually — true occupancy on one screen. When capacity is full, sales stop automatically; your venue doesn’t get caught off guard.