How to compare the full cost of ticketing platforms

You're comparing ticketing platforms, and every price page seems to be answering a slightly different question. One quotes a fee per ticket. Another leads with a percentage. A third says the organizer pays nothing, because the buyer covers the charges. Which one actually costs your event business less?

Compare the cost of running the same sales through each platform, including payment processing, subscriptions, services you need and the work your team still does. Then separate what your business pays from what buyers pay. A low advertised rate is useful only when the complete calculation still works for your events.

The first thing you want to do is choose a real event or a realistic year of events. Ask each provider to price that exact business, with the same tickets, order sizes and payment assumptions. You'll learn more from that exercise than from comparing the cheapest example on each website.

We'll work through the charges to include, a fictional comparison where the cheaper transaction rate produces the more expensive total, and the questions to settle before signing. The aim is a written cost comparison you can explain to your finance team without having to guess what a provider meant.

Start with the event business you're buying for

A ticketing quote needs a sales plan behind it. If you're comparing platforms for a recurring venue, use the season or year you expect to run. If you're buying for one conference, use that event. Keep the period identical across providers, particularly when one charges monthly and another charges annually.

Write down paid tickets by price, rather than multiplying capacity by your highest ticket price. Include your expected early releases, discounts and premium tickets. Add the number of orders, because an order containing several tickets can attract a different total charge from several separate purchases.

Keep complimentary tickets and free registrations separate. Ask whether they use an allowance, attract a charge or require a paid plan. Don't assume "free events" describes how complimentary places at a paid event are treated. Those are different questions, and the answer belongs in the quote.

Specify where your business is based, where the event takes place and the currency in which you want the money. If international cards or currency conversion are relevant, say so. A domestic card example doesn't establish the cost of the payment mix you expect to receive.

Use recent order reports when you have them. For a new event, label the sales mix as an assumption and keep a lower sales case. You don't need a perfect forecast to compare costs fairly. You do need every provider using the same forecast, rather than selecting whichever assumptions make its pricing look cheapest.

Translate every fee into a charge you can calculate

Ask what triggers each charge and which amount it applies to. "Per transaction" is not precise enough if one provider means an order and another means a ticket. Get the unit written down before putting anything into your calculation.

For a fixed charge per paid ticket, multiply the rate by paid tickets. For a fixed charge per order, multiply by paid orders. For a percentage, establish whether the provider applies it to the ticket amount after discounts, the complete buyer payment or another stated amount. Include its rounding method where it affects the result.

Separate platform fees from payment processing until you have confirmed whether processing is included. If a bundled ticket fee already includes the relevant card processing, adding a separate processor estimate exaggerates its cost. If processing is excluded, leaving it out makes the same comparison misleading in the other direction.

Ask about minimum charges, monthly minimums and thresholds. A low rate above a volume threshold might be irrelevant to your first season. A minimum commitment might still be payable if an event is cancelled. Record when the obligation starts and whether it applies across your account or separately to each event.

Prepaid credits need another question. What happens to credits you don't use? Divide the amount you actually have to buy by the tickets you realistically expect to issue, allowing for the provider's expiry and refund terms. A discount for buying more tickets than you need can increase the cash you spend.

Keep a dated copy of the written offer and the terms it refers to. A screenshot showing "from" pricing is a research lead. It doesn't tell your team what your account will be charged when sales start.

Keep buyer charges and organizer costs visible

An organizer can have no platform deduction on a sale while the buyer pays a substantial booking charge. That doesn't make the transaction free. It changes who funds it, and it changes the total price people compare with other things they could do that night.

Prepare two views. The first shows your business's deductions and invoices. The second shows the buyer's complete payment for the same ticket selection. Keep them separate instead of adding a passed fee to your organizer costs and counting it again in the buyer total.

For the platform comparison, decide whether you are holding the underlying ticket amount constant or holding the buyer total constant. Those choices answer different commercial questions. At the same underlying ticket amount, a higher passed fee increases what buyers pay. At the same buyer total, a higher charge can reduce what remains for the event.

