Advanced Online Ticket Booking System

Overview

I built this ticketing stack for ELEGANZA, a live student batch party — not a classroom checkout. Buyers register on a countdown landing page. Organisers review bank-receipt payments and approve or reject. Door staff scan a QR. Physical tickets print for people who still need paper. Confirmed guests get a personalised e-ticket on WhatsApp.

Tickets closed 26 March 2024. Source: batchPartyticket_FullStack.

Problem

Campus events that sell through spreadsheets and cash at the door lose seats, lose money, and stall the queue while someone squints at a screenshot. ELEGANZA needed a path from public buy → human payment review → a scan that either lets you in or does not.

What I built

Public registration books against event inventory. Payment at the time of the event was bank-slip upload, with a review queue for admins and a manager approve/reject step — we did not pretend a card gateway was live when it was not.

After approval, the system issues an e-ticket with a dynamic QR and sends it to the buyer’s WhatsApp number. Entrance uses a Vue-powered scanner so check-in is a scan, not an argument. Staff can print physical tickets. An organiser dashboard tracks ticket counts, attendees, and event timing. Persistence is MySQL for events, tickets, and orders.

Impact

The system ran for a named live event. That end-to-end path (buy, review, scan) is the artefact. It was university team work with a public repo and write-up. I do not invent attendance totals here; the useful claim is that door and finance used the same ticket record.

Key features

• Public registration with a countdown landing page
• Bank-receipt payment review and manager approve / reject
• Personalised QR e-tickets delivered over WhatsApp
• Vue QR scanner at the door
• Physical ticket printing for staff
• Organiser dashboard for counts and timing
• Inventory-aware booking in MySQL

Technologies

PHP, HTML, CSS, JavaScript, Vue.js, Bootstrap, and MySQL. Real-time-style updates on the door side sit on that stack rather than a separate product.

My role

Full-stack contributor on the university project team — booking UX, server logic, QR/check-in, and the public write-up as shared ownership.