← Integrations · Event ticketing
Sell tickets on your own site. No Eventbrite cut.
We connect a ticketing system to your website, or help you choose one: pick the event, pick the ticket, pay, and a QR ticket goes to the attendee's phone. Instead of handing Eventbrite, Universe or DICE a fee on every ticket AND your attendee list, you sell on your own site and the attendees stay yours.
The maths
What Eventbrite, Universe and DICE actually charge.
Event ticketing platforms publish "free for organisers" but make money on per-ticket booking fees, either charged to the attendee (most common) or paid by the organiser, and they own the attendee list, so the people who came to your event are theirs to market to. Either way, the money comes off the same pot, plus a Stripe-style payment fee on top. The result for a typical UK event:
| Platform | Per ticket fee | Who owns the attendees | On a £25 ticket × 200 sold |
|---|---|---|---|
| Eventbrite (UK) | 3.7% + £1.79 | Eventbrite | £549 in fees |
| Universe (Ticketmaster) | 3% + £0.99 | Universe | £359 in fees |
| DICE | ~7% (Org's pay-the-fee model) | DICE | £350 in fees |
On your own site you pay what your ticketing system charges, which you can see before you sign. Set that against the £350 to £550 those platforms take on a single 200-ticket event, then add what you keep: the attendee data (Eventbrite does not make it easy to take with you), and the search value of selling on your own pages rather than sending people to a "Buy on Eventbrite" link.
The checklist
What to look for in a ticketing system.
Whether you already have one or you are choosing, these are the points we check a ticketing system against.
- Ticket types and tiers, general admission, early bird, VIP, tables, group discounts and complimentary tickets, each with its own cap.
- Capacity and waitlists, when an event sells out, a waitlist, with any released ticket offered to the next person.
- QR tickets and wallet passes, a ticket the attendee can keep in Apple Wallet or Google Wallet instead of hunting for an email.
- Door scanning that works offline, a staff app that scans tickets and keeps working when the venue signal drops.
- Refunds you control, your refund policy shown at the point of sale, and each refund approved by you.
- Transfer and resale rules, tickets tied to the buyer by default, with transfers or resale at face value only if you want them.
- Promo codes and recurring events, discount codes for partners and social pushes, and a template for weekly or monthly events.
- Door sales, walk-in sales on the night, in the same system and the same scan-in flow.
- Payments to your own account, and an export, you are the merchant, and the attendee list comes out as a CSV any time.
How it joins your site
An embedded checkout, real event pages, or a straight link.
An embedded checkout. Many ticketing systems provide a checkout you can embed, often as an iframe, a sandboxed window inside your page. We place it on each event page, so the attendee picks and pays without leaving your site, while the checkout and the door scanning stay the system's own, well-tested parts.
Event pages your site builds. Where the system has an API, your site can show each event as a real page with full structured data, so it can be found on Google, with the checkout opening from there.
A straight link. Your Buy tickets buttons open the system's own event page. The simplest route; the trade-off is that the attendee leaves your site to buy.
New to these terms? See the glossary.
How it goes
From "I want this" to "first ticket sold".
- Email us with the event details, or run a free audit at /audit. Tell us what you use for tickets now, if anything.
- If you have a system, we check what it supports. If you need one, we compare a short list against the checklist above, and you choose.
- Your first event goes into the system: date, venue, tiers and capacity, with payments connected to your own bank account.
- We connect it to your site: an event page with the checkout embedded or linked, and Buy tickets buttons where they belong.
- A test sale, a test scan and a test refund. Then tickets go on sale, and you tell your list.
For an event series, the second event is quicker, because the venue, capacity and tiers are already set up.
Common questions
What event organisers ask before moving ticketing to their own site.
How does this compare to Eventbrite's "free event" tier?
Eventbrite's free tier is for genuinely free events only, the second you charge anything, the booking fee kicks in. If your tickets are free and you just need RSVP tracking, Eventbrite's free tier may be all you need. The moment money changes hands, a ticketing system on your own site is worth comparing.
Will Eventbrite let me export my existing attendee list?
Yes, event by event: you can export the attendee list for each event, so plan to do it one event at a time during your switch. We help you bring the lists into the system you choose.
Can I move ticket sales for an event already on sale?
Technically yes: set the event up in the new system, point the Buy tickets button on your site at it, and look after anyone who already bought on Eventbrite there. In practice it is usually easier to finish an event that is already on sale where it is, and switch for the next one. We will advise on the specific event.
How does refunding work?
Choose a system where you set the refund policy, it is shown to the buyer at the point of sale, and you approve or decline each request. The refund then goes back to the original card through the system's payment provider, on that provider's normal timing.
What about touts and scalping?
Look for tickets tied to the buyer by default, with transfers off unless you switch them on. For high-demand events, some systems offer resale at the original price, so a returned ticket goes back on sale through you rather than through a resale site.
What if there is bad signal at the venue?
Make offline scanning a requirement. A good door app caches the tickets when the doors open, logs each scan on the device, and syncs when the signal returns, so the queue keeps moving.
Do you take a cut of my ticket sales?
No. We charge for building and looking after your website, quoted to your business. What the ticketing system costs is between you and its supplier, which is why pricing is on the checklist.
Get this on your site
Your site, your system, your customer.
It starts with a free audit. Tell us which ticketing system you use now, or that you need one, and we will scope connecting it into the quote for your build and website management.