We had four days to prepare a simple ticketing system for a cultural institution. The application covers the journey from concert information and the purchase form to payment processing, ticket codes and the organiser’s panel.

A defined scope for one event

The organiser needed a dedicated sales page where buyers could purchase without creating an account. The application supports one ticket type, a defined capacity and a per-order quantity limit. Event information and collection instructions sit alongside the purchase form.

We built the custom application with Laravel and a Filament administration panel.

From an order form to individual codes

A buyer selects the quantity, enters contact details and proceeds to Przelewy24. After payment verification, the application generates an individual code for each ticket and prepares an email with the codes and collection instructions. The organiser can also access the codes in the panel.

The integration validates the provider notification, amount and currency. A repeated notification for the same paid transaction does not create another set of tickets. An email sending error does not reverse the recorded payment.

Capacity and the payment window

At order creation, the application checks available capacity and temporarily reserves places for payment. Abandoned orders stop holding capacity after the reservation window expires. The organiser can change the per-order limit and enable or disable sales.

The event operating procedure also needs to account for delayed payment confirmations, particularly when few tickets remain.

A panel for everyday administration

The Filament panel lets the organiser search orders, filter them by payment status and view ticket codes. Settings cover the event name, date, venue, description, images, terms, price, allocation and collection instructions.

The application can be prepared for another event after retaining the necessary records from the previous edition. Preparing the next edition requires a technical reset, described in the handover documentation.

The delivered application

The implementation scope includes the event page, order form, Przelewy24 integration, individual codes and administration panel. The frontend uses Blade and Tailwind; the application uses MySQL/MariaDB. Documentation covers configuration, deployment and preparation for another event.

Software for your own workflow

We build custom Laravel applications around specific operating needs. Tell us about your event or workflow so we can establish the scope, delivery window and maintenance plan.

Laravel, MySQL, PHP, Tailwind
Back