Per-ticket fees are not a flat charge. They are a percentage of your revenue that grows with every ticket you sell, and the headline fee you see on the pricing page is only part of what you actually pay. On a typical platform charging a fixed amount plus a percentage per ticket, a single event selling 10,000 tickets at $30 can hand over more than $30,000 in fees before you count payment processing, payout holds, paid add-on modules, or refund charges. This article works through the arithmetic and the less obvious costs that sit around it, then explains the cases where a per-ticket platform is still the right choice.
The visible per-ticket fee, and how it compounds at volume
The first cost is the one quoted on the box. Per-ticket pricing is usually expressed as a fixed fee plus a percentage of the ticket price. For the worked examples below we use an illustrative structure of $1.79 per ticket plus 3.7% of the ticket price, applied to a $30 ticket. These numbers are representative of common public pricing, not a quote from any one provider, and your real rate will vary. The point is the shape of the curve, not the exact figures.
The fee per ticket is fixed: $1.79 plus 3.7% of $30, which is $1.11, for a total of $2.90 per ticket. That sounds small. The problem is that it never stops scaling. Sell twice as many tickets and you pay twice as much. Below is what that single per-ticket fee costs across four event sizes, and what you keep from gross sales.
| Tickets sold | Gross sales (at $30) | Fee per ticket | Total per-ticket fees | What you keep | Effective rate |
|---|---|---|---|---|---|
| 500 | $15,000 | $2.90 | $1,450 | $13,550 | 9.7% |
| 1,000 | $30,000 | $2.90 | $2,900 | $27,100 | 9.7% |
| 5,000 | $150,000 | $2.90 | $14,500 | $135,500 | 9.7% |
| 10,000 | $300,000 | $2.90 | $29,000 | $271,000 | 9.7% |
The arithmetic is straightforward. Each row is tickets multiplied by $2.90. The effective rate stays at roughly 9.7% of gross sales no matter how big the event gets, because the fee is a percentage by design. At 10,000 tickets you have paid $29,000 for what is, mechanically, the same checkout flow that processed your first ticket. A flat-fee platform such as eventcloud charges the same $125 per user per month whether you sell 500 tickets or 50,000, so the line on this chart would be flat rather than climbing. You can see the published rate on the pricing page.
Payment processing on top
The per-ticket fee is frequently quoted separately from card processing. Read the small print and you often find the per-ticket fee is the platform's cut, and the card fee (commonly around 2.9% plus $0.30 per transaction) is added on top. On the $30 ticket that is another $1.17 per ticket, or $11,700 across 10,000 tickets, pushing the all-in cost on that event past $40,000.
This matters for comparison because some platforms bundle a low-looking per-ticket fee precisely because processing is billed elsewhere. With a flat-fee model the only payment cost is standard card processing, paid directly to Stripe rather than to the platform, with no platform margin layered on top. The card fee exists either way. The difference is whether a second fee rides alongside it.
Payout holds and the cost of waiting
A cost that never appears as a line item is the payout hold. Many ticketing marketplaces hold your funds until after the event has happened, sometimes days afterward, as protection against refunds and chargebacks. For a one-off concert that might be tolerable. For an organiser running on tight margins it is a genuine cash-flow problem: you have bills to pay before the doors open, and your ticket revenue is sitting in someone else's account.
The cost here is real even if it is hard to see. If you sell $150,000 of tickets two months before an event and cannot touch the money until afterwards, you are effectively giving the platform an interest-free loan of your own revenue, and you may be financing supplier deposits and venue payments from elsewhere. Direct Stripe payouts on the normal schedule, with no post-event hold, remove that gap entirely, because the money lands in your bank on the standard rolling basis as sales come in.
Add-on modules: badge printing, hardware and white-label tiers
The sticker fee rarely covers everything you need on the day. Common paid extras include:
- Badge printing billed per badge or as a separate module subscription.
- On-site hardware rental: scanners, kiosks and printers charged per unit per day, which adds up fast across a multi-day event with several entrances.
- White-label or branding removal locked behind a higher tier, so your own event page carries someone else's logo unless you pay to remove it.
- Premium support or account management reserved for enterprise plans.
Each of these is reasonable on its own. Stacked together on a large event they can rival the per-ticket fees. With eventcloud, badge printing and QR check-in on any phone are included, so there is no hardware rental line and no paid check-in module. Staff scan with the phones they already carry, which also removes the logistics of shipping and returning rented kit.
Fees on refunds, and the cost of "free" tiers
Two quieter costs sit at the edges of the fee schedule.
Refund fees
When a ticket is refunded, some platforms keep their per-ticket fee anyway, and the card processor may not return its cut either. So a cancelled $30 ticket can leave you out of pocket on fees for revenue you never kept. For events with normal cancellation rates this is a steady, invisible drain.
The "free" tier that the attendee pays for
Many platforms advertise free organiser plans where the fee is absorbed by the attendee at checkout instead. That is not free, it just moves the cost. The buyer sees a $30 ticket become $33 or $34 at the final step, and that price jump at checkout is a well-known driver of cart abandonment. The cost lands on your conversion rate rather than your invoice, which makes it easy to miss and expensive to ignore. A flat monthly fee means the price the buyer sees can be the price they pay, with no surprise add-on at the last screen.
The opportunity cost: what that money could have funded
The final cost is what the fees are not doing for you. Take the 10,000-ticket example: roughly $29,000 in per-ticket fees, before processing. Set against eventcloud at $125 per user per month, even a small team running events year-round pays a few thousand pounds annually rather than tens of thousands per large event. The difference is not abstract. On a single big event it is the budget for a headline act, a second stage, better marketing spend, or simply margin kept in the business. Run several events a year and the gap compounds into real money that could fund growth instead of fees. Festival organisers in particular feel this at scale, which is why we wrote separately about ticketing for festivals.
When per-ticket still wins
Per-ticket pricing is not a trap, and for some organisers it is genuinely the better deal. If you run small or infrequent events, a per-ticket fee can be cheaper than any monthly subscription, because you only pay when you sell and the totals stay low. For free events, many platforms charge nothing at all, which is hard to beat. And for discovery, large marketplaces put your event in front of an existing audience that is already browsing for things to do, which has real value if you have no list of your own yet.
The honest summary is a break-even calculation. Below a certain volume, per-ticket wins. Above it, a flat fee wins, and the cross-over comes sooner once you add processing, holds and paid modules into the comparison. If you are weighing a specific platform, our comparison with Eventbrite walks through the same maths against a named provider. Work out your own numbers at your real ticket price and volume, and the right answer becomes obvious.
Frequently asked questions
What is a per-ticket fee?
A per-ticket fee is a charge a ticketing platform takes on every ticket sold, usually a fixed amount plus a percentage of the ticket price. Because part of it is a percentage, the fee scales with your revenue, so larger events pay proportionally more even though the checkout process is the same.
Are per-ticket fees separate from payment processing?
Often, yes. Many platforms quote the per-ticket fee separately from card processing, which is commonly around 2.9% plus a small fixed amount per transaction. The card fee is then added on top of the platform fee, so the all-in cost is higher than the headline figure suggests.
What is a payout hold and why does it cost me?
A payout hold is when a platform keeps your ticket revenue until after the event has taken place, as protection against refunds and chargebacks. It costs you because you cannot use your own revenue to pay suppliers, venues or staff before the event, creating a cash-flow gap you may have to finance elsewhere.
Is a free organiser plan actually free?
Usually the cost is moved rather than removed. On many free plans the fee is absorbed by the attendee at checkout, so a $30 ticket becomes $33 or $34 at the final step. That price increase at checkout can reduce conversion, so the cost lands on your sales rather than your invoice.
How does a flat-fee platform like eventcloud compare?
eventcloud charges a flat $125 per user per month with no per-ticket, booking or transaction fees. Only standard card processing applies, paid directly to Stripe rather than to eventcloud, and payouts arrive on Stripe's normal schedule with no post-event hold. Badge printing and QR check-in on any phone are included, with unlimited events and tickets.
