Use casesEvent ticketing, box offices and ticket resale
Get tickets to fans, not bots
Check for a person when someone joins the queue, checks out or transfers a ticket, without a puzzle in the way at the busiest moment.
Request
Checkout for 4 tickets
The on-sale opened a minute ago
An on-sale lasts minutes. Bots need seconds.
When a popular event goes on sale, scripts join the queue, hold seats and check out faster than any fan. The tickets reappear on resale at a markup, and fans blame you. HEIP checks the purchase at the moment it happens.
Why now
1,000 tickets bought by scripts × a $150 resale markup = $150,000 out of fans' pockets.
What you get
- Tickets that reach fans
- Because HEIP checkswhether a person was in control at checkout
- A queue for people
- Because HEIP checksqueue entry and seat holds, with a policy for each
- No puzzle at the busiest moment
- Because HEIP checksquietly, and answers step up only when it isn't sure
- Transfers you can stand behind
- Because HEIP checksthat the action token was issued for this transfer, in this session, and used once
Actions to protect
| Action | Suggested policy | On step up, you usually |
|---|---|---|
| Checkout | Fast | One-time code, or release the seats |
| Transferring or reselling a ticket | Critical | Re-authenticate |
| Changing account email or phone | Critical | Re-authenticate |
| Joining the queue | Standard | Verify email or phone |
| Browsing events | Observe | Nothing: observe only, never blocks |
Policies are named presets you set per action. Critical asks for the most evidence. Fast suits frequent actions that still matter. Standard fits everyday actions. Observe never blocks.
Where it fits
HEIP works with your queue and checkout. It decides when to ask for a step, so most fans never see one.
Works alongside
- Virtual waiting rooms
- Purchase limits
- Verified-fan programs
- Payment and fraud checks
Roll it out on on-sale checkouts
Baseline
Pick on-sale checkouts. Note how they're protected today.
Observe
HEIP decides on real traffic but blocks no one.
Compare
Review its decisions against what you already know.
Enforce
Turn it on for on-sale checkouts only if it earns it.
Most teams go from observe to enforce in 6 to 8 weeks. Observe mode blocks no one while you compare. How onboarding works
Questions
Does HEIP replace our waiting room?
No. The waiting room controls how many people get through. HEIP checks whether a person is in control when they act.
Will it slow checkout down during an on-sale?
Only a step-up adds a step for the fan. The decision itself is a single call from your server.
Do we still need purchase limits?
Yes. Limits cap how much one account can buy. HEIP checks whether a person is buying at all. They work best together.
Can we try it on one event first?
Yes. In observe mode HEIP records what it would have decided and changes nothing for fans.
Trust has to move with the action.
When digital actions can be automated, trust must move with them.