Inventory begins with the Event
Organizers define ticket tiers and the inventory available to the public Event. That inventory belongs to the same operational context as timing, location and capacity; it is not a separate product catalog with a name that merely resembles the Event. Publishing controls decide when a public sale is ready, while the retained tier structure gives the later reservation and admission workflows a stable source.
This connection matters before the first payment. A tier can describe its price and available quantity, and the public surface can present only what the organizer has made sale-ready. The system does not need to infer supply from successful charges after the fact. Capacity is established first, then each reservation competes against the same inventory rather than a page-local counter.
Reservation and payment form one transaction
A buyer selects admission through the public Event or Venue surface and receives a reservation context that carries the chosen items into payment. Checkout completion is bound to the reservation rather than treated as an isolated payment notification. That lets NOCTRA distinguish a paid admission from an abandoned or expired attempt and keeps the buyer-facing state aligned with the underlying Event inventory.
The payment boundary records the commercial evidence required by the implemented transaction flow. Seller profile, tax context, applicable disclosures and the accepted transaction terms can be attached to the formation of the sale. This is not a promise that NOCTRA replaces every external accounting or legal process. It is a durable record of the checkout that the native system actually formed and operated.
Delivery continues into access
Successful reservations produce ticket access that can be delivered to the buyer and resolved at the Event. The ticket is not reduced to an email attachment: it remains connected to the reservation, its current holder and the Event against which it will be validated. NOCTRA Door can then interpret the QR result inside the correct live context while manual guest and ticket search remains available when scanning is not the right path.
Secure transfer allows a valid holder to pass admission through a controlled token flow instead of sharing an untraceable image. The receiving state can be resolved without breaking the ticket's relationship to its origin. That continuity matters at the entrance, where staff need a current answer rather than a history of screenshots, forwarded messages and private explanations.
Refunds do not erase the sale
A refund changes the commercial outcome, but it does not make the original transaction disappear. NOCTRA retains successful refund evidence and can issue the corresponding correction records for the native flow. Buyer and Workspace reporting surfaces can therefore distinguish the original sale from what happened afterward instead of replacing one amount until the history becomes impossible to follow.
That evidence also improves post-Event Commercial Actuals. Native ticket revenue can be calculated from successful paid reservations and reduced by successful refunds, producing a read-only contribution grounded in activity NOCTRA handled. The system does not extend that calculation to external providers or claim that native ticket revenue represents every source of Event income.
Native Ticketing is available from Free
Every NOCTRA plan can use Native Ticketing, including Free. Pricing V3 changes capacity, reporting and the ticketing rate as an operation grows, but it does not reserve the core native path for a paid software tier. An organizer can begin with an Event, publish its admission and operate the Door without first adopting an external sales stack or a hollow trial plan.
External Ticketing remains a separate choice from Core onward because it describes an independently operated sales model. No paid tickets remains equally precise: the Event sells no paid tickets. Keeping these modes distinct gives each Event a truthful admission premise while Native Ticketing provides the connected path from published inventory to the final scan.
The connected record also makes support and handover more concrete. Organizers, payment operations and Door teams can refer to the same reservation and ticket state without treating an email, a processor reference or a scanned code as separate versions of the truth.