Ticket vendor guide and resale glossary
Ticketmaster, See Tickets, Tixel, TicketSwap and the rest, without the panic.
Ticket sites all look similar until a sale gets hot. Then the differences matter: queues, browser rules, buyer limits, resale routes, app tickets, transfers, personalisation and the weird little gotchas that decide whether a group actually gets in.
Seller index
Jump to the seller or term you need.
Use this as a quick glossary when a festival guide names a vendor, resale route or app mechanic you have not used before.
Before you buy
Start with the event page, then decode the vendor.
The safest ticket plan has two layers. First, read the event's current official page: dates, ticket types, age rules, buyer limit, named-ticket rules, transferability, resale route and entry requirements. Then read the vendor's mechanics: account login, queue behaviour, app delivery, payment, waiting list, transfer and resale.
When a guide says to collect an account, that means the account email address, phone number or username needed for that official flow. It never means the password. Keep credentials private, keep 2FA on the owner's device, and use TicketSquad to record who is responsible for buying, paying or receiving a transfer.
TicketSquad uses that shape in every event guide. The vendor tells you how the sale behaves. The event tells you what the tickets mean. Your Squad needs both before anyone starts trying to buy.
- Use official event and vendor links, not screenshots or strangers in DMs.
- Capture the exact buyer limit and split the Squad into checkout-sized Groups.
- Write down ticket type, fallback product, all-in budget and who can pay.
- Check whether transfers, resale, name changes and app delivery are enabled for this event.
- Know what data the buyer needs: names, emails, dates of birth, postcodes, IDs, access evidence or registration numbers.
- Share account identifiers only: email address, phone number or username. Never share passwords or one-time codes.
What our research shows
The same vendor names keep appearing, but the event rules keep changing.
We checked the current TicketSquad event research catalogue while building this guide. This is not market-share data; it is a practical signal from the events we track for group ticket planning. Ticketmaster dominates the sample, but European resale and festival-specific platforms show up often enough that groups need a wider glossary.
Vendor signals in our event research
Most common buyer limits we found
That limit distribution is why our event guides talk about Groups. A ten-person friend group may become a six-person Group for Glastonbury-style sales, a four-person Group for some Ticketmaster product limits, two-person Groups for Burning Man-style public sales, or one-at-a-time planning for live resale.
Queues and bot checks
Do not try to outsmart the queue. Try to look like a normal, prepared buyer.
Ticket vendors rarely publish their full fraud rules, and that is the point. The useful advice is boring and strong: use the official link, log in early where the vendor asks for it, keep payment ready, avoid bots and auto-refresh tools, and do not multiply sessions unless the seller explicitly says it is allowed.
Community reports are useful for knowing where fans get hurt, but they are not official rules. AXS and Ticketmaster are both often described by fans as unforgiving around refreshes, extra tabs, VPNs, unusual networks and repeated logins. Treat that as a reason to be conservative, not as a reason to 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
Account email or phone number, access to your own login and 2FA, payment card, billing address, exact ticket products and backup choices.
After a failure
Record the error, keep the official page open if instructed, and move to the agreed fallback route instead of guessing.
If the official queue guidance is vague, assume conservative behaviour: one account, one sensible browser session, no refresh unless told, no shared queue links, and no tools designed to simulate human traffic.
Vendor glossary
The ticket sites and resale routes your Squad is most likely to meet.
Naming matters under pressure. Tixel, TicketSwap and Twickets are separate systems, and a rushed group chat can easily blur them together. Confirm the exact official link before anyone joins a waitlist, turns 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; keep the app/account ready for mobile tickets, transfers and resale where 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 or queue on high-demand sales. Official advice usually favours one clean session, staying on the page, and following the event-specific instructions about refreshing, tabs and devices.
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
Do not treat a Ticketmaster account as enough preparation. The group still needs product choice, buyer limit, card owner, phone/app access and fallback rules agreed before trying 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
Because See Tickets often sits behind event-branded pages, groups can confuse the festival rule with the seller rule. Capture 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 is not usually a classic queue; it is alert speed, waitlist setup, auto-purchase settings and knowing the exact category before 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 calm when the group has already approved category, quantity, max price and payment responsibility.
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 is usually speed and trust, not a long waiting room. Alerts, account readiness and payment readiness 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 does not automatically make it official for every event. If the festival names a different official resale, use that 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. Treat watchlists and notifications as prep, not proof that a ticket is held.
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 does not mean every listing solves entry rules. Named tickets, lead-booker rules and mobile-transfer timing still need checking.
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
AXS accounts, app login and phone access can matter as much as the browser session, especially for mobile ID entry.
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 the group, everyone should know whether tickets will stay on that phone or be sent to friends 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 are easy to miss: coach, shuttle, VIP, parking, lockers and payment plans can sit beside admission.
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, citizenship/resident status, camp choice or name-change deadlines.
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
Personalisation deadlines can matter more than the buying moment. Capture 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
Country-specific EVENTIM sites differ. EVENTIM UK, DE, IT and other markets should be treated as related but not identical.
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 can have strict age, venue, last-entry and ID rules. Those belong in the group plan, not only in the listing 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
The more events we research, the sharper this seller guide gets.
This is a living guide. Every time we research another festival, gig or high-demand sale, we look for the seller details fans can actually use: which site handles the sale, whether the app matters, how resale works, what other fans report, and what your group should decide before trying to buy. If a rule is not published yet, we will say that plainly rather than pretending.
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
Transferability is not a vibe. It is a rule you need before money moves.
The same marketplace can be safe for one event and the wrong route for another. A seller may reissue a barcode, transfer inside an app, change a name, release a ticket closer to the event, or simply give the original buyer responsibility for entry. If the event says official resale is Tixel, use Tixel. If it says TicketSwap, use TicketSwap. If it says no transfer, 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
The app is where vendor rules become a plan your friends can actually use.
TicketSquad does not sell tickets, jump queues or scrape vendors. It helps the group do the human work cleanly: choose the official route, split by the buyer limit, collect the right data, record who is trying for which Group, and keep helping after the first successful buy.
That matters because ticket vendors are only one part of the mess. The group also has budgets, lead bookers, accessibility needs, travel, camping, app installs and resale fallbacks. A good plan keeps those decisions visible before the sale site gets busy.
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, collect account emails or phone numbers, buyer limits, transfer rules, budgets, fallback products, resale routes and payment owners before the ticket site starts getting busy.
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