Kapta · 15/09/2026
Authorisation should reflect the booking's current entitlement, including its date, time and status. The project needs to define how changes reach the entrance and what happens when the available information is no longer recent.
Can a ticket for today enter at any time?
That depends on the attraction's commercial rules. Define whether admission uses a fixed session, an early or late arrival allowance, or all-day validity. Keep admission rules separate from session capacity so an entry exception does not silently change bookable availability.
Does the QR code change when a booking is rescheduled?
Confirm this behaviour in the configuration being used. The integration should not assume that every change produces a different code. The essential requirement is to link the presented code to the current booking and apply its updated validity, even when the visitor shows an older email.
How should a cancelled booking be blocked?
Define the source of booking status, how updates arrive and the maximum acceptable delay at readers. Test a cancellation after ticket issuance but before arrival at the gate. If information is stale, the procedure should explain how staff verify the case.
What matters for entrance times in Hungary?
Configure rules using the attraction's time zone, such as Europe/Budapest, and test date and clock changes. A time shown on a phone configured for another country should not redefine the purchased session. Include near-midnight opening scenarios in the assessment with Kapta.
