Skip to main content
Every checkout on the hosted checkout page goes through an order — including free tickets, which settle as an order of 0. Tickets, add-ons, and bundles follow the same path: the buyer places an order, confirms it, pays if there is anything to pay, and settlement creates their registration(s). Orders are listed on the Orders page in the event navigation.
The Orders page is for viewing and tracking. Buyers create and confirm orders themselves on the hosted checkout. From the console you can cancel a pending order and, on a paid one, issue a refund.

​
Order status

1

Placed — Awaiting confirmation

The visitor picks their items and submits. The order holds its places for 15 minutes: while it is pending, those seats count against the ticket type’s capacity so nobody else can take them.
2

Confirmed — Completed

The buyer confirms. A free order settles at confirmation with an amount of 0. A paid order moves to Awaiting payment, holds its places longer, and settles when the payment page reports success. Fulfilment turns the settled order into its registration(s), and the attendee appears in the attendee list.
3

Or: Expired / Cancelled

An order not confirmed within 15 minutes expires and releases its held places automatically. The buyer — or the console — can also cancel a pending order, which releases the hold immediately.

​
The order number

Every order has an order number — the handle a buyer quotes, and the one your site receives when they return from checkout. The console shows it in the Order column so a buyer’s question can be matched to their order. The order’s detail page also shows the Hosted order page address, which opens only for the buyer’s email.

​
What the page shows

Each row lists the order number, buyer, items, total (Free for a 0-amount order), expiry for pending orders, and when it was placed, with its status: Awaiting confirmation, Awaiting payment, Completed, Expired, Cancelled, or Refunded. From a completed order, jump to the resulting attendee.

​
Rules to know

  • Even free events run on orders. Confirming on the hosted checkout places a 0-amount order and settles it — so the Orders page is a complete record of public registrations. Registrations added on the Attendees page skip orders entirely.
  • A pending order holds capacity. If a ticket looks sold out but the attendee count says otherwise, unexpired pending orders are likely holding places — they release within 15 minutes.
  • Repeat submissions never double-book. Someone already registered who checks out again is acknowledged as already registered — no second seat, no error message. This holds even if they used a since-spent code or the ticket has since closed.
  • Expiry is automatic and exact — 15 minutes from placement, no action required.
  • Paid orders require payments to be connected for the Business Unit. Without that, a paid order cannot be placed; the free path keeps working.

Ticket types

Capacity that pending orders hold against.

Attendees

Where a completed order’s registrations land.

Bundles

One order can include a bundle.

Refund policies

The promise attached to what an order bought.