Ticket vendor guide and resale glossary
Ticketmaster, See Tickets, Tixel, TicketSwap and the rest, without the panic.
Ticket sites all look much the same until a sale gets hot. Then the differences start to bite. Queue behaviour, buyer limits, whether the app matters, how resale works, and the small print that quietly decides whether your group gets in together.
Seller index
Jump to the seller or term you need.
A quick glossary for when a festival guide names a seller, a resale route or an app mechanic you haven't used before.
Before you buy
Read the event page first. Then work out how the seller behaves.
A ticket plan has two layers, and people usually only do one of them. Start with the event's own current page, which is where you'll find the buyer limit, the age rules, whether tickets are named and whether they can be transferred at all. Only then work out how the seller behaves: how you log in, what the queue does, whether the tickets land in an app.
When a guide here says collect an account, it means the email address, phone number or username that official flow needs. It never means the password. Keep credentials private, keep 2FA on the owner's own phone, and record who is responsible for buying and paying somewhere other than a chat thread.
TicketSquad uses that shape in every event guide, because it's the order that stops people wasting prep. The seller tells you how the sale behaves. The event tells you what the tickets actually mean. You need both before anyone tries to buy anything.
- Use official event and vendor links. Never a screenshot, and never a stranger in your DMs.
- Capture the exact buyer limit and split the Squad into checkout-sized Groups.
- Write down the ticket type, the fallback, the all-in budget and who's actually paying.
- Check whether transfers, resale and name changes are enabled for this specific event.
- Find out what the buyer will be asked for. Names and emails, sometimes dates of birth, postcodes, ID or access evidence.
- Share account identifiers only: email address, phone number or username. Never share passwords or one-time codes.
What our research shows
The same seller names keep coming up. The event rules never stop moving.
We counted these across our own event research catalogue while building this guide. It isn't market-share data, and we wouldn't pretend otherwise. It's a practical signal from the events we actually track. Ticketmaster dominates our sample, but European resale platforms come up often enough that a group planning a trip abroad needs the wider glossary.
Vendor signals in our event research
Most common buyer limits we found
That spread is why our event guides keep talking about Groups. Ten friends might need splitting into a six for a Glastonbury-style sale, or a four for some Ticketmaster limits, or pairs for a Burning Man-style public sale. The friendship group and the checkout group are rarely the same shape.
Queues and bot checks
Don't try to outsmart the queue. Try to look like a prepared, ordinary buyer.
Ticket sellers don't publish their full fraud rules, and that's deliberate. So the useful advice is dull. Use the official link. Log in early if they ask you to. Have your payment ready. Don't run bots or auto-refreshers, and don't open extra sessions unless the seller has explicitly said you can.
Community reports tell you where fans get hurt. They aren't official rules, and people do overstate them. Fans describe both AXS and Ticketmaster as unforgiving about refreshes, extra tabs and repeated logins from odd networks. Take that as a reason to be conservative on the day. It is a terrible reason to run an experiment.
Do
Read the event page on sale morning, keep one clean buyer session per account unless told otherwise, and leave the queue page alone if the vendor says not to refresh.
Do not
Run auto-refreshers, browser automation, VPN gymnastics, repeated logins, copied queue URLs, or tab/device experiments during a high-demand sale.
Prepare
Your account email or phone, access to your own login and 2FA, a payment card, a billing address, and the exact product you have agreed to buy.
After a failure
Write down the error, keep the official page open if you were told to, then move to the fallback you already agreed. Don't start guessing.
When the official queue guidance is vague, be boring. One account. One sensible browser session. No refreshing unless they tell you to, no passing queue links around, and nothing built to imitate human traffic.
Vendor glossary
The ticket sites and resale routes your Squad will most likely meet.
Names matter more than you'd think under pressure. Tixel, TicketSwap and Twickets are three separate companies, and a fast-moving group chat blurs them together within about four messages. Confirm the exact official link before anyone joins a waitlist, switches on auto-purchase or pays a seller.
Primary seller and official resale
Ticketmaster
Most common vendor signal in our event research.
Best for
Large UK and international festivals, stadium shows, arena tours, presales, official resale and transfer-supported events.
App or website
Website and app. Use the official event page for the sale, and keep the app logged in for mobile tickets, transfers or resale where they're enabled.
Resale route
In-site or in-app Fan-to-Fan resale and Ticket Transfer where the event enables them. Some events disable both, delay transfer, or name another official resale route.
Queue / buying mechanic
Expect a waiting room on high-demand sales. The official advice almost always comes down to one clean session, staying on the page, and doing whatever that event says about refreshing.
Transfer and resale default
Transfers and resale depend on the event. Some events enable Ticket Transfer or Fan-to-Fan resale; some keep transfers closed until nearer the show; some use lead-booker or app rules.
Fan sentiment to verify
Fans value official barcode and transfer tooling, but community reports often describe bot errors, locked sessions, dynamic pricing and punishing refresh or multiple-tab behaviour.
Gotcha
Having a Ticketmaster account isn't preparation. The group still needs the product, the buyer limit, the card owner and the fallback agreed before anyone tries to buy.
Collect for the group
Account identifiers only. Email address, phone number or username may be useful; passwords and one-time codes should never be shared.
- Ticketmaster account email or phone number
- target product/date
- buyer limit
- payment owner
- transfer/resale status
Primary seller, fan-to-fan resale and event-specific flows
See Tickets
Frequent across UK festivals and one of the most important Glastonbury-adjacent sellers.
Best for
Festival primary sales, event-branded ticketshops, payment plans, official resale portals and named-ticket events.
App or website
Mostly web and event-branded ticket shops. Account, wallet or app requirements vary by event, so check the exact sale page.
Resale route
See Tickets Fan-to-Fan or event-run resale where enabled; some events instead use named tickets, scheduled resale windows or a third-party resale partner.
Queue / buying mechanic
Queue behaviour is event-specific. Treat the official festival or See Tickets page as the current source for login, refresh and browser guidance.
Transfer and resale default
See Tickets powers different resale and ticket delivery setups. Some events use official resale, some use named tickets, and some place responsibility on the original booker.
Fan sentiment to verify
Fans tend to trust event-branded See Tickets flows, but complaints usually focus on opaque queues, payment-plan differences and event-specific account rules.
Gotcha
See Tickets often sits behind an event-branded page, so groups mix up the festival's rule with the seller's rule. Write down both.
Collect for the group
Account identifiers only. Email address, phone number or username may be useful; passwords and one-time codes should never be shared.
- See Tickets or event-shop account email
- order holder
- ticket type
- name fields
- official resale route
Official or approved resale for many festivals
Tixel
A recurring official resale route in UK and Australian-style festival data.
Best for
Sold-out festival resale, waitlists, capped-price resale and events where the festival explicitly points buyers to Tixel.
App or website
Web marketplace with mobile-friendly alerts and purchase flows. Set up the account, notifications and payment path before a high-demand resale moves.
Resale route
Third-party resale marketplace when the event appoints or approves Tixel. It is not the original seller unless the event sends buyers there.
Queue / buying mechanic
The pressure here isn't a classic queue. It's alert speed, waitlist setup and knowing your exact category before any money moves.
Transfer and resale default
Tixel verifies tickets and handles buyer protection, but final delivery can still depend on the original ticket platform and event rules.
Fan sentiment to verify
Fans like the price caps, verification and auto-purchase idea; the stress points are alert speed, category mistakes and final delivery depending on the original ticket platform.
Gotcha
Auto-purchase is only relaxing when the group has already signed off the category, the quantity, the max price and who's paying.
Collect for the group
Account identifiers only. Email address, phone number or username may be useful; passwords and one-time codes should never be shared.
- Tixel account email
- ticket category
- max price
- auto-purchase consent
- who still needs resale
Fan-to-fan resale and SecureSwap
TicketSwap
Common in European festival resale research, especially where TicketSwap is named or culturally normal.
Best for
Face-value-ish resale, secure barcode replacement where supported, and fast-moving day/pass resale.
App or website
Website and app. Alerts can work on both, but the app and push notifications can matter for high-demand drops, raffles and auto-buy-style flows.
Resale route
Third-party resale marketplace. SecureSwap can reissue or protect tickets where TicketSwap has the right partnership; otherwise the original ticket rules still matter.
Queue / buying mechanic
The mechanic here is speed and trust rather than a long waiting room. Alerts, account readiness and payment readiness all matter.
Transfer and resale default
SecureSwap can invalidate the seller barcode and issue a new one where partnered; otherwise the transfer depends on the original ticket and event.
Fan sentiment to verify
Fans like SecureSwap and broad European adoption; complaints tend to be fastest-click-wins alerts, bot anxiety and uncertainty when SecureSwap is not supported.
Gotcha
TicketSwap being popular doesn't make it official for your event. If the festival names a different resale route, use that one first.
Collect for the group
Account identifiers only. Email address, phone number or username may be useful; passwords and one-time codes should never be shared.
- TicketSwap account email or phone number
- exact pass/day
- max price
- official status
- delivery method
Face-value resale marketplace
Twickets
Less frequent in current festival rows, but important for UK gigs and some festival-adjacent resale.
Best for
Face-value resale for gigs, theatre, sport and selected festival tickets where Twickets is an approved partner.
App or website
Marketplace website, with app-style alerts where available. Watchlists and notifications are preparation, though. They don't mean a ticket is being held for you.
Resale route
Third-party face-value resale when fans list there or an artist/event approves Twickets. Delivery still depends on the original platform.
Queue / buying mechanic
Usually alert-and-buy rather than queue-and-wait. Watchlists and notifications help, but the group still needs a budget and category decision.
Transfer and resale default
Delivery can be mobile transfer, e-ticket, postal or collection depending on the event. Seller proof and the original platform matter.
Fan sentiment to verify
Fans like the face-value positioning and artist partnerships; complaints often mention scarce listings, basket races and delivery-method uncertainty.
Gotcha
Face value doesn't mean a listing solves your entry problem. Named tickets, lead-booker rules and transfer timing all still apply.
Collect for the group
Account identifiers only. Email address, phone number or username may be useful; passwords and one-time codes should never be shared.
- Twickets account email
- acceptable section/category
- max price
- delivery method
- lead-booker risk
Primary seller, waiting room and official resale
AXS
A major UK and international signal for arena, stadium and London festival-style events.
Best for
Arena shows, premium products, mobile ID tickets, official resale and venue-linked sales.
App or website
Website for buying, with the AXS app often important for Mobile ID tickets, entry, transfer and resale controls.
Resale route
In-site or in-app transfer and official resale where the event enables them. AXS Mobile ID and transfer locks are event-controlled.
Queue / buying mechanic
AXS waiting rooms are often about being ready before the sale, then being placed when the sale opens. Do not assume arriving earlier guarantees a better place.
Transfer and resale default
AXS Mobile ID, Transfer and Resale are event-specific. Some tickets become transferable later; some stay locked.
Fan sentiment to verify
Fans often describe AXS as especially unforgiving about suspicious-activity checks, refreshes, VPN or network quirks and app ticket visibility. Treat it as one clean session unless official guidance says otherwise.
Gotcha
The AXS app login and phone access can matter as much as the browser session, especially where entry is by mobile ID.
Collect for the group
Account identifiers only. Email address, phone number or username may be useful; passwords and one-time codes should never be shared.
- AXS account email
- app readiness
- ticket tier
- resale/transfer status
- phone owner
App-first tickets, waiting lists and transfers
DICE
Common in club, electronic, venue and city-festival research.
Best for
App-first event tickets, waiting lists, refunds to waiting list, QR tickets and friend transfers inside the DICE app.
App or website
App-first. The website is useful for discovery, but ticket management, send-to-a-friend and wait-list actions are usually in the DICE app.
Resale route
In-app return to wait list and friend transfer where the event enables them. Some events disable those buttons or close them near show time.
Queue / buying mechanic
DICE pressure often comes from app readiness, waiting-list notifications and fast payment rather than a browser queue.
Transfer and resale default
Send-to-a-friend and waiting-list returns depend on the event and timing. Some tickets lock close to show time.
Fan sentiment to verify
Fans like quick app tickets and wait-list returns; the pain point is that transfer and wait-list availability can change by event and timing.
Gotcha
If one person buys for everybody, the group needs to know upfront whether those tickets are staying on that phone or getting sent out later.
Collect for the group
Account identifiers only. Email address, phone number or username may be useful; passwords and one-time codes should never be shared.
- DICE account phone/email
- waiting-list status
- friend-transfer plan
- show time
- refund deadline
UK festivals, club nights and Re:Sell
Skiddle
A strong UK signal in the event catalogue, especially for electronic and regional events.
Best for
UK festival and club inventory, payment plans, waiting lists, Re:Sell and event add-ons.
App or website
Website plus app. The app can matter for waiting-list notifications and checkout once tickets are allocated.
Resale route
In-platform Re:Sell and waiting list where the event enables them. Promoter settings decide what can be returned or resold.
Queue / buying mechanic
Skiddle can use waiting lists, reminders and high-demand sale pages. Follow the event page for refresh, payment-plan and ticket-limit guidance.
Transfer and resale default
Re:Sell and ticket management depend on the event. Some events allow resale; others restrict name changes, refunds or transfers.
Fan sentiment to verify
Fans like official Re:Sell and clear add-ons; gotchas include short waiting-list claim windows, missed app notifications and extras scattered across the flow.
Gotcha
Add-ons hide in plain sight. Coach travel, parking, lockers and payment plans all sit alongside admission, and people miss them.
Collect for the group
Account identifiers only. Email address, phone number or username may be useful; passwords and one-time codes should never be shared.
- Skiddle account email
- ticket tier
- add-ons
- payment-plan choice
- resale/waiting-list status
UK festival ticketshops and account-managed resale
Kaboodle
Important for Boomtown and other UK festival flows with named accounts and travel products.
Best for
Festival primary sales, official resale, travel products, name changes and event-branded ticket portals.
App or website
Event-branded web ticket shops and account pages. App requirements are event-specific rather than a universal Kaboodle buying pattern.
Resale route
Event-controlled official resale, name change or ticket-management tools where enabled. Use third-party resale only when the event points there.
Queue / buying mechanic
Kaboodle mechanics vary by event. The important prep is usually account access, exact ticket type and any travel/public-transport product.
Transfer and resale default
Some Kaboodle-backed events use name changes, official resale or buyer-managed tickets. The original booker often matters.
Fan sentiment to verify
Fans value event-specific ticket management when it works; pain points are resale windows, name-change deadlines, transport-linked products and original-booker dependency.
Gotcha
A ticket route can be tied to transport, resident status, camp choice or a name-change deadline.
Collect for the group
Account identifiers only. Email address, phone number or username may be useful; passwords and one-time codes should never be shared.
- Kaboodle account email
- ticket route
- travel ticket
- name-change status
- resale route
European ticketshops and resale-backed flows
Paylogic
Frequent across Dutch, Belgian and European electronic festival research.
Best for
Paylogic shops, personalised tickets, official resale links, add-on-heavy festival products and European dance events.
App or website
Event-branded web shops and account or personalisation links, often reached through email after purchase.
Resale route
Event-controlled official resale, name change or repersonalisation where enabled. Some events integrate a third-party resale marketplace.
Queue / buying mechanic
Queue and waiting-room details are usually controlled by the event ticketshop. Check current shop guidance before trying to buy.
Transfer and resale default
Paylogic-backed events often expose personalisation, name changes or official resale, but the exact rules sit with the event.
Fan sentiment to verify
Fans like clean personalisation links when they arrive; frustration usually comes from missed deadlines, market-specific help pages and event-by-event differences.
Gotcha
The personalisation deadline often matters more than the buying moment. Get real attendee names and emails early.
Collect for the group
Account identifiers only. Email address, phone number or username may be useful; passwords and one-time codes should never be shared.
- Paylogic shop account email
- attendee name
- personalisation deadline
- resale link
- add-ons
Primary tickets and official resale in several European markets
EVENTIM and fanSALE
Lower frequency than Ticketmaster in our current pack, but important for Germany and central Europe.
Best for
German and European primary sales, fanSALE resale, printable/mobile tickets and event-specific name rules.
App or website
Country-specific EVENTIM websites and apps, with fanSALE as the in-family resale route in supported markets.
Resale route
fanSALE is the in-family official resale route where the event and country site support it. Country rules, payment details and name checks differ.
Queue / buying mechanic
EVENTIM demand can be queue-like or ordinary checkout depending on the event. Prepare account and payment early, then follow the live page.
Transfer and resale default
fanSALE can be the official resale lane where supported; personalised-ticket events may need name-change handling.
Fan sentiment to verify
Fans trust fanSALE for supported events, but report confusion around country sites, IBAN/payment requirements, transfer timing and personalised tickets.
Gotcha
EVENTIM's country sites differ. Treat the UK, DE and IT markets as relatives rather than the same shop.
Collect for the group
Account identifiers only. Email address, phone number or username may be useful; passwords and one-time codes should never be shared.
- EVENTIM account email
- country site
- fanSALE status
- ticket name
- delivery method
Club, electronic and festival listings
Resident Advisor
A recurring source for electronic events, club nights, city festivals and multi-venue programming.
Best for
Electronic events, club nights, festival parties, resale/waitlist-style demand and event discovery.
App or website
Website and app/listing ecosystem. Use the event page and RA account controls to confirm what is actually enabled.
Resale route
Event-specific transfer, resale, refund or waitlist controls where enabled. RA should not be treated as a universal resale marketplace.
Queue / buying mechanic
The buying pressure is often product timing, waitlist status and account readiness rather than a classic numbered queue.
Transfer and resale default
RA ticket transfer, resale or refund options vary by event and seller setup. Check the event page and RA account controls.
Fan sentiment to verify
Fans like RA for electronic discovery and trusted listings; complaints usually come from strict event controls, last-entry rules and unclear transfer/refund availability.
Gotcha
RA events often carry strict age, last-entry and ID rules. Those belong in your group plan as well as the listing's small print.
Collect for the group
Account identifiers only. Email address, phone number or username may be useful; passwords and one-time codes should never be shared.
- RA account email
- event date/time
- ticket tier
- last entry
- ID rule
How this guide improves
This guide gets better every time we research another sale.
This one is alive. Every festival or gig we research adds seller detail that fans can actually use. Which site handles the sale. Whether the app matters. How resale works in practice rather than in the terms. What other people report going wrong. Where a rule hasn't been published yet, we'll say so plainly instead of inventing a confident answer.
Official seller and resale link
The official ticket page, primary seller, app requirement, approved resale route and any event-specific partner.
App or website
Whether buying, ticket delivery, transfer, resale or wait-list actions work best in the app, on the website or both.
Ticket limit
How many tickets one person, account, card or household can buy, and whether limits change by ticket type.
Queue and bot checks
Waiting room timing, refresh advice, tab/device/IP/VPN warnings, and anything fans should avoid so they do not lose their place.
Safe account details
The email address, phone number or username needed for buying, transfer or resale. Never passwords, recovery codes or one-time codes.
Details needed to buy
Names, emails, phone numbers, DOBs, postcodes, registration numbers, ID, accessibility evidence or lead-booker details.
Transfer rules
Whether tickets can be transferred, renamed, resold, returned to a waiting list, or only used by the original buyer.
Resale route
Whether resale happens inside the seller app/site, through an event-run exchange, or via a named partner, plus price caps, fees and timing.
Payment and plans
Accepted payment methods, deposit/payment-plan rules, instalment deadlines, card-owner constraints and refund rules.
What fans report
Reddit, forums and fan reports for what people like and dislike: queue gotchas, app pain, support delays, false sell-outs and practical buyer tips.
Resale and transfer
Whether a ticket can move is a rule, and you need it before money does.
The same marketplace can be exactly right for one event and the wrong route for the next one. A seller might reissue a barcode, or move the ticket inside an app, or change a name, or release tickets late, or leave the original buyer responsible for getting everybody through the gate. If the event names Tixel, use Tixel. If it names TicketSwap, use TicketSwap. If it says no transfers, believe it.
Official resale
A resale route named by the event, promoter or primary vendor. Start here before any public marketplace.
In-site resale
Resale inside the same primary seller account or app, such as Ticketmaster Fan-to-Fan, AXS Resale, Skiddle Re:Sell or DICE wait-list returns where enabled.
Third-party official resale
A separate resale site named by the event, such as Tixel, TicketSwap or Twickets. It can be official for one event and irrelevant for another.
Fan-to-Fan
Vendor-managed resale where another fan buys the ticket through the official system, often with new delivery or barcode handling.
Transfer
Sending a ticket to another account or app. Transfer can be disabled, delayed or restricted by event.
Account identifier
The email address, phone number or username needed to find an account for buying or transfer. It never means a password or one-time code.
App-first ticket
A ticket where buying may happen on web, but delivery, transfer, resale or entry depends on a mobile app.
Name change
Changing the named attendee on a personalised ticket. Often fee-based, deadline-based or limited to one change.
Waiting list
A vendor-managed list for returns or sold-out products. Some waitlists only notify; some can auto-charge.
Secure barcode reissue
A resale mechanic where the original barcode is cancelled and the buyer receives a new valid ticket.
Where TicketSquad helps
Where the seller rules turn into something your friends can actually follow.
TicketSquad doesn't sell tickets, jump queues or scrape sellers. It helps with the human half of the job. Pick the official route, split by the buyer limit, collect the data once, record who is trying for which Group, and keep everyone helping after the first person gets through.
Which matters, because the seller is only one part of the mess. There are also budgets, lead bookers, access needs and everyone's travel. A good plan keeps all of that visible while the sale site is still quiet.
More hard-mode ticket guides
Planning another big one?
The buying-group method changes shape by event: different ticket agents, account rules, limits, products, travel plans and fallback routes.
Ready to plan your next ticket sale?
Turn vendor rules into a buyer-ready plan
Create the event, then collect the account emails, buyer limits, transfer rules, budgets and fallback products once. Do it while the ticket site is still quiet.
Sources
Official and community sources checked for this guide.
- Ticketmaster UK Fan Support: Smart Queue
- Ticketmaster UK Fan Support: Ticket Transfer
- Ticketmaster UK Fan Support: selling tickets
- See Tickets: Consumer Terms and Conditions
- See Tickets: Fan-to-Fan Marketplace
- Tixel: how Tixel works
- Tixel: Seller and Buyer Terms of Use
- TicketSwap Help: SecureSwap
- TicketSwap Help: how TicketSwap works
- Twickets: how Twickets works
- AXS Help: waiting room
- AXS Help: Mobile ID and the AXS app
- DICE Help: add tickets to the wait list
- DICE Help: send tickets to a friend
- TicketSwap Help: ticket alerts
- TicketSwap Help: raffles
- Skiddle Help: Re:Sell
- Skiddle Help: waiting list
- Kaboodle Help: Ticket Resale
- Paylogic Customer Service: transfer or re-personalize tickets
- EVENTIM fanSALE
- Resident Advisor Help Centre
- Reddit community thread: Ticketmaster bot activity reports
- Reddit community thread: AXS suspicious-activity reports