When someone purchases tickets, an order is created containing one or more ticket items. Each ticket item is assigned to an attendee by first name, last name, and email address. Purchasers can use the
For me
option to assign a ticket to themselves, or enter different attendee details to buy on behalf of others.
Order Records
Order statuses
— Paid ticket orders move through three statuses:pending
while payment is processing,succeeded
once payment is confirmed, andrefunded
after a successful refund. Orders can also be canceled if checkout does not complete. An invoice number is automatically assigned when the order succeeds.Attendee records
— Event Settings includes attendee management and attendee export tools. Use those records for registration review, capacity planning, and event follow-up. Dedicated accounting exports for full paid order records are not part of the current Event Settings flow.Refunds
— Event managers can refund succeeded ticket orders from the attendee list in Event Settings. Open the relevant attendee record and use the Refund Order action. Guild issues the refund through the connected Stripe account, marks the order as refunded, removes the affected attendees from the Event, and emails the purchaser.Exporting attendee data
— Export attendee data from Event Settings for planning, registration review, and follow-up. This is attendee data, not a full accounting export of paid order records.Attendee Experience
For more on the attendee experience when purchasing tickets, see Attendee Purchase Flow.