Here is the honest answer most ticketing pages bury: event payment processing fees cost roughly 2.9% plus 30 cents per transaction, and that number is basically unavoidable no matter which platform you use. That is what it costs a bank and a card network to move money from an attendee's card into your account. It is a real, tangible service. The much larger figure on some of your invoices is something else entirely: a platform fee, stacked on top, that has nothing to do with processing the payment. Confusing the two is how organisers end up thinking a 12% total take is just "the cost of card payments". It is not.
So let us separate the floor you cannot escape from the ceiling somebody added on purpose, and show you how to read your true cost per ticket.
What payment processing actually costs
Payment processing is the plumbing. A processor like Stripe takes the card details, checks with the bank, handles fraud screening and settlement, and drops the money in your account. For that, Stripe's standard US rate is 2.9% plus 30 cents per successful card charge, with no setup fee and no monthly minimum. International cards add around 1.5%, currency conversion adds about 1%, and a disputed charge costs 15 dollars. Those are the honest, published costs of accepting a card.
Every platform pays some version of this. Square, PayPal and Adyen all sit in the same ballpark. Nobody has a secret deal that makes card processing free, because the card networks charge interchange to everyone. So when a platform tells you processing is "included", read it as "we are still paying it, and we have folded it into a bigger number you cannot see the seams of".
Why it is not a platform fee
A platform fee is what a ticketing company charges for its software: the event page, the checkout, the reporting, the check-in app. That is a legitimate thing to charge for. The problem is that many platforms quote the two costs as one blended figure, so a fee that is mostly software margin looks like an inevitable cost of taking payment. They are two different jobs done by two different parties.
| Charge | Who does the work | Roughly what it costs | Can you avoid it |
|---|---|---|---|
| Payment processing | The card processor (Stripe, Square, PayPal) | 2.9% plus 30 cents per transaction | No, it is the real cost of card acceptance |
| Platform fee | The ticketing company | Anything from zero to 5% plus a fixed fee per ticket | Yes, it depends entirely on which platform you pick |
Processing is the tax you owe the card networks. The platform fee is the tip you did not know you were leaving.
The 2.9% is the card networks' cut. Everything above it is a choice somebody made for you. Credit: Brano / Unsplash
Own Stripe versus merchant of record: who holds the money
There is a second, quieter difference hiding under the fees, and it decides when you actually get paid. It comes down to whose account the money lands in.
Under a merchant of record model, the platform collects every payment into its own account, holds the funds, deducts its fees, and pays you a net lump sum, often a few business days after the event and sometimes with a reserve held back. You get one payout and a fee already subtracted. Under an own processor model, you connect your own Stripe account, and the money lands with you at the moment of purchase, per transaction, with each fee itemised. Your bank feed and your sales report describe the same events, which makes reconciliation an afternoon rather than an ordeal.
Neither is evil, but they feel very different in practice. Merchant of record means less setup and someone else carrying the compliance. Own Stripe means you hold your own cash flow, you are not waiting until after the event to be paid, and there is no reserve quietly sitting on your money. For organisers with real cash-flow needs (paying deposits, suppliers and staff before the doors open), getting paid at purchase rather than after the event is the difference that matters.
The stacking problem, in one table
Now put the two charges together and you can see why "it is just processing" is such an expensive misunderstanding. Here is what different models actually take on a 50 dollar ticket, using published US rates.
| Platform | Headline fee structure | Total take on a 50 dollar ticket |
|---|---|---|
| Eventbrite | 3.7% plus 1.79 service, plus 2.9% processing | About 5.09, roughly 10.2% |
| Humanitix | 5% plus 1.29, processing included | About 3.79, roughly 7.6% |
| TryBooking | 1 dollar per ticket plus 3.5% | About 2.75, roughly 5.5% |
| Own Stripe only | 2.9% plus 30 cents, no platform fee per ticket | About 1.75, roughly 3.5% |
The gap between the top row and the bottom row is not processing. Processing is the same 2.9% plus 30 cents underneath all of them. The gap is platform fee, stacked per ticket, at every event. On a flat subscription like eventcloud's 125 dollars per user per month, the per-ticket platform fee is zero and payments run through your own Stripe, so the only per-transaction cost is that unavoidable floor. Compare that against a stacked model on the Eventbrite comparison and the maths is stark once you are selling in volume.
How to read your real cost per ticket
Two quick habits will keep you honest. First, always split the quote. When a platform gives you a single percentage, ask which part is processing and which part is their software. If they cannot or will not separate it, assume the difference above roughly 3% plus 30 cents is their margin. Second, do the maths at your real ticket price and volume, not on a headline. A fixed per-ticket fee (that 1.79 or 1.29) punishes cheap tickets hardest: on a 10 dollar ticket, 1.79 is nearly 18% before you add the percentage. The lower your face value, the more a fixed fee hurts.
There is a third habit worth building: watch what happens to your fees on refunds and chargebacks, because that is where blended pricing gets sneaky. When you refund an attendee, the card processor's percentage is often returned to you but the fixed portion sometimes is not, and a chargeback can cost you a flat dispute fee on top. Under a merchant of record model those adjustments are buried inside a net payout, so you rarely see them line by line. Under your own Stripe account each refund, each returned fee and each dispute shows up as its own entry, which is dull to look at and wonderful when the finance team asks you to explain a number.
To be fair, for a tiny free event none of this matters, because free tickets carry no platform fee on most platforms and there is no card to process. And if you sell only a handful of tickets a year, a pay-as-you-go per-ticket platform can be cheaper than any subscription. The break-even only tips toward flat pricing once you are moving real volume across the year. Below that, honesty says stay where you are.
But if you are selling thousands of paid tickets and telling yourself the fee is "just card processing", it is worth an hour with a calculator. Separate the floor from the ceiling, decide whether you want to be paid at purchase or after the event, and price accordingly. Start with the numbers on the eventcloud pricing page and see how much of your current fee is actually processing, and how much was just along for the ride.