Don't quietly change that assumption between providers. Our guide to absorbing ticketing fees or passing them to buyers explains the pricing decision in detail. Here, the job is to make the provider costs comparable before deciding how your event will fund them.

Price presentation also matters. For covered US live-event tickets, the FTC's fee-rule guidance requires the displayed upfront total to include known, calculable mandatory charges, with specified exceptions including government charges, shipping and optional purchases. The total must be more prominent than other price information, subject to the rule's final-payment provision.

That guidance was checked in October 2026. Its live-event definition includes concerts, sport and live performances; don't assume every paid gathering has identical coverage. Check the requirements for your sales markets. A provider's fee allocation setting does not decide what your advertising must disclose.

Add the subscriptions and services your event needs

List the work the platform must support before you price the extras. A venue selling reserved seats needs a usable seating arrangement. A touring operator might need several staff accounts. An event with substantial door sales needs a way to take payments and issue valid tickets at the entrance.

Ask which of those requirements are included in the quoted plan. Then ask what happens at the volume you expect. Email allowances, account permissions, data access and support levels can matter more than a feature appearing somewhere on a website. "Available" and "included in this quote" need separate answers.

Use the cost of the package you would actually buy. If your required seating or support sits on a higher plan, compare that plan. If you would keep your existing email system regardless, don't claim its entire subscription as a saving from a replacement you won't make.

The same applies to hardware. Include purchase or hire, delivery, connectivity and any additional staff training your chosen entrance setup requires. Ask whether your existing phones or devices are supported. Buying new equipment is a real cost; deciding that you need it without checking is an avoidable one.

Advertising spend and promoter commissions should remain identifiable. They are costs of acquiring sales, even when the platform helps manage them. Don't describe a ticketing tool as covering your advertising budget just because campaign controls appear in the same account.

For each extra, name the requirement it satisfies and the person who approved it. If nobody can explain why the event needs the service, leave it outside the required package and price it separately as an option. This keeps the comparison useful without filling it with every possible upgrade.

Build the comparison so someone else can audit it

You can use a spreadsheet, but the arrangement matters more than the software. Start with a section containing the assumptions shared by every quote. Keep ticket quantities, prices and order counts there. When your sales plan changes, update those inputs once and calculate every provider again.

Below that, separate transaction charges, recurring fixed charges and one-time costs. Keep estimated staff time identifiable. Put cash costs in their own subtotal before adding the value of work, so a colleague can see whether the saving would reduce bills or free up your team's time.

Give every charge a source. That can be the dated written quote, a particular clause in the agreement or your own recorded estimate for a task. If a provider tells you a charge doesn't apply, record that answer with the conditions. "Not applicable for domestic card orders" is more useful than an unexplained zero.

Avoid hiding uncertain costs inside a general contingency amount. If international payment charges are unknown, leave that item unresolved and ask for the rate. A contingency can help with event budgeting, but it doesn't explain why one provider's quote is incomplete. Someone approving the purchase should be able to see which totals are confirmed.

Finally, include a short note on differences you can't fairly price. One option may offer the required support hours and the other may not. Another may fail a demonstration your entrance team needs. Resolve those requirements before using the cost subtotal to choose a winner. Your comparison should explain why the shortlisted platforms qualify.

Refunds and disputes can leave costs after the sale disappears

A cancelled or refunded order can change both revenue and charges. Ask each provider which original fees come back, whether there is another refund charge and who funds the amount returned to the buyer. Check partial refunds as well as full cancellations.

Stripe's refund documentation, checked in October 2026, says its original processing fees aren't returned when a successful payment is refunded. It also explains that refunds depend on the available balance. Those are Stripe's documented arrangements, not a statement that every ticketing provider passes the same costs to organizers.

Your agreement needs to explain the platform's treatment. A platform may combine charges or take responsibility for parts of the process. Don't apply the processor's public terms directly to your own bill without establishing who is charging you and what your contract says.

