Industry · Events and ticketing
Event and ticketing chargebacks: cancellations, reschedules and fees
Ticket sellers collect money weeks or months before the event, so disputes follow cancellations, reschedules, fees the buyer didn’t expect and tickets the buyer says never arrived. For an event that hasn’t happened yet, the dispute window runs from the event date, up to 540 days after the sale.
Key takeaways
- The clock starts at the event. Up to 540 days after the sale.
- Cancelled means refund. “All sales final” rarely survives an event that didn’t happen.
- The terms at purchase are the terms. Changing your refund policy later doesn’t bind earlier buyers.
- Show the total price. Late-appearing fees are a dispute trigger and an FTC rule issue.
Why events and ticket sellers get disputed
You sell a promise. The money arrives today, the show happens months from now, and a lot can change in between: the date, the lineup, the venue, the buyer’s plans. Tickets get forwarded, resold and screenshotted. The disputes we see most:
- Event cancelled. No show, no refund.
- Event rescheduled. The new date doesn’t work for the buyer.
- Tickets not received or wouldn’t scan. “I never got them,” or “we were turned away.”
- Fees. The total was higher than the price advertised.
- Fraud and resale. Stolen cards buying resale-ready tickets, or a buyer who attended and disputes anyway.
Which reason codes ticketing sees
The main family is not received: Visa 13.1, Mastercard 4853 (legacy 4855) and Amex C08, for cancelled events and tickets that never arrived. The second is cancelled services: Visa 13.7, Mastercard 4853 and Amex C05, for buyers who cancelled or rejected a new date. Fee complaints come in as incorrect amount (Visa 12.5), and stolen-card purchases as fraud (Visa 10.4, Mastercard 4837).
The insight: the terms the buyer saw are the ones that count
When a show moves, sellers often update their refund policy and point unhappy buyers to the new version. Not so fast. The buyer agreed to the terms shown at checkout on the day they bought. A policy you published later doesn’t bind them, and refusing a refund under the new wording is how a winnable reschedule becomes a lost chargeback.
Keep the version, not just the policy. Know which version of your terms each buyer accepted, and when. That one fact settles most reschedule disputes before they start.
Fees are the other trap. The FTC’s rule on unfair or deceptive fees covers live-event tickets and requires sellers to show the total price, including mandatory fees, more prominently than other pricing. A buyer who first sees the full amount on the last screen is a buyer primed to dispute.
Third-party ticket agencies get a little time when an event is cancelled: Visa makes the bank wait 30 calendar days after the cancellation before filing a not-received dispute, so a prompt refund can head it off.
Deadlines that run long
For tickets to a future event, Visa’s not-received window runs 120 days from the event date, up to 540 days after the purchase. Tickets sold a year ahead can be disputed well after the show. Your response window is still the date on your notice, usually 7 to 21 days.
Dispute Daddy builds this for you
What wins is usually in your ticketing system: the terms version the buyer accepted, the delivery record, and the scan log from the door. Dispute Daddy works from the exports you upload, builds the response around what the buyer claimed, and keeps the due date in view. You review, approve and submit. A flat $99 a month. See pricing.