You set your ticket price at $50. Your ticketing platform charges 5%. Stripe takes 2.9% + $0.30. Your state charges 8% sales tax. Your venue takes 10%.
After all the cuts, you net $36.70 on a "$50 ticket."
Now multiply that by a few wrong assumptions about how fees stack, and you're either bleeding margin without knowing it or overcharging buyers and watching cart abandonment climb.
Event ticket pricing isn't just about picking a number. It's about understanding the fee layers, making deliberate decisions about who pays what, and choosing a structure that holds up at scale — across different ticket types, currencies, and tax jurisdictions.
This guide breaks down every fee decision an event promoter needs to make, when each approach works, and what happens when you get it wrong.
The Fee Stack: Understanding Every Layer
Before you can set fees, you need to understand the layers that eat into (or add onto) your ticket price. Most promoters think about fees as a single number. In reality, there are three distinct layers, and each behaves differently.
Layer 1: Ticketing Platform Fees
This is what your ticketing platform charges for using their service — typically 2-8% of the ticket price, sometimes with a flat per-ticket minimum.
These fees are per ticket. Sell 500 tickets at $50 with a 5% platform fee, and you've paid $1,250 in platform fees regardless of how many individual orders those tickets came from.
Layer 2: Payment Processing Fees
This is what Stripe, Adyen, Square, or your payment processor charges to handle the transaction. The standard Stripe rate in the US is 2.9% of the transaction total + $0.30 per transaction.
The critical distinction: processing fees are per order, not per ticket. A buyer purchasing 4 tickets pays one $0.30 fixed fee, not four. This is the math that breaks most all-in pricing calculations — and it's the reason you can't simply multiply a single-ticket "all-in price" by quantity and get an accurate total.
Layer 3: Taxes and Regulatory Fees
Sales tax, VAT, entertainment tax, venue surcharges — these vary by jurisdiction, event type, and sometimes even ticket type. Some regions tax the base ticket price. Others tax the base price plus service fees. Some require service fees to be included in the taxable base; others don't.
Getting this wrong isn't just a margin issue — it's a compliance risk. Under-collecting tax means you owe the difference out of pocket. Over-collecting means you're overcharging buyers.
The Five Fee Decisions Every Promoter Must Make
Decision 1: Flat Fee vs. Percentage Fee
| Model | How It Works | Best For | Watch Out For |
|---|---|---|---|
| Flat fee | Fixed dollar amount per ticket (e.g., $3.00) | Events with a narrow price range (all tickets $30-$50) | Looks disproportionately large on cheap tickets, trivial on expensive ones |
| Percentage fee | Percentage of ticket price (e.g., 5%) | Events with wide price ranges (GA at $25, VIP at $200) | Can get very large on high-value tickets without a cap |
| Percentage with cap | Percentage with a max ceiling (e.g., 5%, max $10) | Multi-tier events with premium tickets | Requires a platform that supports min/max fee caps |
The right call: If all your tickets are within a $20 range of each other, a flat fee is simpler and easier for buyers to understand. If you have GA at $30 and VIP at $250 on the same event, percentage with a cap prevents the VIP fee from becoming unreasonable while keeping GA fees proportional.
TicketBlox supports all three models — flat, percentage, and percentage with min/max caps — configurable per fee type, per event.
Decision 2: Absorb Fees or Pass Them Through
This is the decision that affects your margin and your buyer experience more than any other.
Absorb (promoter pays): The buyer sees $50, pays $50. You absorb the platform fee, processing fee, and any other charges out of your revenue. Your net on a $50 ticket might be $43 instead of $50.
Pass through (buyer pays): The buyer sees $50 base price + fees at checkout. The total might be $57.50. You keep your full margin, but the buyer experiences "sticker shock" at checkout.
Hybrid (split it): You absorb some fees (platform) and pass through others (processing). Or you inflate the base price slightly to cover part of the fees while keeping the visible fee amount small.
There's no universally right answer. But there are patterns:
- Premium events (VIP, exclusive, high-ticket): Absorb fees. Your buyers are paying $200+. A clean, round number signals professionalism. The $8 fee you absorb is invisible against the ticket price.
- High-volume, low-price events (club nights, community events): Pass through fees. At a $15 ticket price, absorbing a $2.50 fee means you're giving up 17% of your revenue. That's not sustainable.
- Recurring event series: Pick one approach and be consistent. Switching between absorbing and passing through across events creates pricing confusion and erodes buyer trust.
The key is that buyers don't hate fees — they hate surprises. If you pass fees through, show them clearly. If you absorb them, your pricing should reflect that decision in your margin planning.
Decision 3: How to Handle Taxes
Tax on event tickets varies wildly by jurisdiction:
- Some states/countries tax the base ticket price only
- Others tax the base price plus service fees (meaning your ticketing fee increases the tax owed)
- Some regions require that service fees be included in the taxable base (your fee is effectively taxed)
- International events must handle VAT, GST, or local entertainment taxes that may apply at different rates to different ticket types
What this means practically: You need a fee engine that lets you mark individual fees as taxable or non-taxable, and that can include specific fees in the tax base calculation when the jurisdiction requires it.
Example: A $20 ticket with a $3.00 service fee in a jurisdiction where service fees are taxable:
- Taxable base = $20 + $3 = $23
- Tax at 8% = $1.84
- Buyer total = $24.84
If the service fee were marked as non-taxable, the tax would be $1.60 (8% of $20 only), and the total would be $24.60. That $0.24 difference multiplied across thousands of tickets adds up — and getting it wrong in the wrong direction means either you owe the tax authority the difference, or you've overcharged your buyers.
TicketBlox lets you configure each fee as taxable or non-taxable independently, and supports "include in base tax calculation" settings for jurisdictions that require it.
Decision 4: Multi-Currency Fee Structures
If you run events across multiple countries — or sell to international buyers — your fee structure needs to adapt to different currencies.
A 5% fee works universally. But a $3.00 flat fee doesn't translate to ¥300 or £3.00 — those are very different amounts in purchasing power terms.
The right approach: Set percentage-based fees as your default (they scale across currencies automatically), and use currency-specific overrides for flat fees. A $2.00 booking fee in USD might need to be £1.50 in GBP and ¥200 in JPY.
TicketBlox supports multi-currency fee overrides at the individual fee level. When a buyer checks out in MXN, the platform applies the MXN-specific fee configuration — including the correct decimal precision and rounding rules for that currency.
This matters for promoters operating across Latin American and Caribbean markets where currency variance is significant and decimal precision rules differ from USD.
Decision 5: Item-Level vs. Order-Level vs. Transaction-Level Fees
This is the structural decision most promoters don't realize they're making — and most platforms don't let them make deliberately.
| Level | Applies To | Example | Use Case |
|---|---|---|---|
| Item-level | Each ticket individually | 5% service fee per ticket | Standard ticketing fee |
| Order-level | The entire order once | $1.00 handling fee per order | Fulfillment, admin costs |
| Transaction-level | The payment transaction | 2.9% + $0.30 processing fee | Payment processor pass-through |
A single order can (and often should) include all three:
- 2% service fee on each ticket (item-level)
- $1.00 handling fee on the order (order-level)
- 2.9% + $0.30 processing fee on the total (transaction-level)
For an order of 3 tickets at $33.33 each:
- Item-level: 3 × $0.67 = $2.01
- Order-level: $1.00
- Transaction-level: 3% of ($100 + $2.01 + $1.00) = $3.09
Grand total: $106.10
If your platform only supports one fee level, you're either overcharging (applying order-level fees per ticket) or undercharging (applying item-level math to transaction-level costs). The math needs to be precise, especially when those fees interact with automated revenue splitting to partners and affiliates.
Putting It Together: A Fee Structure for a Real Event
Let's walk through a concrete example. You're running a 2,000-person festival with three ticket types:
| Ticket | Price | Qty Available |
|---|---|---|
| Early Bird GA | $35 | 500 |
| Regular GA | $50 | 1,000 |
| VIP | $150 | 500 |
Your fee decisions:
- Structure: Percentage fee (5%) with a $10 cap
- Absorb or pass through: Pass through to buyers with transparent all-in pricing display
- Tax: 8% sales tax on base price only
- Order-level: $1.00 handling fee per order
- Transaction-level: Payment processing passed through at actual cost
A buyer purchasing 2 Regular GA + 1 VIP:
- Tickets: $50 + $50 + $150 = $250
- Service fees: $2.50 + $2.50 + $7.50 = $12.50
- Handling: $1.00
- Tax: 8% of $250 = $20.00
- Processing: ~2.9% of $283.50 + $0.30 = $8.52
Buyer total: $292.02
Everything is trackable, auditable, and accurate. No spreadsheet required. And when your venue partner takes 10% of gross ticket revenue through automated revenue splitting, the calculation is clean because the fee structure is clean.
Common Fee Mistakes That Cost Promoters Money
Mistake 1: Using the Same Fee Structure for Every Event
A $3 flat fee makes sense for a $40 club night. It looks absurd on a $10 community event and trivial on a $300 gala. Match your fee model to your price range.
Mistake 2: Ignoring the Tax-on-Fees Question
If your jurisdiction taxes service fees and you haven't configured your fees as taxable, you're under-collecting tax and will owe the difference.
Mistake 3: No Cap on Percentage Fees
A 5% fee feels reasonable on a $50 ticket. On a $500 VIP package it's $25 — which some buyers will perceive as excessive. Always set a max cap.
Mistake 4: Calculating Fees Monthly in Spreadsheets
If you're exporting Stripe transactions and manually calculating fee breakdowns, you're wasting hours that could go into understanding your audience or building your affiliate network.
Mistake 5: Not Testing Multi-Ticket Cart Math
Add multiple ticket types to a cart and check the math. If processing fees multiply per ticket instead of per order, you're overcharging. This is exactly the issue correct all-in pricing solves.
How to Evaluate Your Platform's Fee Capabilities
When comparing ticketing platforms, promoters should ask:
- Can you set flat, percentage, and capped fees independently?
- Can you configure fees at item, order, and transaction levels?
- Can you mark fees as taxable or non-taxable?
- Does the platform support multi-currency fee overrides?
- Does the fee engine round correctly?
- Can you see a real-time fee breakdown per order?
TicketBlox's fee engine supports all of the above.
Book a Demo → and see how TicketBlox gives you complete control over your fee structure — without spreadsheets, without guesswork, and without losing buyers at checkout.
Frequently Asked Questions
How much should event ticketing fees be?
Industry standard ranges from 2-8% for platform/service fees, plus payment processing (typically 2.9% + $0.30 per order on Stripe). Total visible fees should stay under ~15% of ticket price.
Should I absorb ticketing fees or pass them to buyers?
Premium events often absorb fees. High-volume, low-price events usually pass them through. The key is transparency and consistency.
What's the difference between a flat fee and a percentage fee for events?
Flat fees are predictable but don't scale across ticket tiers. Percentage fees scale but may become large on expensive tickets. Percentage with a cap is often the best compromise.
How do taxes work on event ticket fees?
Some jurisdictions tax only the base ticket price; others tax the base plus service fees. Your platform should let you configure each fee as taxable or not.
How should I handle fees for international events?
Use percentage-based fees as default and override flat fees per currency. Your platform should support currency-specific rounding and precision.
What's the difference between item-level, order-level, and transaction-level fees?
Item-level applies per ticket, order-level once per order, and transaction-level to the payment transaction. A proper event pricing structure uses all three.