Payment disputes are separate from refunds you approve. Stripe's explanation of how disputes work describes a cardholder raising a dispute through their issuer, with the payment amount and applicable dispute fees deducted during the process. The documentation also explains that evidence and deadlines affect how the dispute is handled.

Ask who receives the notification, who submits evidence and whether the quoted service includes that work. Confirm which dispute fees are returned following a successful challenge. Don't estimate the platform's total liability by multiplying a generic industry rate by ticket revenue.

Use your own experience for a normal refund allowance, then examine a separate cancellation case. Returning all buyer payments is a different problem from handling occasional refunds. Keep refunded revenue separate from fees retained after refunds, so the same money doesn't become a loss twice in your comparison.

Compare cash timing without calling your own money a fee

Money held temporarily by a provider is not automatically a cost. It's still important if your venue deposit is due before the money becomes available. A low fee can be commercially awkward when the payout schedule requires cash your business doesn't have.

Ask about initial account approval, the first payout, normal payouts, reserves and event-related restrictions. Ask when the bank can actually make the money available. "Weekly payouts" describes a frequency; it doesn't establish which sales qualify for the next transfer.

Stripe distinguishes payout schedules from settlement timing. Its documentation, checked in October 2026, explains that changing how often payouts are sent doesn't make pending funds available sooner. Bank processing can add time after a transfer is sent. Again, your ticketing agreement determines the arrangements that apply to your account.

Build the cash dates into your event cash-flow forecast. If you need temporary funding, include its actual fees or interest in a separate financing line. Don't add the entire delayed payout to platform costs. That would treat your own receivable as money you have permanently lost.

Check the cancellation position too. If ticket proceeds have already paid suppliers, how will refunds be funded? If a reserve is held, what conditions release it? You need a workable answer even when both providers have the same transaction charge.

A platform can be affordable over the year and still fail your next deposit deadline. Decide whether the timing is acceptable before ranking it as the cheapest suitable option. Otherwise your comparison may recommend an arrangement the event cannot finance.

Put a realistic value on the work your team still does

Your team will do some work whichever platform you choose. Don't charge one provider for every hour of event administration while assuming the other needs none. Compare the tasks that genuinely change, using a demonstration or a test rather than a promise about saving time.

Ask the person who will run ticketing to create an event, find a booking, handle a permitted change and prepare a payout report. Include a group order and a refunded order when checking reports. A neat dashboard is pleasant; being able to explain the bank deposit is more useful to your accounts team.

For ongoing work, estimate the difference in hours and multiply by a reasonable staff cost. Label the rate and hours as your assumptions. If salaried staff will remain employed either way, that value describes time made available for other work. It is not automatically a reduction in payroll.

Migration and training belong in the first year. Include rebuilding event settings, preparing contact imports, teaching the entrance team and operating the old account while unfinished business remains. Our guide to switching ticketing platforms explains that operational move. Here, count the work so the purchase decision reflects it.

Support deserves a practical test. Who can your duty manager contact during your actual event hours? What help is included, and what requires another agreement? A faster response may matter, but don't invent a dollar saving for an incident you cannot reasonably estimate.

For essential support, treat an inadequate service as a reason the platform doesn't qualify. You don't have to turn every operational requirement into a speculative financial penalty before taking it seriously.

A worked comparison of two fictional quotes

Let's use a deliberately simple example. Everything in this comparison is fictional, in USD, and illustrates the method rather than any provider's pricing. Assume a year of events sells 2,000 paid tickets at $40 each through 1,000 orders. Ticket revenue is $80,000, with two tickets in every order.

Both quotes cover the same required work. The organizer absorbs all charges. There are no discounts, taxes, refunds, disputes, currency conversions or financing costs in this base case. The comparison values staff time separately from supplier invoices, and assumes the stated work estimates are reasonable for this operator.

