An event ticketing app needs a clear event page, ticket types with set capacity, local payments such as mada, Apple Pay and Tabby, and a unique QR ticket per attendee sent by WhatsApp and email. At the gate it needs a scanner app that accepts each ticket only once and keeps working on weak internet. You can build all of it from a description in Fanann, then test it on a small event before the big one.
- how to build an event ticketing app
- event ticketing system with qr code check in
- qr code ticket scanner app for events
- sell event tickets online with mada
- how much does a ticketing app cost
How do you build an event ticketing app with QR check-in?
An event ticketing app has two halves: a ticket store where the audience buys and pays, and a gate app where organizers scan QR codes at entry. With the Fanann Agent you describe the event, ticket types, payments and entry in plain language, and it builds both halves with the database, payments and notifications, published on your own domain and brand.
Why your own system instead of a public ticketing platform? You own attendee data for marketing future events, control design, pricing and ticket types, and can add what fits you: conference registration forms, family tickets, separate sessions or memberships. Public platforms remain useful for reaching new audiences; the two can coexist.
Events this fits
- Conferences and professional meetups with registration and name badges.
- Concerts and shows with numbered seats or general admission.
- Tournaments, exhibitions and seasonal markets in Ramadan or winter.
- Workshops and in-person courses with limited seats.
- Seasonal events such as Riyadh Season, Eid or National Day activations.
What features does a ticketing app need?
| Part | Core features | Later |
|---|---|---|
| Event page | Name, Hijri and Gregorian date, map location, agenda, terms | Speakers, promo video, FAQs |
| Ticket types | General, VIP, early bird, student, family; each with capacity, price and end date | Seat maps, free invite-only tickets |
| Purchase | Cart, attendee names, coupon, payment, invoice | Tabby and Tamara, corporate bulk purchase |
| Ticket | Unique QR per attendee, sent by WhatsApp and email, shown in the account | Apple Wallet, ticket transfer |
| Gate | Scanner app for staff, single-use acceptance, live headcount | Multiple gates, badge printing |
| Admin | Live sales, attendance, refunds, list exports | Cross-event reports, marketing to past attendees |
The data and the attendee journey: from ad to gate
In plain words, these are the tables the AI will build; review them before it starts:
- Events: name, date and time, venue, total capacity, status (draft, on sale, sold out, ended).
- Ticket types: event, name, price, capacity, sale start and end.
- Orders: buyer, amount, payment method, status, invoice.
- Tickets: order, ticket type, attendee name, unique code, status (valid, used, cancelled).
- Scans: ticket, gate, staff member, time, result (accepted, already used, invalid).
- 1Sees the ad
A Snapchat, TikTok or WhatsApp link opens the event page on their phone.
- 2Chooses and holds
Picks ticket type and quantity; tickets are held 10 minutes while they pay.
- 3Pays
By mada, Apple Pay or card, with an e-invoice that includes VAT.
- 4Receives tickets
WhatsApp and email with one QR per attendee, plus a reminder the day before with location and parking.
- 5Enters in a second
Staff scan the code: green with the name and ticket type, or red if already used.
QR codes and the gate: stopping fraud and queues
Organizers' biggest fears: one screenshot forwarded to ten people, and a long queue because the venue's internet is weak. The fix is designing the ticket and the gate app together.
- A long random code that cannot be guessed, not the order number
- Accepted once, with entry time and gate recorded
- Linked to the attendee name shown on scan
- Cancelled instantly on refund or transfer
- Shown inside the account for sensitive events
- A sequential number anyone can predict
- No usage record, so it works repeatedly
- No name, so it resells easily
- Still valid after a refund
- A generic PDF shared without limit
A gate app that survives the rush
- Downloads valid tickets before doors open, works offline, and syncs scans when the network returns.
- Blocks the same ticket at two gates after sync and shows a clear duplicate alert.
- Manual lookup by name or phone for lost tickets, for supervisors only.
- A live headcount against capacity for safety and crowd flow.
Payments, refunds and the on-sale rush
Ticket payments are special: many people buy in the first minutes, capacity is fixed, and refunds need a clear policy. Connect local payments such as mada, Apple Pay, cards and KNET in Kuwait, and add Tabby and Tamara for pricier tickets if your audience uses them.
| Challenge | Practical fix |
|---|---|
| Overselling | A 10-minute hold during payment, with capacity enforced in the database, not the interface |
| On-sale traffic spike | Autoscaling hosting, a lightweight page, and a load test before announcing |
| Payment fails after a hold | Release tickets automatically when the hold expires and notify the buyer |
| Refunds | A written policy on when and how much, with the ticket cancelled instantly |
| Event cancelled or postponed | A bulk message to attendees with a full refund or transfer to the new date |
For gateways and receipts, read how to add payments to your app; for disputes, read refunds and chargebacks in the Gulf. Fanann runs your app on in-region hosting with autoscaling and daily backups.
Build it with Fanann: a ready prompt
Paste this into Fanann and adjust ticket types and capacity. Ask for the plan first and review the hold and scanning logic carefully.
Build an event ticketing system called 'Tadhkarati', Arabic first with English. The owner creates events: name, Hijri and Gregorian date, time, map location, agenda, terms and an image. Each event has ticket types (general, VIP, early bird, family), each with a price in SAR, capacity and sale start and end dates. Buyers log in by phone with OTP, choose tickets, enter each attendee's name and apply a coupon. Tickets are held for 10 minutes during payment and released automatically if payment is not completed. Payment by mada, Apple Pay and cards, with an e-invoice including VAT. After payment, each attendee gets a ticket with a unique random QR code, sent by WhatsApp and email and shown in the account, plus a reminder one day before. A gate app for staff: camera scanning, green with name and ticket type or red with the reason, single-use acceptance, offline mode with a preloaded list that syncs later, and manual lookup for supervisors. Roles: owner, gate supervisor, scanner, refunds support. Dashboard: live sales per ticket type, attendance versus capacity, refunds and attendee export. Show me the plan and tables before building.
Try it in FanannIf your events are seasonal and also need activity and experience bookings, read events booking app for Saudi seasons.
Event-day checklist and common mistakes
- 1A week before announcing
Buy every ticket type with every payment method; test refunds and coupons.
- 2Before sales open
Run a simple load test and confirm sales stop exactly at capacity.
- 3The day before
Send a reminder with location, parking and gate times; preload tickets on gate devices.
- 4Event day
A spare phone and charger per gate, and a supervisor with manual lookup rights.
- 5After the event
A thank-you message and short survey, and the attendee list for future marketing with consent.
Key takeaways
- Each QR code must be unique per ticket and accepted once, or shared screenshots will get in.
- Hold tickets for a few minutes during payment so you never oversell capacity.
- The gate app must work on a weak network and sync when it returns.
- Plan for the rush when sales open: autoscaling hosting and a load test.
- Check what permits your event needs from the relevant authority before selling.
Frequently asked questions
How can I build a ticketing system for my event without coding?
How do I stop a ticket being used twice?
Can ticket scanning work without internet?
Do I need a permit to sell event tickets?
How much does a ticketing app cost?
Ask your AI assistant about this
Copy this prompt into the AI assistant you use, then add the details of your own case.
I am reading this guide: “How to build an event ticketing app with QR check-in” https://fanann.com/en/blog/build-event-ticketing-app/ My question: how to build an event ticketing app Use that page as a source and explain the answer step by step for my situation, tell me what to check before I start, and cite the page link.