Avoid tax and fulfilment errors: Stripe ticketing for UK events

Stripe works well as your payments engine, but most events need a ticketing layer on top of it unless you are running a single-tier, low-complexity sale. Your first move is to pick an integration mode: Checkout Sessions, Payment Links, or connecting your Stripe account to a ticketing platform. For most promoters, Lookport Ticketing offers a ready-built route that connects directly to Stripe without custom development.

TL;DR:

• Payment Links are best for simple, one-off sales with flat pricing, but offer limited branding options compared to Checkout Sessions.
• Checkout Sessions handle complex ticketing features like discounts and seating, but require some developer effort to set up and test thoroughly.
• Connecting Stripe to a dedicated ticketing platform simplifies integration, streamlines proceeds, and adds attendee management tools at a fixed commission.
• Stripe Tax calculates taxes based on the event location, not the buyer, requiring proper location data attachment and jurisdiction registration review.
• Using webhooks for checkout completion ensures reliable ticket delivery confirmation, with testing recommended before processing live transactions.

Table of Contents

• Quick checklist: which Stripe integration mode fits your event
• Integration step-by-step: Checkout Sessions, metadata and connecting your Stripe account
• Tax and compliance for ticket sales: Stripe Tax and performance locations
• In-person and hybrid sales: Terminal, POS and unified payment stacks
• Fulfilment and reliability: webhooks, checkout.session.completed and ticket delivery
• Payment methods, fees and payout timing: what organisers should expect
• How Lookport simplifies Stripe ticketing for concert promoters and organisers
• FAQ
• Sources
• Primary sources: Stripe documentation and Lookport links

Quick checklist: which Stripe integration mode fits your event

Your choice depends on how complex your ticket structure is and how much development time you have.

• Single-tier or community events: Payment Links give you a shareable checkout page with no code, ideal for one-off sales with a flat price.
• Multi-tier paid or seated events: Checkout Sessions give you control over line items, discounts and metadata, which suits tiered pricing or reserved seating.
• Marketplaces or multi-promoter events: connecting your Stripe account to a ticketing platform through its ‘Connect with Stripe’ flow keeps each promoter’s proceeds separate while centralising reporting.

Each path trades off differently. Payment Links take minutes to set up but offer little branding control. Checkout Sessions need some developer time but handle tax and currency conversion automatically. A ticketing platform adds attendee management on top, at the cost of a commission.

Before you integrate anything, gather your bank details, complete Stripe’s business verification, and confirm the event address, since this feeds directly into tax calculation later.

Integration step-by-step: Checkout Sessions, metadata and connecting your Stripe account

Start by creating and verifying your Stripe account, then enable Payments, Connect and Stripe Tax depending on which mode you chose.

1. Create the Checkout Session server-side, never in client-side code, and include your line_items with price and quantity for each ticket type.
2. Attach metadata such as event ID, ticket type and order ID to the session so you can match payments to specific tickets later.
3. Set success and cancel URLs so buyers land somewhere sensible whether payment completes or not.
4. For simple flows, use Payment Links instead, which support an after_completion redirect that can include the Checkout Session ID as a placeholder, useful for sending buyers straight to a confirmation or ticket-delivery page, according to Stripe’s Checkout Sessions documentation.
5. If you are connecting a ticketing platform’s Stripe integration, check what access it requests: a well-built ‘Connect with Stripe’ flow lets you keep proceeds in your own account while only granting the platform permission to create charges and read transaction data.
6. Test with Stripe’s test keys first, then use the Stripe CLI to forward webhook events to your local environment before going live.

Build a small test matrix covering a successful card payment, a declined card, an abandoned checkout and a refund, so you know each path behaves as expected before real buyers arrive.

Pro Tip: Run your full test matrix with Stripe’s test cards before connecting a live bank account, since a missed metadata field is far easier to fix before your first real sale.

Tax and compliance for ticket sales: Stripe Tax and performance locations

Ticket tax is assessed on where the performance happens, not where the buyer lives. Stripe Tax uses a performance_location, the event’s physical address, to work out the correct rate, as explained in Stripe’s tax guidance for tickets.

• Attach the performance location to each line item through the Tax Calculations API, Checkout Sessions, Payment Intents or Payment Links, so Stripe Tax calculates the right rate automatically, per Stripe’s location-based tax documentation.
• If you run ticketing through Stripe Connect, tax registrations and performance locations are managed per connected account, so you cannot share a single registration across multiple promoters or venues.
• Test mixed carts and cross-border events before launch, since a single order containing tickets for different venues can trigger different tax treatments within the same checkout.
• Review your registration status in each jurisdiction where you sell tickets, since liability can sit with you or with the platform depending on how the integration is structured.