Quote A charges $0.60 per ticket for the platform, plus payment processing of 3% of the ticket amount and $0.30 per order. Its platform charge is $1,200. Percentage processing is $2,400, and the fixed order charge is $300. Total transaction charges are therefore $3,900.

Quote B bundles platform and processing into $2.50 per paid ticket, giving transaction charges of $5,000. At this point, A looks cheaper by $1,100. If you stop at transaction fees, that's the answer you would take to the team.

Now add the rest. A requires an annual software package costing $1,200. Its additional operating work is valued at $900 for the year, and its initial setup work at $600. B has no required software subscription in this example, operating work valued at $600 and initial setup valued at $200.

The first-year total becomes $6,600 for A and $5,800 for B. B costs $800 less on the stated assumptions, despite its higher transaction charge. The result comes from the required subscription and estimated work, rather than a claim that bundled pricing is always cheaper.

Source: illustrative arithmetic using the fictional assumptions in this section. These are not market prices, customer results or Loopyah quotes. Work amounts are estimated staff-time values, so the totals are not entirely cash invoices.

Dividing by 2,000 tickets gives a first-year cost of $3.30 per paid ticket for A and $2.90 for B. Dividing by $80,000 of ticket revenue gives 8.25% and 7.25%. These measures include the stated software and work costs; they are not the advertised payment-processing rates.

For renewal, remove setup only if it won't recur. A then costs $6,000 and B costs $5,600 under unchanged assumptions. Keep the first-year and renewal answers visible. The setup difference matters, but it doesn't explain the entire gap.

Test the assumptions that could change the winner

In the fictional example, A has the lower transaction cost, so higher ticket volume can eventually make it cheaper. At the assumed $40 price and two tickets per order, A's transaction cost averages $1.95 per ticket. B's is $2.50. The difference is $0.55 per ticket.

A's first-year subscription and work costs total $2,700; B's work costs total $800. The difference is $1,900. Divide $1,900 by $0.55 and A needs more than 3,454 tickets to offset that difference. At 3,456 tickets in 1,728 orders, A becomes slightly cheaper while preserving the assumption of two tickets per order.

That's a useful threshold only if the fixed costs really stay fixed and the price and order mix remain similar. More events might require extra support or staff time. If that happens, change the assumptions and calculate again rather than quoting the threshold as a universal rule.

Order size can change the answer too. Keep 2,000 tickets and $80,000 revenue, but put every ticket in a separate order. A's fixed processing charge becomes $600 instead of $300. Its total rises by $300. B stays unchanged because its fictional bundled charge is per ticket.

Ticket prices matter when one quote includes a percentage. A move towards higher-priced premium tickets increases the percentage part of A's charges. A larger number of cheaper tickets changes the balance differently. Use the mix you expect to sell, not the single ticket price that happens to favour your preferred platform.

Also test lower sales against annual commitments. A subscription still needs paying when demand disappoints, unless your agreement says otherwise. You don't need dozens of scenarios. Concentrate on assumptions that are uncertain enough, and expensive enough, to affect the choice.

Ask for a quote you can check against an actual payout

Send the same short request to each shortlisted provider. Include your event period, paid tickets by price, order count, payment assumptions and required services. Ask for the estimated buyer payments, organizer deductions and separate invoices, with the fee calculation shown.

Ask the provider to identify exclusions rather than treating a blank line as zero. If refunds, international payments or event-day support cannot be priced from the information supplied, get the applicable rate or the question they need answered. An incomplete quote can stay under consideration, but it can't win a completed cost comparison.

Have the provider calculate an ordinary group order and a refunded order. Compare its answer with your own model. This is where a fee calculated on the complete payment, or a fixed charge applied per ticket, becomes much easier to notice.

Bring one awkward transaction from your own events into that discussion. Perhaps a company buys several conference places, then changes one attendee and requests a partial refund. Or a buyer purchases online and the entrance team must find the order when their phone is flat. Ask the provider to show the ordinary steps and explain any charge.

