Kapta · 15/09/2026
NTAK's attraction guidance distinguishes sales data from validation data. For covered operations electronically recording ticket usage, that record has reporting implications. Admission design should therefore preserve the link to the ticket. Official attraction guidance.
Is a QR scan the same as an entry?
Not necessarily. It may be a repeated attempt, an out-of-time ticket or a scan that did not allow passage. Define outcomes such as request received, entry authorised and usage recorded. If a passage sensor exists, explain how its information enters the workflow.
Which references should remain connected?
The ticket identifier, validation reference and time of use appear in the TSS specification. The integration should preserve their relationship with the original booking. TSS v1.04 validation specification.
How can sales and visits be tested separately?
Use a ticket sold yesterday and used today, an unused ticket and a rejected attempt. Operational reporting should explain differences between bookings, tickets sold and admissions. Do not count every scan as a distinct visitor.
What should I ask Kapta?
A mapping between the FareHarbor QR, admission entitlement and the record in the responsible ticketing system. Identify what readers and controllers can return so the workflow follows real installation data and applicable operational rules.