In-person and hybrid sales: Terminal, POS and unified payment stacks

Taking payments on the door does not need to mean a separate system from your online sales. You have three practical options: Stripe Terminal for card-present hardware under your own Stripe account, a pre-certified POS integration, or letting your ticketing platform process in-house sales directly.

• Choose Stripe Terminal if you want door sales reconciled against the same Stripe account as your online checkout.
• Choose a pre-certified POS integration when you already use point-of-sale hardware for merchandise or bar sales and want ticketing on the same device.
• Let your ticketing platform handle in-house sales when you want a single dashboard across online and door transactions without managing hardware separately.

Whichever route you pick, confirm EMV and PCI compliance for the hardware, check battery life and connectivity for your venue, and plan for a backup payment method in case of a signal drop on the night.

Fulfilment and reliability: webhooks, checkout.session.completed and ticket delivery

Never rely on the redirect page alone to confirm a sale, since a buyer can close their browser before the redirect completes, leaving you with a paid order and no record of it. Stripe’s fulfilment documentation recommends webhooks as the reliable path instead.

1. Listen for checkout.session.completed as your primary trigger for releasing tickets.
2. Handle asynchronous payment events too, since some payment methods confirm success or failure after the initial checkout session closes.
3. Write idempotent fulfilment handlers so a retried webhook never issues the same ticket twice.
4. Verify webhook signatures server-side before processing any event, to confirm the request genuinely came from Stripe.
5. Test locally with the Stripe CLI, forwarding events to your development environment before you trust the flow in production.

Pro Tip: Log every webhook event you receive, even ones you don’t act on, since that log becomes your fastest way to diagnose a missing ticket complaint.

Payment methods, fees and payout timing: what organisers should expect

Offering more payment methods at checkout tends to reduce drop-off, particularly for younger audiences who expect digital wallets as standard.

• Cards remain the baseline, but adding Apple Pay, Klarna and Link gives buyers a faster path to completing payment.
• Klarna and similar methods can suit higher-priced tickets where buyers want to spread the cost.
• Link speeds up repeat purchases for buyers who have saved their details with Stripe before.

Stripe’s UK pricing page sets out standard processing fees alongside notes on local payment-method pricing offers and Instant Payouts eligibility, which varies by account and region rather than applying uniformly.

Build your assumed processing fee into your ticket price calculations from the start, and state clearly at checkout which payment methods you accept, so buyers are not surprised partway through.

How Lookport simplifies Stripe ticketing for concert promoters and organisers

Beyond payments, you get the pieces Stripe alone does not provide, including practical ideas like a five second QR check in for home poker leagues:

• QR check-in and ticket scanning for admission control on the door, covered on our ticket scanning page.
• Marketing integrations that connect your sales data to promotional campaigns, detailed on our marketing integrations page.
• Revenue modelling through our concert profit and tour budget calculator, so you can map ticket pricing against your event costs before you go on sale.

FAQ

Does Stripe do ticketing?

Stripe is a payments processor, not a ticketing platform. It handles checkout, tax calculation and payouts, but attendee management, QR check-in and seating need a ticketing layer such as Lookport Ticketing built on top of it.

Is Elon Musk invested in Stripe?

This question sits outside what this guide covers, since it concerns Stripe’s company ownership rather than how to integrate Stripe for ticket sales. We recommend checking Stripe’s own investor communications for current, accurate ownership details.

What platforms integrate with Stripe?

Many ticketing, e-commerce and subscription platforms integrate with Stripe through its APIs or Connect, including dedicated ticketing solutions like Lookport, which links proceeds directly to your own Stripe account. The right choice depends on whether you need custom checkout code or a platform that is already built and ready to connect.

What are the disadvantages of using Stripe?

Building a Stripe integration yourself takes development time, particularly to get webhooks, metadata and tax calculation working reliably, as outlined in Stripe’s fulfilment guidance. Stripe alone also lacks ticketing-specific features like QR check-in or seating management, which is why most organisers pair it with a dedicated ticketing platform.

Sources

• Checkout Sessions — Stripe Docs
• Stripe pricing — Stripe

Primary sources: Stripe documentation and Lookport links

The guidance above draws on Stripe’s own integration documentation. Follow the linked guides for full API details before you build.

Recommended

• Stripe payments for ticketing
• Online & hybrid ticketing
• Ticketing fee calculator
• Ticketing marketing integrations