You are checking whether the quoted package supports the work, rather than demanding a custom demonstration of everything you might eventually do. Keep the test relevant to a transaction your staff actually handles. If a workaround requires another subscription or manual preparation, include it in the comparison.

Keep the answer with the quote. A colleague taking over ticketing next season should be able to repeat the task without relying on your memory of a sales call. That small amount of preparation also makes it easier to challenge an unexpected invoice using the agreed terms after the first event.

Request a sample payout statement with personal details removed. Can you connect sales, fees, refunds, adjustments and the amount transferred? Check whether reports include the fields your bookkeeper needs. A low rate is less attractive if the accounts team must repeatedly investigate unexplained differences.

Finally, confirm the price period, renewal terms, notice requirements and treatment of unused commitments. Ask whether the written quote or the standard terms prevail if they differ. Keep the agreed answer with the comparison so another team member can understand what was approved.

Review commitments beyond the first event

An annual agreement can change the cost of a short event season. Ask when billing begins, whether you can pause between events and what happens if your programme shrinks. Compare the amount you must pay over the commitment, rather than multiplying an attractive monthly rate by only the months you intend to sell.

Check renewal separately from launch pricing. If an introductory discount expires, use the confirmed renewal rate for the later period. If the next rate isn't guaranteed, say that. A three-year comparison built on an unconfirmed promise to hold prices is less useful than an honest first-year calculation with the uncertainty recorded.

Volume pricing needs careful treatment. Ask whether reaching a threshold changes the rate on every ticket in the period or only later tickets. Also ask whether volumes combine across events. Those details can change the amount payable even when two quotes advertise the same discounted rate. Get a worked example using your expected volume.

A cancellation case should show the commitments that remain. The venue bill and artist contract belong in your wider event budget; this comparison should show the ticketing subscription, unused credits, retained charges and any contracted services you still owe. Keep the platform calculation limited to costs caused by that arrangement.

Before accepting an advance, rebate or promised marketing contribution, ask what repayment conditions apply. A benefit tied to exclusivity or minimum sales can create a future obligation. Record the benefit and the obligation separately, with the relevant dates, so nobody approves a lower apparent cost without understanding the commitment that produced it.

Check what the platform actually removes

A fuller ticketing product can replace paid tools or reduce repeated work, but only count the parts you will use. A platform with more features isn't automatically better value for a simple event. Equally, a low ticket fee isn't the full answer if you must buy another service to perform an essential task.

Loopyah's ticketing tools combine ticket sales with card processing in the paid-ticket fee and let organizers choose whether to absorb that fee or pass it to buyers. The same live page describes scanning tickets and taking door payments using the Loopyah app. These capabilities were checked in October 2026.

For a business that sells at the entrance, that connection is worth testing against its current process. Ask the team to demonstrate the required purchase and check-in tasks, then compare the equipment, services and work your event would actually need. Don't translate a feature description into a guaranteed saving.

Use the current rate for your country and the terms for your account. The fictional quotes above are deliberately separate from Loopyah's prices. Processing being included answers one comparison question; it doesn't remove the need to check refunds, support, eligibility and payout conditions.

Data arrangements also deserve attention before signing. Where a supplier processes personal data for your business under UK GDPR, the ICO's processor guidance explains that a binding contract must contain compulsory provisions. The guidance is under review following legislative changes. Establish the roles and current requirements that apply to your circumstances rather than assuming a ticketing subscription resolves them.

Make the buying decision explicit

Choose the lowest credible total among the platforms that can perform the work your events require. Keep buyer price and cash availability visible alongside that total, and distinguish invoice savings from the value of staff time. If your preferred provider costs more, explain the specific capability or service that justifies paying it.

Before signing, have the person responsible for ticketing and the person responsible for the accounts review the same calculation. Resolve missing charges with the provider, attach the written terms and record the assumptions that would trigger another review. Your next comparison can then start with actual statements and experience, rather than another collection of advertised starting prices.