Ticketing fraud is usually discussed as a security problem, which is why it is usually solved badly. Security problems get security budgets: a better scanner, a rotating barcode, an app that refuses screenshots. Those measures help, and every one of them has been deployed for years, and the losses have not gone away. That is the clue. Fraud in this market is not a perimeter failure. It is a structural consequence of selling a bearer instrument into a market where the issuer cannot see the transfer.
We think the right way to reason about it is as a tax. Somebody pays it, on every transaction, in a form that rarely appears on a line item labelled fraud.
Who actually pays
Start with the fan who buys a counterfeit and is turned away at the gate. They lose the ticket price, but the rights-holder loses more: a supporter who tells the story for a decade, a seat that showed as sold and sat empty, and a stewarding incident at a gate on a match day. None of that is booked as fraud loss.
Then the payment layer. Chargebacks on event tickets are unusually expensive because the dispute usually arrives after the event, when the merchant has no way to prove attendance and the acquirer has already released funds. High chargeback ratios raise processing costs across the whole book, not just on the disputed transactions, and in severe cases they threaten a merchant account entirely. A ticketing platform’s payment economics are therefore hostage to a fraud problem it does not fully control.
Then the rights-holder’s own inventory. Speculative listings — seats offered for sale before the seller holds them — distort the visible price curve and pull demand away from the primary sale. Bulk acquisition by automated buyers compresses the window in which ordinary supporters can buy at face value. Both are enabled by the same underlying fact: an admission right that can be listed, promised and transferred without the issuer seeing any of it.
Fraud is not what happens at the gate. It is what happens in the gap between the sale and the gate, where the issuer has no visibility and no policy.
Why the usual defences plateau
Rotating barcodes solved copying. That was a genuine advance, and it moved a large share of counterfeit losses out of the system. But it moved them rather than removing them, for three reasons.
- The fraud migrated upstream If you cannot forge the credential, you defraud the account that holds it. Credential stuffing against ticketing accounts, social-engineered transfers and marketplace impersonation all attack the human, not the barcode.
- Closed apps fragment the fan A supporter with tickets from a club, a promoter and a resale platform now holds three apps and one confused expectation. Confusion is the raw material of social-engineering fraud.
- Transfer stayed invisible Even where a platform supports in-app transfer, a substantial share of real-world transfers happen outside it — a screenshot, a message, a printed page handed over in a car park. The issuer sees none of it.
Each additional control raises the cost of attack a little and the cost of legitimate use a little too. Eventually the friction curve crosses: the measure that stops the fraudster also stops the grandmother. Most large rights-holders are somewhere near that crossing point now, which is why incremental hardening has stopped producing results.
What changes with a verifiable credential
A credential that is cryptographically bound to an issuer changes the failure mode. A forgery does not fail at the gate after a supporter has travelled; it fails at verification, wherever verification happens — including inside a resale marketplace before money changes hands. Moving detection earlier in the chain is where most of the economic benefit sits, because the expensive part of fraud is not the lost ticket revenue, it is everything that happens after a real person has been let down.
Binding the credential to a holder changes the second failure mode. If the right to attend is tied to a verified identity or a registered device, a stolen barcode is worth much less, and the market for stolen barcodes thins out accordingly. This is where the design work gets genuinely difficult, because identity binding trades against the legitimate, ordinary act of giving your seat to a friend.
That is why transfer policy, not cryptography, is the real product. A credential that can carry rules — transferable once, to a verified recipient, at or below face value, until a defined cut-off — lets the rights-holder permit the legitimate transfer and refuse the industrial one, using the same mechanism.
Not “how do you stop forgery”, but: where in the chain does a fraudulent credential first fail, who bears the loss today at each step, and what does your system do when the venue network drops at 14:45 on a Saturday?
The transfer economics nobody models
Here is the part that turns a security investment into a commercial one. Once transfer is observable, resale stops being leakage and becomes a channel. The rights-holder can set a policy that participates in the transfer — a share of the uplift, a capped resale price, a requirement that the seat returns to an official marketplace — and can do so with the confidence that the policy is enforced by the credential rather than by a terms-of-service page nobody reads.
That has a second-order effect on the primary market. Season-ticket renewal decisions are influenced by whether a holder believes they can responsibly release seats they cannot use. A safe, sanctioned transfer path improves renewal, and renewal is the single most valuable number on a rights-holder’s ticketing report.
It also improves the fan record. When a transfer is executed inside the system, the receiving fan is identified and consented, and the club learns who actually attended rather than who bought. Attendance data with identity attached is what makes hospitality upsell, sponsorship measurement and safety planning work. It is, in our view, the most under-priced asset in the entire ticketing stack.
How we underwrite it
When we look at a company in this area, we are not trying to establish that fraud exists. We are trying to establish who currently absorbs the cost, because that person is the buyer. Sometimes it is the club, sometimes the promoter, sometimes the payment processor, and occasionally it is the fan, in which case the sale is much harder and the founder needs to know that before they build a pipeline around it.
We then ask what the product replaces rather than what it adds. Rights-holders rarely rip out a ticketing system; they wrap it. A company that can sit alongside an incumbent platform, take over issuance and transfer policy, and leave access control hardware untouched has a dramatically shorter sales cycle than one demanding a full migration.
And we ask about the season. Ticketing procurement runs on a calendar with two or three windows a year. A product that misses the window waits, and a company that has not modelled that in its cash plan will run out of money in a month when nothing was ever going to close.