Protection
Anti-scalping in Bookitive — the risk score, every signal it reads, the flag/verify/hold/block action ladder, and how the pieces fit into one system.
Protection keeps tickets in the hands of real fans. Every public checkout is scored for abuse risk, scored orders meet a configurable response ladder, and a set of supporting tools — phone verification, per-customer limits, named tickets, rotating QR delivery — makes bulk-buying and resale-for-profit hard while honest buyers never notice a thing.
The hub lives at Protection in the organization sidebar, with four tabs: Overview (activity metrics), Rules, Review queue, and Lists.
The risk score
Each incoming public order gets an advisory 0–100 score. Low scores always pass; medium (30+) and high (60+) trigger whatever action you configured. The score is built from named signals, each visible on the order so a decision is never a black box:
| Signal | What it caught |
|---|---|
| Frequent orders from this email / phone / IP | Velocity within the last hour |
| Active across many of your events | Cross-event buying sprees |
| Many orders from the same device | Device fingerprint velocity |
| Disposable email address | Throwaway inboxes |
| Undeliverable email address | Fake contacts |
| Proxy, VPN, or datacenter | IP anonymizers |
| IP country differs from the phone | Geographic mismatch |
| Automated / non-browser request | Bots |
| Repeated verification attempts | OTP friction |
| Large number of tickets · High order value · At the per-order limit | Size amplifiers |
Two design choices worth knowing: server-observed signals lead — client-supplied data (like the device fingerprint) only ever amplifies a score that real server evidence started, so a scalper can't be saved by faking client data, and an honest buyer can't be condemned by it. And scoring never blocks by accident — if a lookup service is down, that signal is skipped; an outage can't freeze your sales.
The response ladder
For each band you pick one action — the ladder from softest to hardest:
Flag only → Require phone verification → Hold for review → Block.
Defaults are set organization-wide and inherited by every new event; each event can override them. Details: Rules and actions.
The supporting cast
- Phone verification — SMS-verified buyers, and the key that makes max per customer limits on ticket types enforceable.
- Attendee names — one name per ticket, printed and checked at the door.
- Rotating QR delivery and transfer policies — tickets that can't be screenshot-resold.
- Allow and deny lists — your manual overrides in both directions.
Tune with the Overview
The Overview tab shows how protections have been firing — risky orders, held, approved, blocked, and the top signals over 7/30/90 days. Lots of held orders you end up approving? Soften the medium action. Blocked buyers writing you support emails? Check the deny list. The metrics exist so the knobs get turned with evidence.
Related
Guest list
Every ticket holder in one live list — arrival status, search by name or code, ticket expansion, exports, and the door's no-tech fallback.
Rules and actions
What happens to a risky order — flag, require phone verification, hold for review, or block — configured as organization defaults with per-event overrides.