Booking and payments
How free, paid and pay-at-venue bookings behave, how holds prevent overselling, and what each order state means.
What a buyer does
The buyer opens the public event page, chooses an occurrence and ticket quantities, and enters the details the event requires. Boni places a hold on the inventory, creates a pending order, and then follows one of three payment paths.
| Event type | What happens |
|---|---|
| Free | The order confirms immediately and tickets are issued at once |
| Paid | The buyer is sent to a Boni-hosted payment page; tickets are issued only after payment is confirmed |
| Pay at venue | Where enabled for the organizer, the order confirms with payment due at the door, and staff can mark it paid later |
No ticket exists before its order is confirmed. A paid order that is abandoned never produces a ticket.
Holds stop overselling
A hold reserves the requested quantity while the buyer completes checkout, and it expires on its own. Expired holds are released before the next availability check, so an abandoned checkout returns its seats to the pool without anyone intervening.
Repeated submissions of the same booking are de-duplicated, so a double-tap or a retried request produces one order, not two.
The order access link
Every confirmed order gets a signed private link showing order state and one QR code per ticket. The link is the attendee's ticket wallet: it is not indexed, it is scoped to that order, and it is safe to forward to the people attending on that booking.
The same link is sent by the confirmation email, which arrives from Bino Orders as soon as a free or paid order is confirmed. If a buyer loses the email, an organizer can resend the confirmation from the panel.
Order states
| State | Meaning |
|---|---|
| Pending | Created, awaiting payment; inventory is held, not sold |
| Confirmed | Tickets issued and valid for entry |
| Cancelled | Cancelled by the organizer or after payment failure; tickets are void |
| Expired | The hold lapsed before payment completed; inventory returned to the pool |
Cancelling an order voids its tickets, and a voided ticket is rejected at the gate rather than silently accepted.
Integrations
Per-organizer API keys and signed outbound webhooks for order confirmation, order cancellation and ticket claim are available as part of onboarding, so an organizer's own systems can react to ticketing events.
Next: Gate entry.