The emails started before the venue had finished updating its website. You announced the new date at 9:14, apologized, promised every ticket would be honored. By lunch there were eleven disputes in your Stripe dashboard, and every one of them came from someone who had, three weeks earlier, typed 'can't wait' into the order notes. They aren't lying to their bank. They aren't trying to steal from you. They are grieving a Saturday they had already lived in their heads, and the dispute form is the only place that lets them say so.

The ticket was never the product

In 1986, Daniel Kahneman, Jack Knetsch and Richard Thaler published a study of what ordinary people consider fair in business. The pattern they found is called dual entitlement: customers believe they are entitled to the terms of a reference transaction, the deal as they first understood it, and firms are entitled to their reference profit. A change that pushes the customer below that reference reads as a loss the firm has inflicted, even when the firm had no choice. A hardware store raising the price of snow shovels after a blizzard feels like theft. A merchant passing along a cost increase feels merely unfortunate.

A concert ticket is a reference transaction with a date baked into it. The customer didn't buy admission to a room. They bought the Saturday in June, the babysitter already booked, the friend flying in. Move the date and you haven't modified the service. In their accounting, you've taken the thing they paid for and handed back something smaller. 'Your ticket is still valid' is true, and it lands as an insult, because it asks them to accept a loss as if it were nothing.

This matters because the reviewer at the cardholder's bank isn't deciding who is nicer. They are deciding a narrow question, and the question changes completely depending on which of three things actually happened.

Cancelled, postponed, or missed: three different disputes

Cancelled. If you cancelled the event and never delivered it, the dispute will be coded as services not provided, Visa reason code 13.1 or its Mastercard equivalent. You will lose, and you should expect to. A no-refund clause does not matter here. The card networks' guidance during the mass cancellations of 2020 said essentially this: a merchant that cancels a service and offers only a credit cannot hide behind its refund policy unless the cardholder agreed to take the credit. Fighting these burns the dispute fee on top of the refund and nudges your ratio upward. The right answer is to refund before the dispute is filed, and to accept the ones that arrive anyway.

Postponed. If you rescheduled and the customer's ticket was honoured at the new date, the question becomes whether you delivered what was agreed. The policy the customer accepted at checkout now matters, as does whether the new date fell within the window that policy describes and whether you gave the customer a real choice. A reschedule where the customer could attend, could transfer, or could request a refund within a stated window is a defensible dispute. A reschedule announced after the fact with no options is a cancellation wearing a different name.

Missed. If the event happened, on the original date or the rescheduled one, and the customer didn't come, this is a no-show, and your terms govern, provided you can prove they saw them. The dispute often arrives weeks later, framed as 'not received', and the reviewer needs to see that the service was available on the date and the customer simply did not use it.

Most organizers lose the postponed case not because the rules are against them but because they answer it like a cancellation, apologizing and offering vouchers, or like a no-show, pointing at a policy. The postponed case is its own thing, and it has to be argued as one.

The voucher trap

The instinct after a reschedule is to offer credit: keep your ticket, or take a voucher for a future show. It's generous, and for a thin-margin organizer it is often the only thing that is affordable. But a voucher only protects you from a dispute if the cardholder accepted it. A voucher you emailed to everyone is an offer. A voucher the customer clicked to redeem, or replied 'yes, I'll take the credit' to, is an agreement, and an agreement is evidence.

This is where dual entitlement helps instead of hurts. People who feel they've suffered a loss are far more willing to accept a substitute when they choose it than when it is assigned to them. Offer the refund alongside the credit, make both a single click, give a deadline, and record the choice. The customers who take the credit are now customers who agreed. The ones who take the refund are no longer disputes. The ones who do nothing are the only population left, and for them you hold a timestamped record that they were offered both.

The evidence that wins a postponed-event dispute

A reviewer reads a rescheduled-event response looking for four things, in this order.

Proof of the original agreement. The checkout page as it looked when they bought, with the refund and reschedule terms visible before the pay button, not buried in a footer link. A screenshot with the date in the corner beats a PDF of your current terms.

Proof of notice. The reschedule email with its send timestamp and, if your platform records it, the open or click. Include the message itself, not a summary. Reviewers are suspicious of merchants who paraphrase.

Proof the service was available. The event happened on the new date. A ticket-scan log showing the customer's barcode as valid and unscanned proves both that you delivered and that they chose not to come. If they did scan in, that single line usually ends the dispute.

Proof of the options you offered, and the customer's response or silence. The refund window, the credit option, the deadline, and the record that this customer chose neither.

Four exhibits, one page of narrative, in that order. The narrative should say, in plain terms: the customer agreed to these terms, we rescheduled within them, we notified the customer on this date, we offered a refund until this date, the event took place, the customer's ticket was valid and unused. Leave out how hard the year has been. The reviewer is not permitted to care.

Your next moves

  • Open your checkout flow today and screenshot the step where the reschedule and refund terms appear, with the date visible. If they only exist as a footer link, move a one-line summary above the pay button before your next on-sale.
  • Write your reschedule email template now, while nothing is on fire. It should contain the new date, a refund link, a credit link, and a deadline, so that every customer's choice becomes a logged event.
  • Confirm your ticketing or scanning tool exports a per-ticket scan log with timestamps, and know where that export lives. Download one after every event and store it next to the order data.
  • Decide, in writing, the window inside which a reschedule is a reschedule and outside which you will refund. Thirty days, ninety days, the same season. Put the number in your terms and treat it as a promise.
  • If you cancel outright, refund everyone before they ask. The disputes you prevent cost nothing. The ones you fight and lose cost the refund plus the fee.

Where Argeback fits

Every one of those exhibits already exists somewhere: the ticketing platform, the email tool, the scan log, the Stripe order. The dispute is lost in the gap between knowing that and assembling it before the deadline, usually in the week after a reschedule when you can least spare the hours. Argeback pulls the dispute in from Stripe, drafts the response around the records you attach, and files it from your phone before the window closes, so the postponed cases you should win are actually fought. If you sell tickets on Stripe, take a look at https://argeback.lumenlabs.works.