Ticketing
What Causes Chargebacks on Resale Tickets?
Why do buyers dispute resale tickets after attending the show? A look at first-party misuse, delayed delivery, and what actually reduces it.
TL;DR
Friendly fraud, increasingly called first-party misuse, is a chargeback filed by the genuine cardholder against a purchase they actually made, whether from confusion, buyer's remorse, or deliberate abuse. It is now the dominant dispute category across card-not-present commerce, with estimates running from 60% to 75% of total disputes in delayed-delivery categories, and live events is one of the hardest hit because months pass between purchase and delivery. Standard fraud prevention barely touches it, because the person filing the dispute is a legitimate customer who authenticated successfully.
The fraud that passes every check
Fraud prevention tools are built to answer one question: is the person holding this card the person who owns it?
Friendly fraud is what happens when the answer is yes.
The cardholder is real. The device is theirs. The billing address matches. They passed authentication, completed the purchase, received the ticket, and attended the event. Then they called their bank and said the charge was not authorized.
Every control in a standard fraud stack approved that transaction correctly. That is the problem.
What is friendly fraud?
Friendly fraud is a chargeback filed by the legitimate cardholder against a transaction they themselves made. The card networks generally prefer the term first-party misuse, which is less charming and considerably more accurate.
It splits into three groups, and telling them apart matters more than the label.
- Genuine confusion. The buyer does not recognize a descriptor from a purchase made four months ago. They believe they are reporting fraud. In their mind, they are.
- Process avoidance. The buyer wants a refund and finds the dispute path easier than yours. If your refund flow is slower or more confusing than calling the bank, you have made this choice for them.
- Deliberate abuse. The buyer attends the event and disputes anyway, knowing the merchant rarely wins. One in five consumers admit to having done some version of this.
Only the third is what most people mean by fraud. All three arrive as the same chargeback.
How big is the problem?
It has stopped being a subcategory and become the main event.
In dispute terms the concentration is higher still. Analysis of Merchant Risk Council and LexisNexis data puts first-party misuse at 60% to 75% of total disputes for many merchant categories, with streaming, gaming, digital downloads, and travel worst affected.
The direction is consistent across sources. The Merchant Risk Council's 2026 survey of 1,278 merchants across 37 countries found 64% reporting rising first-party misuse, with one in four seeing increases of 25% or more.
Live events belongs in that worst-affected group for the same reason travel does. The gap between purchase and delivery is measured in months.
The losses you cannot prevent, covered
Chargeback indemnification moves first-party dispute losses off your P&L.
Talk to our team →Why is friendly fraud so hard to fight?
Because the tools that work against criminal fraud are the wrong tools for this problem.
Authentication does not help.
3D Secure shifts liability when a cardholder authenticates. In first-party misuse the real cardholder authenticated successfully, so there is nothing to shift.
Device and identity signals do not help.
Everything about the transaction is legitimate, because it was.
The win rates are bad.
The overall merchant win rate on contested chargebacks runs around 41%, with US-specific estimates near 54%. For disputes coded as true fraud it drops to roughly 9%, and a large share of first-party disputes get filed under fraud codes.
The all-in cost exceeds the transaction.
LexisNexis research puts the total at $5.13 for every $1 lost to chargebacks once fees, staff time, and lost goods are counted. On a $220 pair of seats, the real cost of losing the dispute is well over $1,000.
Then the compliance layer. Under Visa's Acquirer Monitoring Program, the merchant excessive threshold is now 1.5%, and these disputes count toward it regardless of whether the underlying claim was honest.
What does reduce it?
Real levers exist. They are just smaller than the problem.
- Recognizable descriptors. Include the event name or your consumer-facing brand. This alone collapses the confusion category.
- Pre-event reminders. A message a week out naming the event, seats, and charge amount reconnects the purchase to the memory.
- A refund path faster than a dispute. If disputing is easier than asking you, buyers will dispute. Make yours the path of least resistance.
- Network evidence programs. Visa's Compelling Evidence 3.0 and equivalent Mastercard programs let merchants demonstrate prior undisputed behavior from the same cardholder, which reclassifies some disputes before they escalate.
- Prevention alerts. Alert networks resolve disputes pre-chargeback at roughly $20 to $30 each, against $110 to $450 for a dispute that reaches the chargeback stage.
Run all five and you will move the number. You will not eliminate the category, because a portion of your buyers will always dispute purchases they made and received.
Who ends up paying?
By default, the platform. That is the part worth stating plainly.
For most event businesses, first-party disputes are absorbed as a cost of doing business, sitting as an unpredictable line in the P&L that spikes seasonally and gets explained to the board each quarter. Some platforms push it to sellers by holding proceeds until the dispute window closes, which converts a finance problem into a supply problem.
There is a third option, which is to move the liability off the platform entirely.
How Coinflow handles first-party dispute risk
Every tactic above is worth running, and we would tell any event platform to run them. But there is a floor beneath which prevention cannot go, because the buyer authorized the purchase, received the ticket, and disputed anyway. No descriptor fixes that.
Coinflow's approach is to take that loss off your books.
Chargeback indemnification means dispute losses are covered rather than absorbed, which turns a volatile seasonal line item into a known cost of processing. Fraud tooling and dispute handling live inside the same stack as acceptance and settlement, so there is no third vendor and no fourth reconciliation feed. And because indemnified disputes are not eroding your margin, the reason to hold seller payouts until after the event weakens considerably.
Platforms in high-dispute categories tend to describe the change the same way. Disputes stop being an unpredictable margin hit and become a managed variable.
If first-party disputes are the line you cannot forecast, talk to our team about what indemnification would change.
Disputes you cannot prevent, off your books
Indemnified chargeback coverage for delayed-delivery and live event categories.
Talk to our team →Frequently asked questions
Is friendly fraud a crime?
Deliberately disputing a legitimate charge to keep goods or services is fraud in most jurisdictions, but prosecution is vanishingly rare and the amounts are too small to pursue individually. In practice it is handled as a commercial problem rather than a criminal one, which is precisely why volumes keep rising. Framing matters for policy design: most first-party disputes come from confusion or process avoidance rather than intent.
How do I tell friendly fraud apart from real fraud?
Look at the signals around the transaction rather than the reason code on the dispute. Matching device and IP history, a delivered and accepted ticket transfer, prior undisputed purchases on the same card, and event attendance data all point toward first-party misuse. That evidence is also what network programs like Compelling Evidence 3.0 are designed to accept.
Do prevention alerts stop friendly fraud?
They intercept disputes before they become formal chargebacks, which protects your monitoring ratio and costs far less than losing a representment. What they do not do is prevent the loss, since resolving an alert usually means refunding the customer. Treat them as ratio protection and cost containment rather than revenue protection.
This content is for informational purposes only and does not constitute financial, legal, or investment advice.
