> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://learn.nuwebgroup.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://learn.nuwebgroup.com/_mcp/server. # How do ticketing platforms make money? > Learn how ticketing platforms earn revenue through transaction fees, subscriptions, licences and services, and what each model means for operators and buyers. **Ticketing platforms make money by charging for the technology and services used to sell, manage and fulfil event tickets.** Common revenue models include per-ticket fees, order fees, percentage-based commissions, subscriptions, enterprise licences, implementation work and optional services. Some platforms also participate in payment-related revenue or operate marketplaces that help events reach buyers. The commercial model depends on who the platform serves and what responsibilities it takes on. There is an important distinction between the **price a ticket buyer pays**, the **revenue earned by the ticketing business** and the **revenue retained by the event organiser**. The same checkout can involve several companies with different rights to each amount. ## What are the main ticketing platform revenue models? **Most ticketing businesses combine transaction revenue with recurring or contracted income.** A platform may serve individual organisers, venues, ticketing operators or businesses building ticketing into another product, so no single pricing model fits every arrangement. | Revenue model | How it works | Typical trade-off | | --------------------------------- | ---------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- | | **Per-ticket fee** | A fixed charge applies to each paid admission | Revenue follows volume, but low-value tickets may be sensitive to fixed fees | | **Percentage of sales** | A share of the defined transaction value is charged | Scales with price, but requires a precise definition of the fee base | | **Per-order fee** | One charge applies to a basket or completed order | Easier for multi-ticket orders, but basket composition matters | | **Subscription** | A monthly or annual payment covers agreed access and limits | Predictable spend, but unused capacity still has a cost | | **Licence or minimum commitment** | A negotiated fee covers technology, support or committed usage | Better commercial predictability at scale, with contractual obligations | | **Services and add-ons** | Implementation, integrations, managed operations or support are charged separately | Flexible scope, but total cost can be harder to compare | These are commercial patterns, not formal industry tiers. Public-facing platforms may publish standard fees, while infrastructure suppliers often negotiate terms according to volume, support, markets and integration requirements. Eventbrite, for example, publicly describes ticketing and payment-processing fees, while other platform businesses use subscription-plus-commission pricing. Neither structure reveals the whole contract for a larger enterprise implementation. ## Who pays the ticketing platform's fees? **Fees may be paid directly by the buyer, absorbed by the organiser, billed to the ticketing operator or divided between parties.** Who funds a fee and how it is displayed are separate decisions. A buyer-facing fee adds to the amount the customer pays. An absorbed fee is deducted from the seller's receipts or paid separately, so the customer sees a price that incorporates that cost. A platform licensing fee may never appear as a line item at checkout. Consider two hypothetical organisers offering a £40 admission: * **Buyer-pays arrangement:** the advertised and final price is £44 including a £4 mandatory ticketing fee, subject to any applicable tax-display rules. The organiser's contractual ticket proceeds may be £40 before other costs. * **Fee-absorbed arrangement:** the customer pays £40 all-in. The organiser may receive £36 before separate processing, tax and settlement adjustments if the same £4 is deducted from proceeds. The example isolates one fee to show the difference; real contracts often contain several charges. Neither arrangement is automatically more economical. Demand sensitivity, tax treatment and transparency rules also affect the choice. ## How is a ticketing platform different from a ticket marketplace? **A ticketing platform provides systems for issuing and managing tickets; a ticket marketplace also helps buyers discover offers from multiple sellers.** A company can be both, but the economic value it delivers may differ. A marketplace may charge transaction commissions partly in return for discovery, audience reach and marketing distribution. An infrastructure provider may instead license its technology to a ticketing business that develops its own customer relationships and demand. A venue running direct sales may prioritise control over branding, customer accounts and payment arrangements over marketplace reach. This affects the comparison of fees. Paying for a marketplace audience is not the same product as paying for a booking engine, although both may charge a per-ticket amount. Ask which services, traffic sources, marketing tools and operational responsibilities are included. ## Where do payment fees and ticketing revenue fit? **Payment processing is a separate cost centre and sometimes a separate revenue stream.** A card transaction can involve a gateway, processor, acquiring services, a merchant and the ticketing platform. Their roles can be performed by different companies. Some platforms allow connected businesses to contract with a processor directly. Others offer managed payments or platform-payment arrangements. In the latter case, the platform may collect an application fee, charge for payment-related services or negotiate revenue sharing where its provider permits. Stripe Connect documents more than one approach to who sets processing prices for connected businesses. It would be misleading to assume that every “processing fee” is passed through at cost or that every “service fee” belongs entirely to the technology company. The contract should identify the fee recipient, who bears refunds and disputes, and how net proceeds are calculated. **Merchant of record is another distinction:** it identifies a merchant-side role under a particular payment arrangement, not simply the company whose software powers checkout. ## Which costs matter beyond the headline fee? **Total ticketing cost includes the technology charge and the work needed to run the operation safely.** A low fee per ticket is not necessarily the lowest-cost arrangement if staff must manually reconcile orders, maintain integrations or handle avoidable admission problems. Useful cost categories include: * Setup, data migration, seat-map configuration and integration development. * Ticketing fees, gateway charges, payment method costs and currency conversion. * Support coverage for major onsales and event days, plus staff training. * Access control equipment, printing, messaging and fulfilment. * Reporting, data exports, API access, SSO or advanced permissions where charged separately. * Refund administration, chargebacks, reconciliation and contract exit costs. An established ticketing operator also needs to examine its **own gross margin**, not just its supplier's price. If it sells under its own brand, it must understand which customer fees it can set, what costs it carries and whether the arrangement permits differentiated services. ## How should businesses compare ticketing commercial models? **Compare models using the same realistic ticket mix, support requirements and operating assumptions.** A provider quoting a smaller percentage may be more expensive for low-price orders if it also charges a fixed amount per transaction. Build a sample model covering different ticket values, baskets containing multiple tickets, complimentary admissions, refunds, peak onsales and geographic payment methods. Calculate buyer-facing totals and organiser net proceeds independently. If the provider offers volume tiers or minimum commitments, test quiet months as well as busy ones. Ask whether prices are indexed or change by volume, what happens when event sales are cancelled or refunded, which fees apply to box-office orders and which services are excluded. Where different entities collect fees, request a worked statement showing the contractual flow of funds. **The best model is the one whose economics, operating responsibilities and customer experience fit the business—not simply the one advertising the lowest fee.** ## Related explanations #### [How do booking fees and service fees work in ticketing?](/checkout-commerce/how-do-booking-fees-and-service-fees-work-in-ticketing) Checkout & Commerce · Pricing, fees and business models #### [How can white-label ticketing businesses control prices and fees?](/checkout-commerce/how-can-white-label-ticketing-businesses-control-prices-and-fees) Checkout & Commerce · Pricing, fees and business models #### [What does all-in ticket pricing mean in different markets?](/checkout-commerce/what-does-all-in-ticket-pricing-mean-in-different-markets) Checkout & Commerce · Pricing, fees and business models #### [Which payment methods should ticketing platforms support?](/checkout-commerce/which-payment-methods-should-ticketing-platforms-support) Checkout & Commerce · Payments and settlement [More in Checkout & Commerce →](/checkout-commerce)