Running a ticketed event has always had the same few hard parts. Getting people to register. Collecting payment if tickets cost money. Making sure you don't oversell. Getting attendees their confirmation without chasing them. And then, on the day itself, actually getting people through the door quickly and fairly.
Most organisers either wire together a combination of forms, spreadsheets, and UPI screenshots — which works until it doesn't — or they reach for a platform built for large venues that adds overhead and fees a 300-person college event can't justify.
Boni Event Ticketing is a hosted ticketing platform designed for this gap. It is live and in active use for real events. This article explains what it is, what it does, who it is for, and what is still being built out.
What It Is
Boni Event Ticketing is a multi-tenant platform that handles the full ticketing cycle for an event: registration, payment (for paid tickets), QR pass delivery, and gate check-in.
Each organiser gets a public booking page at a shareable URL. Attendees visit that page, pick their ticket type, and complete registration — with payment handled in the same flow for paid tiers. After that, a confirmation email goes out automatically with a unique QR code. On event day, gate crew scan those QR codes. The system rejects any duplicate scan.
It is a Boni product. Both the attendee booking pages and the organiser dashboard are hosted by Boni and open in a browser. No separate app is needed on either side.
The Real Problem It Solves
Here is what goes wrong without a proper system:
Registrations without capacity control. A Google Form or WhatsApp link keeps accepting entries even after you are full. You find out when 400 people show up to a 200-seat venue.
Manual payment collection. People send money to a personal UPI ID. You spend hours reconciling screenshots. Some people claim to have paid when they haven't. Some pay and never get a confirmation.
No confirmation that works at the gate. A WhatsApp screenshot as "proof" cannot be verified at speed. Anyone can forward it. A name-check spreadsheet is slow and argument-prone.
Gate chaos. Two volunteers with a printed list and no way to detect duplicate entries. Long queues, frustrated attendees, and a bad start to the event.
Boni Event Ticketing addresses each of these directly, in one flow.
How It Works, Step by Step
1. Create Your Event
An organiser sets up their event through the organiser panel. They add the event name, date, venue, description, and any cover image. Then they configure ticket types.
Ticket types can be free or paid. You can have multiple types on the same event — for example, a free general entry and a paid delegate pass, or a student tier and a parent tier at different prices. Each ticket type has its own capacity limit. When a type sells out, it closes automatically.
The platform also supports optional booking rules — things like requiring a phone number or email address on registration, or limiting each person to one ticket.
2. Publish the Booking Page
Once the event is set up, it gets a public booking URL. The organiser shares this link anywhere — WhatsApp, Instagram, email. That is all they need to do.
The booking page works on mobile, works in WhatsApp, and works without the attendee creating any account.
3. Attendees Book
Attendees visit the page, pick their ticket type and quantity, and fill in the required details. For free events, they confirm and that's it. For paid events, they pay through a hosted payment link — standard payment methods are supported.
Inventory is tracked in real time. The system uses an oversell guard: it holds the slot while a person is in the booking flow, confirms the hold on successful booking, and releases expired holds if someone abandons. You cannot end up with more confirmed bookings than capacity.
4. QR Pass Delivered by Email
After a booking is confirmed — whether free or paid — the attendee gets an automatic confirmation email. It contains their QR code ticket.
This is the QR pass they bring to the event. It is unique to their booking. The QR encodes a signed token; it cannot be faked or tampered with. The same email also includes a link to their order page, where they can view their booking and ticket details.
No manual work by the organiser. No separate QR generation. No WhatsApp forwarding needed — though the order link can be shared via WhatsApp by the attendee if they want.
5. Gate Check-In on Event Day
Gate crew log into the organiser panel on their phones and open the scan interface. The page is mobile-first and designed for quick scanning.
When a QR code is scanned, one of three things happens:
- Valid, first scan: entry is allowed. The system shows the attendee's name and ticket type.
- Duplicate scan: the system rejects it and shows who claimed that ticket, at what time, and at which gate. The gate crew can see it was already used.
- Invalid or void ticket: the scan is rejected with a clear message.
Each scan result shows as a clear popup. The device buzzes. The crew presses OK and scans the next person. It is fast and unambiguous.
The scan tool works for multiple simultaneous gate points. Multiple phones can scan in parallel.
6. Scan-Only Gate Accounts
Not everyone at the gate needs access to the full organiser dashboard. A temporary crew member — a student volunteer, a hired security person — should only be able to scan tickets, not view booking data, change event settings, or do anything else.
Boni Event Ticketing has scan-only accounts for exactly this. A scan-only login can open the gate check-in interface and nothing else. All other panel functions are blocked. If they navigate elsewhere, they land back on the scan page. This is live as of July 2026.
What Organisers Can Configure
- Free events: registration only, no payment step, QR pass issued immediately on booking.
- Paid events: hosted payment link in the booking flow; QR pass issued after payment is confirmed.
- Pay at venue: organiser enables a mode where attendees register and confirm intent, but pay at the door. The panel can mark tickets paid later.
- Multiple ticket types: different prices, capacities, and rules on the same event page.
- Booking rules: require phone number, require email, limit tickets per registration.
- Capacity limits: per ticket type, with automatic enforcement and hold/release logic.
- Scan-only gate accounts: staff who can only scan, nothing else.
- Organiser-scoped logins: a separate login for the event host that gives access to their events and orders only — not to the broader platform.
Who This Is For
Community event organisers. Supper clubs, meetups, local group gatherings, cultural associations. Events where the organiser is also the person setting up the ticketing the week before.
College and student events. Cultural fests, tech fests, workshops, hackathons, graduation send-offs. Events with free entry plus a paid delegate tier, or capped attendance.
Workshop and training hosts. Paid registrations for workshops, classes, training sessions where capacity is limited and every attendee needs a confirmation.
Small cultural shows. Theatre, music, dance performances. Ticketed seating with a real gate.
Any event where the organiser wants the whole flow handled without stitching together a form, a payment tool, a QR generator, and a spreadsheet.
It is not built for large stadium events with complex seating maps, wristband integrations, or multi-day festival logistics at scale. For events up to a few thousand attendees where the organiser needs a clean booking page and functional gate check-in, it fits.
What Is Live and What Is Still Being Built
It is worth being direct about this. The platform is live and has been used for real events. The core booking, payment, QR pass issuance, and gate check-in flows are all production-verified. Scan-only gate accounts are live as of July 2026.
Some things are still in active development:
- The platform currently requires organiser onboarding through Boni — self-serve event creation for any organiser is not yet available as a fully open flow.
- Post-event reporting and attendance analytics are basic. Real-time admission count is visible during the event, but detailed post-event dashboards are still being built out.
- WhatsApp follow-up for orders (resending the ticket link via WhatsApp) is planned but not yet wired.
- The ONDC integration — which would make events discoverable on the open commerce network — is connected at the technical level but distribution reach via that channel is still early.
If any of these things matter for your specific event, it is worth asking directly when you get in touch.
How to Get Started
The platform is live. Real events are running on it now.
If you are organising an event — a college fest, a community gathering, a paid workshop, a cultural show — and you want to run it without the spreadsheet chaos, the UPI screenshot problem, or the name-check queue at the gate, Boni Event Ticketing is available today. Get in touch through the site and a real person will respond.
Top comments (0)