Kapta · 15/09/2026
Usage control should be shared across entrance points. For single-use tickets, the admission decision and usage record need to work together, including when two people present the same code almost simultaneously.
Can a screenshot work like the original ticket?
A screenshot can carry the same code as the original ticket. Protection should therefore not depend on how the ticket looks. Validation should check the linked entitlement and remaining uses; identity checks, where required, need their own procedure.
What happens if two gates scan the code at once?
Request a concurrency test: simultaneous scans of a single-use ticket should produce only one authorisation. Updating independent counters and synchronising later can leave room for duplicate authorisations. This behaviour should be part of the acceptance criteria.
What if admission is authorised but the visitor cannot pass?
Distinguish a scan attempt, an authorisation and a confirmed passage. Define when a use is consumed and how staff resolve a mechanical failure or abandoned entry. Where there is no passage sensor, the report should explain what was actually measured.
How should a legitimate second scan be handled?
Provide a message that helps staff distinguish an already used ticket, a repeated attempt and a re-entry entitlement. Manual corrections should identify the operator and reason. When discussing the project with Kapta, include the number of entrances and the required behaviour if communication between them fails.
