How do I publish an event and sell tickets?

Publish your event, share its link, and understand where the money goes — including the booking fee and who pays it.

Publish the event, then share its public link — guests buy tickets online and the money goes straight to your Stripe account. Events are available on Pro plan and above, and with the Events product (free to start with one published event per calendar month; £25/month for up to 500 events a month).

Setting up tickets

While tickets' set-up steps are unfinished, the Events page shows a Set up tickets card at the top — the same steps as Your set-up (create and publish your first event, meet the Scanner and share your What’s on page; on a products-only account, your venue details and policies too — free events never need Stripe), with a tick on each one done, and the Your What’s on page card under it. Each Start or Open button takes you to that step on Your set-up, and the card goes away by itself once every step is done or marked Not for us. For your first sales: share your What’s on link where guests see it, and show your door staff the Scanner.

Publishing

Pausing sales without cancelling

Sold as many as the room takes, the chef is off, the weather has turned? You don't have to cancel the event. Open the event's own page from the Events page and choose Stop new sales from the … menu at the top. It asks first — Stop new sales? "Nobody can buy a ticket until you put it back on sale. Every ticket already sold still works." — and once you confirm, the event comes off sale straight away: its public page tells guests "This event is not currently available for booking." and its status pill reads Off sale (Draft if no tickets had been sold yet), while every ticket already sold stays completely valid (same QR code, same ticket page, same door scan). Nothing is refunded and nobody is emailed; only new sales stop. When you're ready, the same menu offers Put back on sale (it asks first too) and the event shows Published again (Today on the day itself); on a draft that has never been on sale, the same menu says Publish instead (Publish this event? — it goes on your What’s on page) — no password prompt either way, and both are recorded in your Activity log. It's also the way out when a paid event's publish tick-box in the builder is locked because Stripe has disconnected: stop new sales from the event page instead. Cancelling is the separate, bigger step — Cancel event refunds and emails every ticket holder (see What are the event defaults (refunds, cancellation, check-in)?).

What guests do

On the event page they go through three short steps — Tickets (a tier, how many and any add-ons), Your details, then Check and pay, which shows the price breakdown line by line — and pay by card, Apple Pay or Google Pay (a free event has just the first two steps). If you run promotions, a Have a code? row on the Check and pay step applies ticket discounts before payment — see How do promo codes work on event tickets?. Ticket issue is safe against glitches: if the buyer's browser closes mid-payment, a paid ticket is still issued automatically — and if the tickets sold out in the meantime, the payment is automatically refunded. Each buyer gets a ticket email with their QR code.

The money and the booking fee

Ticket money is paid directly to your connected Stripe account, minus Stripe's processing fee and any ResoFlow platform booking fee — check the live rates in the Fee calculator on Settings → Payments and deposits → Payouts and Stripe. Free tickets never carry a fee.

You choose who covers the booking fee in Settings → Events (the gear at the top right of the Events page opens it), under Booking fee:

Selling at the door

Walk-up guests are covered three ways from the Scanner (all detailed in How do I check tickets at the door?):

Chasing unfinished checkouts

An abandoned-checkout recovery email (someone who started paying but never finished) can be switched on in Settings → Communications → Guest notifications — see Which emails do event guests get?

Related: How do I create an event? · What are the event defaults (refunds, cancellation, check-in)? · What does the ticket buyer see? · Which emails do event guests get?