Keep £24.80 of every £25 ticket.
Sell tickets to meetups, conferences, workshops and nights out from a page in your event’s colours. Guests pay the price on the page and nothing more. You pay the card rate on what they pay, and free events are free.
- Ticket and booking fees
- £0
- Themes, free for every event
- 12
- Check-in at the door
- Offline
- Paid out after each date
- Next working day
The price on the page is the price they pay.
No booking fee added at checkout, and no fee per ticket taken from you. Ticket payments are card payments, at the same rate as every other payment on your account.
- Page, checkout, email and receipt always show the same total, as UK and US law on all-in prices asks.
- Free tickets and RSVPs are free, with every feature.
- Themes, your own domain, check-in and the widget are included for everyone.
- Want the card fee covered? Set the ticket price to cover it. We never add it on top.
Against the platform you use now.
Type your ticket price and how many you sell. Every figure is our fee engine’s arithmetic, and each platform’s fees are as it publishes them. See the full comparison.
You keep on Tuppence
–
On the other platform
More for you on Tuppence
Every ticket paid by a UK consumer card, with every fee absorbed by you. Other platforms’ fees as they publish them; see the comparison.
Drop in a cover. The page follows.
Each theme takes its colours from your cover, sets a title font and a background, and checks every colour so the text always reads. Pick one, or try them here.
Text contrast 17.8:1 · passes WCAG 2.1 AA
- Your brand first: “Tickets by Tuppence” is small, and you can hide it.
- On your own domain, or on your website with one line of code.
- Link previews, the ticket email and the ticket page wear the same look.
Check-in that keeps going when the signal doesn’t.
Scan in the Tuppence app or the till. Codes are checked on the phone, so the queue keeps moving offline, and every scan is sent when the signal returns.
- The first scan wins, whichever phone made it. A second scan says when and where the guest came in.
- A door staff login that only checks people in, several gates, and live counts by gate and ticket type.
- Find a guest by name when they have no phone, and see what to hand over: a drink token, a badge, a T-shirt.
- Keep seats back for the door and sell them from the till beside drinks and merch. The page never sells past what is left.
Sold out, then sold again, at face value.
When a ticket type sells out, guests join a waitlist. A seat that frees up, or a ticket a guest gives back, goes to the next in line at the price it was bought for, with no fee either side.
A code that can’t be screenshotted
A few hours before doors, a paid ticket’s QR code starts changing every few seconds, so a screenshot shared online won’t get in.
Transfers by name
A guest can pass their ticket to a friend by name and email. The old code stops working and the friend gets a new one.
Named tickets
Ask for a name on each ticket when you need one, shown at the door.
Every kind of ticket. Every way to fill the room.
Tickets and checkout
Every kind of ticket, and a checkout on one sheet.
Paid, free, pay what you want
Several ticket types, early-bird prices that end on a date or after a number sold, group discounts, bundles with merch, donations, and limits per order.
Codes and hidden tickets
Promo codes for money or a percentage off, and access codes that reveal hidden tickets for speakers, sponsors or crew.
Checkout on one sheet
Apple Pay and Google Pay first where the phone has them, then card. Ask buyers your own questions.
Tickets by email
In your event’s look, with a PDF, a ticket page and a calendar file. Reminders go out before the day by themselves.
Fill the room
Sell out, and bring people back.
Repeating events and passes
Weekly or monthly dates, passes for every day of a conference, events that need your approval, and memberships that include tickets.
Partner codes
Codes that earn a partner a commission on each ticket, paid once the event’s money is released.
Your organiser page
Every upcoming event in one place, with a calendar feed and a Follow button that emails followers when you publish.
Messages and ads
Emails to your guests, and your Meta, TikTok and Google Analytics tags, loaded only after the visitor agrees. Sales by source shows which links sold.
Paid out after the event.
Online ticket money is held until each date has happened, then paid out with the rest of your balance. If an event is cancelled, every guest gets their money back in full.
- Released the next working day after each date ends. Your first three events, or any in your first 90 days, wait five working days.
- A repeating event releases date by date. A multi-day pass is released after its last day.
- Refunds before then come out of the held money, so guests are paid back quickly.
- Tickets sold on the door through the till are paid out like any other till sale.
Tickets, the bar and the books together.
Events run on the same account as your payments, till, store and bookings. One balance, one payout, one set of reports.
Tickets in your reports
Ticket sales have their own line in your reports, and Sales by source shows which links and ads sold them.
A statement per event
What sold, what was refunded and when the money pays out, for each event, on screen or as a CSV.
In your books
Ticket sales post to your accounting software as their own line, with a Xero tracking category per event.
Guest lists
Attendees and orders in the dashboard, with refunds by order or ticket and a CSV export.
Every event is the API.
The dashboard, the app and the event page all run on the API you use. An agent can set up an event, add tickets and report on sales through the MCP server, and webhooks tell your systems when tickets sell, transfer or get scanned.
# Give your agent the events tools: claude mcp add tuppence \ --env TUPPENCE_API_KEY=rk_test_… -- npx -y @tuppence/mcp # Then ask it: > Set up our November hack night, 180 places, > early bird at 15 until Friday, then 25 ⏺ tuppence · create_ticketed_event ⏺ tuppence · create_ticket_type ⏺ tuppence · publish_ticketed_event Published: book.tuppence.ai/e/hack-night-nov
Endpoints
- POST /v1/ticketing
/events - POST /v1/ticket_types
- POST /v1/ticketing
/events /{id} /publish - GET /v1/ticket_orders
- POST /v1/ticket_orders
/{id} /refund - POST /v1/ticketing
/check_ins - GET /v1/ticketing
/events /{id} /settlement
MCP tools: create_ticketed_event, create_ticket_type, list_attendees, get_ticket_sales, refund_ticket_order, transfer_ticket and more. Read the docs.
The software is free.
We earn on card payments, so events carry no monthly fee, no ticket fee and no booking fee.
- Event pages, themes, check-in, the widget and your own domain
- Freefor every event, with nothing to upgrade to
- Ticket fee, booking fee, monthly fee
- Nonefor you or your guests
- Paid tickets
- from0.79%the card rate, nothing more
- Free tickets and RSVPs
- Freeno card, no charge
UK prices, excluding VAT. See pricing.
Before you sell your first ticket.
Do my guests pay a booking fee?
No. Guests pay the price on the page, and the page, checkout, email and receipt all show the same total. You pay no fee per ticket either. A paid ticket is an ordinary card payment at the card rate.
What do free events cost?
Nothing. Free tickets and RSVPs have every feature: themes, check-in, the waitlist and emails.
When do I get paid?
Online ticket money is held until each date has happened, then paid out the next working day with the rest of your balance. Your first three events, or any in your account’s first 90 days, wait five working days. Holding it means every guest can be refunded if an event is cancelled.
What happens if I cancel an event?
Every guest gets the full price back, from the money we’re still holding. The card fee on each refunded ticket isn’t returned, and comes from your other balance.
Does check-in work without signal?
Yes. The Tuppence app and the till check codes on the phone, so guests keep coming in offline. Scans are sent when the signal returns, and if two phones scan the same ticket, the first scan wins.
Can guests resell their tickets?
Only through your waitlist, at the price they paid, with no fee either side. They can also give a ticket to a friend by name and email. Either way the old code stops working.
Can I sell on my own website?
Yes. One line of code puts the tickets on your site, or serve the event page from your own domain. Both are free.
Are the pages accessible?
Every theme is checked so text meets WCAG 2.1 AA contrast, whatever your cover. At the door, a guest without a phone can be found by name.
- Apple Wallet and Google Wallet passes
- Texts and WhatsApp to guests
- Reserved seating
Until texts switch on, guests hear from you by email.
Payments that give more back.
Start in test mode in a minute. Go live once you’re verified.