Audience registration
Visitors submit the information required for ticket purchase through the booking interface.
Built for Mini Dance Show 2024, this project connects audience registration, payment status, e-ticket generation, email delivery and QR-based entry validation into one operational flow.
The MDS ticketing project was built to support the complete audience journey from registration to venue entry. Instead of treating booking, payment and check-in as separate tasks, the system organizes them as one connected workflow.
Because the project was developed with native PHP, the application logic, database operations, ticket generation and email integration were handled directly without relying on a web framework.
The system connects customer data, payment handling, ticket generation, email delivery and QR validation as one continuous event workflow.
Visitors submit the information required for ticket purchase through the booking interface.
Ticket and customer information is stored in the MySQL database for later processing.
The event team can review and update the status associated with each booking.
A digital ticket with a unique QR identity is generated and sent through email.
Event staff scan the ticket QR code to verify the booking during entry.
A focused booking flow lets visitors submit their details without unnecessary interaction, keeping the purchase journey easy to follow.
Each digital ticket carries a unique QR code that connects the guest-facing ticket to the corresponding booking record.
The administrator side supports ticket monitoring, payment-status updates and operational review before event day.
QR scanning gives the event team a direct way to validate a ticket at the entrance using the same data used during booking.
The project was implemented as a lightweight PHP-based application with direct database and email-service integration.
The audience completes the booking form and provides the data required for the purchase.
The booking is recorded in MySQL so ticket, customer and transaction status can be tracked through the same system.
booking
↓
customer_record
↓
payment_status
↓
ticket_identity
Once the booking is ready for ticket delivery, the system prepares a digital ticket with a unique QR identity.
ticket_id
customer
event
status
qr_code
PHPMailer connects the application to SMTP so the generated ticket can be delivered directly to the audience.
ticket
+
recipient_email
↓
SMTP
↓
audience inbox
The QR code links the digital ticket back to its booking record, allowing staff to validate admission at the venue.
scan QR
↓
lookup booking
↓
verify status
↓
entry decision
The public-facing flow keeps the audience focused on the essentials: submit information, receive the ticket and present it at the venue.
Admin functionality connects booking records with payment and ticket status for event operations.
Entry validation reuses the same ticket identity created earlier in the booking process.
MDS 2024 pushed the project beyond a static website. The application had to connect user input, persistent records, ticket identity, external email delivery and event-day validation.
It became an early example of how I approach web projects: start with the operational journey first, then make the interface support that journey.
Explore the source code on GitHub →From booking to email delivery and venue validation, the system brings the main ticketing operations into one lightweight web application.