logo
    Back to all posts
    Payments

    Chargebacks and Payment Disputes: An Organiser's Guide

    September 12, 2026·7 min read

    Refunds are well understood: the buyer asks, you decide, the money goes back. A chargeback is a different mechanism with a different balance of power, and organisers usually meet their first one without knowing how it works. This guide covers the structure. The specific rules, timeframes and costs that apply to you are set by your acquiring bank and the card schemes, so confirm the particulars with them rather than working from any general article, including this one.

    A chargeback is not a refund

    In a refund, the buyer comes to you and you return the money. In a chargeback, the buyer goes to their card issuer instead and asks for the payment to be reversed. The issuer pulls the funds back, and you find out after it has happened rather than before.

    • The buyer does not need your agreement, and often does not contact you first.
    • The money is taken back from the settlement flow, so it can affect a payout you were expecting.
    • There is usually a fee attached to the reversal itself, charged regardless of who eventually wins.
    • There is a deadline to respond with evidence, and missing it means losing by default.

    Why ticketing attracts them

    Ticketing has a structural exposure most retail does not: a long gap between payment and delivery of the thing bought. Someone pays in September for a December event. In the intervening months they may forget the purchase, fail to recognise the descriptor on their statement, change their mind, or genuinely be the victim of card fraud. Each of those produces the same reversal even though only one is a real dispute.

    • Unrecognised transaction: the buyer does not connect the statement line to a purchase made months ago. This is the most common and the most preventable.
    • Buyer's remorse presented as a service problem: the buyer wants out and the card is the fastest route.
    • Genuine card fraud: the cardholder did not make the purchase at all.
    • Event cancelled or materially changed: the buyer's underlying complaint is real, and the dispute is a symptom of the refund process not having resolved it.

    What gate scan data actually proves

    This is the most useful thing a ticketing platform gives you in a dispute, and it is worth understanding its limits. A scan record shows that a specific ticket was presented and accepted at a specific gate at a specific time. That is strong evidence that the product was delivered and consumed.

    What it does not prove is who was holding it. In a genuine fraud case, the ticket may well have been used, just not by the cardholder. Scan data answers the question was this ticket used, which defeats a did not receive it claim convincingly, but it does not by itself answer did this cardholder authorise the purchase.

    A response is stronger when scan data is combined with the rest of the transaction record: the confirmation email and when it was opened, the delivery address, any account history showing previous purchases, and the terms the buyer accepted at checkout.

    How disputes interact with payout timing

    Settlement and disputes run on different clocks, and that is the source of most of the friction. Payouts are tied to the event lifecycle. Chargebacks can arrive well after an event has finished and been settled, which means a reversal can land against money you have already received and spent.

    The practical implication is to treat a settled payout as provisional rather than final for a period after the event, particularly for high-value or heavily marketed shows. Ask your acquirer how long your exposure window actually runs, because it is longer than most organisers assume.

    Reducing your dispute rate

    • Make the statement descriptor recognisable. A buyer who sees a name they recognise does not call their bank. This single change prevents more disputes than any evidence you could assemble afterwards.
    • Send a confirmation that survives six months in an inbox, with the event name, date and venue in the subject line, so a search finds it.
    • Answer refund requests quickly, even the ones you intend to decline. An unanswered email becomes a chargeback within about a week.
    • Publish your refund and postponement position at the point of sale, not in a document nobody opens. The terms the buyer accepted are part of your evidence.
    • Keep your scan data. It is the strongest single artefact you have, and it exists only if you scanned at the gate rather than checking names on a list.
    • For a cancelled or materially changed event, refund proactively. Disputes cluster where organisers go quiet, and a wave of them is far more expensive than the refunds would have been.

    Where to get the specifics

    Response windows, fee amounts, acceptable evidence formats and the thresholds at which a card scheme takes an interest in your dispute rate are all set outside this platform, by your acquiring bank and the card schemes, and they change. Ask your acquirer directly for the current figures that apply to your merchant account, and treat any general guidance, including this page, as an orientation rather than an authority.

    Ticketing built for the evidence trail

    QR issuing, gate scan records and transaction history, all retained and exportable when you need to respond to a dispute.

    List Your Event

    Ready to sell tickets for your next event?

    List your event on TicketsMinistry and get real-time analytics, secure payments, and phone-based gate scanning from day one.