Selling Tickets

How ticket selling fits together in the Sway web app: what must exist before the first sale, the order to set it up in, and the six screens involved.

Sway Tickets is Sway's own ticketing. Buyers check out on the event's Sway page, pay the promoter's Stripe account, and receive a scannable ticket by email. Six screens in the event sidebar cover the whole job, and this page is the map to them.

Two things have to be true before any of those screens can take a single euro, and neither of them lives in this group.


What has to exist first

A promoter page with a working payout account. Sway does not hold your money. Every payment goes to a Stripe account connected to the promoter page, not to the event and not to your user account. One promoter, one account, shared by every event that promoter organises. The indicator that matters is Charges enabled: until it reports yes, checkout fails at the payment step, however finished the rest of your ticketing looks. Full procedure in Connect Payouts.

Sway Tickets turned on for the event. The switch sits on the Main tab of the event's settings and decides whether the event sells through Sway or points at ticketing of your own. With it off, most of the screens below are replaced by a line telling you to enable it. See Event settings.

The two are independent, and only one of them is visible on the event. An event can carry Sway Tickets, a complete price list and a published page while the promoter behind it has no usable Stripe account. Nothing in the event stops you, and the buyer gets no warning either: the failure lands on their card, at the moment they pay. Confirm Charges enabled before you announce a sale date.

Set it up in this order

  1. Connect Stripe on the promoter page. Open the promoter, go to SettingsPayouts, and finish Stripe's form. Then wait until Charges enabled reports yes. Stripe decides when that happens, and Sway only reports it.
  2. Turn on Sway Tickets on the event. Open the event, go to SettingsMain, switch Sway Tickets on, and click Save changes.
  3. Choose who gets paid. The event's Payouts tab appears once step 2 is saved. Find the promoter in the table and click Link this promoter. Exactly one promoter per event receives the money.
  4. Create at least one ticket type. Nothing can be bought until one exists. See Ticket Types.
  5. Add what the campaign needs, in any order: Coupons for discount codes, and Presales for a registration campaign. A presale unlocks a Hidden/Private ticket type, so it can only be built after step 4.
  6. Issue comps to guests, artists and press on the Guestlist.
  7. Create your scanners before doors open, one per door or per shift. See Scanners.
  8. Follow the sales on Orders, which is also where a refund is issued.

Steps 1 to 4 are the minimum for an event that sells. Steps 5 to 7 are optional and can be done while sales are running. Making the event public is a separate decision with its own requirements, covered in Publish an Event.

The Payouts tab on an event joins the tab bar only once Sway Tickets has been switched on and saved. Flipping the switch is not enough on its own: save the Main tab, and the tab appears.
Several things freeze the moment an event sells its first ticket: the start and end dates, the Sway Tickets switch itself, the linked payout promoter, and deleting the event. Settle all four before you open sales rather than after.

What still works without Sway Tickets

Turning the switch off does not empty the sidebar. It changes what each screen does.

ScreenWith the switch off
TicketsReplaced by a line saying Sway Tickets is not enabled, pointing at Settings
CouponsReplaced by Sway Tickets is not enabled and a button to the event settings
PresalesSame, and a presale needs a hidden ticket type on top of that
ScannersReplaced by a warning that scanners will not be able to validate tickets
GuestlistWorks, as a plain door list: names, check-in and exports, but no order, no QR code and no email
OrdersOpens normally. This row is not tied to the switch

Who can open each screen

Each of the six is gated by its own permission, granted per event. A screen you have no permission for is greyed out in the sidebar rather than hidden, so the menu looks the same to everybody and the reason is in the tooltip. Viewing and editing are usually two separate permissions: read access opens a screen with its buttons dimmed. See Manage Permissions.


The six screens

Ticket Types

Price, capacity, bundles and sale windows. Start here, nothing sells without one.

Coupons

Discount codes, with expiry dates and usage limits.

Presales

Collect registrations, then email each fan a unique code for a hidden ticket.

Guestlist

Free comp tickets, or a plain door list on an event that does not sell.

Orders

Every purchase on the event, its tickets, and where a refund is issued.

Scanners

One credential per door, handed out with a one-shot pairing link.