Insights / High-demand systems

Keeping a high-demand ticket on-sale fair and online

A popular on-sale compresses a huge amount of demand into minutes. That brings three problems at once: load that can take the system down, bots that crowd out real fans, and fraud that targets the payment flow. The answer is layered design, not one clever tool.

Protect the system with a queue

A virtual waiting room admits buyers at a rate your checkout can handle, and gives everyone a fair, visible position. Serve the waiting page from a CDN so it stays up even if the origin is under pressure, and decide your admission rule (first-come or randomised) in advance and explain it clearly.

Layer your bot defences

No single control stops determined bots. Combine rate limiting, behaviour and device signals, verified accounts, per-buyer ticket limits and challenges at sensitive steps. Measure false positives as carefully as you measure blocked bots, because turning away genuine fans is also a failure.

Keep inventory honest

  • Reserve seats with short holds that expire, and make the stock decrement atomic so you cannot oversell.
  • Make checkout idempotent so a retry or double-click never charges twice or issues duplicate tickets.
  • Show true availability. Fake scarcity ("only 2 left") erodes trust, and in many places can also fall foul of consumer law.

Keep card data out of your systems

Use a payment provider's hosted fields or redirect so card numbers never touch your servers. This shrinks your PCI DSS scope and the damage of any breach. Support strong customer authentication (3-D Secure) for card payments where required.

Make tickets hard to copy

Use signed codes, ideally rotating ones, so a screenshot is not enough. When a ticket is transferred or resold through a permitted channel, revoke and reissue it so only the current holder's code works.

Prove resilience before the day

  • Load test with realistic behaviour, at a multiple of expected peak, including retries and abandoned baskets.
  • Set autoscaling limits and degrade gracefully (for example, pause non-essential features) rather than falling over.
  • Have observability and a rehearsed runbook for the on-sale itself, with named people and clear escalation.
The principle. Fairness is a security property. The same controls that stop attackers also make the queue trustworthy to real buyers.