Selling tickets online is not the hard part. Selling out is. But the mechanics still trip up first-time organizers constantly — the wrong pricing structure, a refund policy written after the first refund request, a door that takes forty minutes to clear because someone is checking names against a printed list.
This guide covers the whole path, in the order you will actually hit it.
1. Decide what you are selling before you decide how
The single most common mistake is opening a ticketing account before deciding on the ticket structure. Work out these four things first:
- Capacity. The real number the venue will let in, not the number on the brochure.
- Tiers. Are you selling one kind of ticket, or several?
- Price points. Covered in detail in our pricing guide.
- The sale window. When each tier goes on sale and when it stops.
Everything downstream depends on these. Changing the tier structure after tickets are live is possible but messy — people who bought at one price will notice when the structure changes.
2. Choose how you sell
You have three broad options in India.
A ticketing platform. You list the event, the platform handles payments, ticket delivery, and the payment gateway relationship. You pay a commission per ticket. This is the default for a reason: you are not building a payment integration for a one-night event, and you are not liable for the gateway compliance.
Your own website plus a payment gateway. Full control, no per-ticket commission beyond gateway charges, but you own everything — payment integration, ticket generation, delivery, refund handling, reconciliation, and the entry system on the night.
Direct payments — UPI to a personal number, cash at the door. Zero setup, and it works for a fifty-person event among people who know you. It stops working the moment strangers are buying, because you have no way of proving who paid, no way of preventing double entry, and no clean record for accounting.
For anything ticketed and public, use a platform.
3. Set up the listing so it actually converts
A listing is a landing page. Treat it like one.
Title. Say what it is and where. "Saturday Night Live Music" tells a search engine nothing. "Anhad Live in Jaipur — Rooftop Acoustic Night" tells it everything.
The first two lines matter most. They become the search snippet and the WhatsApp preview. Front-load the specifics: who is playing, where, when.
Images. One strong horizontal banner, ideally 1200×630 or wider. This is the image that appears when the link is shared, and a shared link with a good image gets meaningfully more clicks than one without.
Venue detail, in full. Address, landmark, and a map pin. "Near the circle" causes calls on the night.
Terms, up front. Age restrictions, entry cut-off, re-entry policy, what is not allowed in. Every one of these that is not on the listing becomes an argument at the gate.
4. Payments: what you actually need
In India, taking online card and UPI payments means a payment gateway, and a gateway means KYC.
What a gateway will ask for:
- PAN of the business or the individual
- Bank account and a cancelled cheque or statement
- GST registration, if you have one
- Business proof — incorporation certificate, partnership deed, or Udyam registration for a sole proprietorship
- Address proof
Allow a week for this. First-time organizers routinely leave gateway onboarding until the week they want to go live and lose selling days to it.
Payment methods to support. UPI is the majority of transactions for Indian event tickets — it should be first and most prominent. Cards and net banking cover the rest. Wallets are increasingly optional.
Settlement timing. Gateways typically settle T+2 to T+7 business days. This matters more than it sounds: if you are counting on ticket revenue to pay the venue advance, check the settlement schedule before you promise anyone anything.
When you use a platform, all of this sits with the platform, and you receive a payout net of commission. That is most of what you are paying the commission for.
5. GST and invoicing
Two separate questions, and organizers conflate them.
Do you need to register for GST? If your aggregate annual turnover crosses the threshold for services, yes. Inter-state supply and certain event categories can also trigger registration independent of turnover. This depends on your specific situation.
What rate applies to admission? Rates for admission to entertainment events depend on the category of event and, for several categories, on the ticket price — with a lower-value exemption applying to some kinds of performance. Cinema tickets sit on a different slab structure again.
Both of these change, and the details matter. Confirm your registration requirement and the applicable rate with a chartered accountant before you set prices — not after, because the answer determines whether your advertised price is inclusive or exclusive of tax.
Practically, what you need in place before selling:
- A decision on whether the displayed price is tax-inclusive (strongly preferred — a price that grows at checkout costs you sales)
- A GSTIN on the invoice if you are registered
- A record of every transaction, which any real ticketing platform gives you as an exportable report
6. Write the refund policy before you sell a ticket
Not after. The first refund request will arrive within hours of going live, and whatever you say to that person becomes your policy whether you meant it to or not.
Decide and publish:
- Are tickets refundable at all? Many events are not, and that is a legitimate position if it is stated clearly before purchase.
- If refundable, until when? A common structure: full refund up to 7 days before, partial up to 48 hours, none after.
- What happens if you cancel or reschedule? A full refund on cancellation is the only defensible position. For a reschedule, offer the choice of carrying the ticket over or refunding.
- Are booking fees refunded? Usually not, and say so.
Put this on the listing, not in a document nobody opens.
7. Deliver tickets people cannot forge or share
A ticket is only useful if it can be verified at the door. Three levels, worst to best:
A name on a list. Slow, disputable, unscalable.
A PDF or an emailed code. Better, but a code that is only checked visually can be screenshotted and forwarded to five people, and all five will show up.
A signed QR code, scanned and marked used. This is the standard, and it is what solves the actual problem. The scan checks a cryptographic signature — so a fabricated code fails before it touches the database — and marks the ticket used in the same operation, so the second person presenting the same screenshot is refused.
That last property is the one that matters. Any system where checking the ticket and marking it used are two separate steps will, on a busy door, let duplicates through.
8. Plan the door
Entry is where events lose their reputation. Some arithmetic: a scan takes about five seconds when it works. Five hundred guests through one scanning point is forty minutes of queue if everyone arrives at once — and they do, in the fifteen minutes before the headline act.
- One scanning point per 150–200 expected guests in the peak arrival window.
- Charge every phone, and bring power banks. A dead scanner is a stopped queue.
- Have an offline fallback. Venue wifi fails. A system that can accept a manually typed code, or that queues scans and syncs later, saves the night.
- Brief the staff on the refusal script. They will meet forged screenshots and genuinely confused guests, and the difference between a polite process and an argument is entirely preparation.
9. After the event
- Reconcile. Tickets sold against tickets scanned against money settled. Discrepancies are much easier to chase in the same week.
- Export the data. Attendee list, sales by tier, sales by day. This is what tells you whether early-bird pricing worked and when your sales actually happened.
- Collect feedback while it is fresh — within 24 hours, or the response rate falls off a cliff.
- Keep the list. The single most valuable asset a repeat organizer has is a list of people who have already paid to see something they put on. Your second event is far cheaper to sell than your first, but only if you kept the list from the first.
The realistic timeline
| When | What |
|---|---|
| 8+ weeks out | Venue confirmed, date locked, gateway or platform KYC started |
| 6 weeks out | Listing live, early-bird tier on sale, refund policy published |
| 4 weeks out | Announcement push, early-bird closes |
| 2 weeks out | Regular tier push, paid promotion if you are running it |
| 1 week out | Reminder to everyone who viewed and did not buy |
| 48 hours out | Final push, door logistics confirmed, staff briefed |
| Day of | Scanners charged, offline fallback tested |
| Day after | Reconcile, export, thank the list |
Start selling
List your event on Tixit — UPI and card payments, signed QR tickets, a scanner app for the door, and CSV exports for reconciliation, with no setup cost.
Next: how to price your tickets and how to promote an event in India.