Ticket buyers who dispute after the event
Why a ticket buyer can dispute a card payment months after paying, how postponements affect it, and what evidence an organiser should keep to answer.
By Achekam · · 5 min read · For Events businesses in South Africa, Nigeria, Kenya
An early-bird ticket for a festival sells in February. The festival happens in October. In January the following year, the organiser's payment provider reports a dispute: the buyer's bank says the cardholder does not recognise the charge, or did not receive what was paid for. The festival accounts were closed months ago, the event team has moved on, and someone now has to prove that this person bought a ticket and that the festival took place.
Stripe singles out event ticketing for this, and the reason is simple: organisers are paid long before they deliver. This article explains how the dispute window works for future events, what changes when an event moves, and what to keep so a dispute can be answered properly.
The window starts on the event date
Stripe explains that card networks typically allow cardholders to initiate disputes within 120 days of the original payment. It adds a qualification that matters to every organiser: when a customer pays for a future event or service, the dispute window generally starts on the event date, not the payment date. Stripe notes that travel and event ticketing are prone to longer intervals between purchase and dispute.
So the February ticket in the example is not safe from dispute in June, when 120 days from payment have passed. The clock, broadly speaking, starts in October when the festival takes place. Stripe's explanation of how disputes work covers the full lifecycle, from inquiries to formal chargebacks, evidence deadlines and how funds and fees move at each stage. Check your own payment provider's terms as well, since rules vary by card network and provider.
For the organiser, the practical consequence is that records for an event must be kept well beyond the event itself, not archived when the final supplier is paid. Selling well ahead of an event raises other questions too, covered in presales before the event.
Postponements and changed dates
Postponement is one place a dispute can begin. A buyer paid for a date that no longer exists, and may not be able to attend the new one.
Visa advises that if delivery of a purchase will be delayed, the merchant should inform the cardholder and give the updated delivery or service date, and should request the cardholder's acknowledgement once the purchase is delivered or the service completed.
Turned into an organiser's routine:
- Tell every ticket holder in writing as soon as the new date is confirmed, with the new date, venue and what they need to do.
- Offer the choices your terms allow, such as transferring the ticket to the new date or requesting a refund, with a deadline.
- Keep the message and a record of who it went to.
- After the event, ask attendees to confirm attendance, for example through a post-event survey or a check-in record, so you can show the service was delivered.
Where the event is cancelled outright, the question becomes refunds rather than disputes, and cancelled event refunds deals with that.
Evidence: terms, attendance and communications
When a dispute arrives, the issuing bank wants to see that the buyer agreed to clear terms and received what they paid for. Flutterwave advises merchants to accept a chargeback where the customer did not get the expected value from the payment, and to decline it using gathered evidence where value was provided.
That gives a useful test. If the buyer genuinely did not get what they paid for, contesting wastes effort and may be unfair. If they did, the organiser needs evidence, typically:
- Terms of sale as they stood when the ticket was bought, including refund and transfer rules.
- Proof of purchase: the order, the payment record and the ticket issued.
- Communications: confirmation e-mails, joining instructions and any postponement notices.
- Proof of attendance: check-in or scanning records, wristband issue, or a badge collection list.
- For corporate bookings: the signed booking form or agreement.
Answering on time
Stripe warns that failing to respond to a dispute inquiry can signal to the issuer an implicit acceptance of the claim and escalate it to a formal, probably unwinnable chargeback.
Disputes arrive as notifications from the payment provider, sometimes to an inbox nobody watches closely once the event is over. Name one person who receives and answers disputes for every event, with a backup, and keep their access to the provider's dashboard current. Typical timelines for the stages of a dispute are covered in the chargeback dispute timeline.
Filing the evidence in Document Centre
The evidence is only useful if someone can find it months later. Achekam helps keep it together and connected to the money.
The payment record. When a buyer pays an invoice through a gateway, a verified payment is recorded as a receipt against the invoice. It debits that gateway's clearing account and credits trade receivables, and the invoice shows as paid or part-paid. The amount is checked against what the link asked for, and a repeated notification never pays twice. That gives the organiser a clear record, in its own books, of what was paid and when.
Signed terms for corporate bookings. Any document can be sent for electronic signature with signature and initials fields placed on it, signers in order or all at once, an expiry and reminders. The signed PDF and a completion certificate are filed back into Documents. A company booking a block of tickets or a hospitality package can sign the booking terms this way.
One folder per event. Document Centre is a folder-based store where you upload files or whole folders, then preview, download, rename, move, tag, archive and search them, and a new version keeps the earlier ones. Create a folder for each event, and file in it:
- the terms of sale as published, saved on the day sales opened and again whenever they changed;
- the postponement notices and the lists they went to;
- the check-in export after the event;
- signed corporate booking forms.
Archive the folder after the event rather than deleting it, so it is still searchable when a dispute arrives.
Before the next event goes on sale, create its folder, save the terms of sale into it, and decide who will answer disputes until well after the event date.
General guidance only, not advice on your own circumstances. Tax and payroll rules change: check the current position with the authority or your adviser.
