The short answer
- Event tickets bought online have no 14-day cooling-off period in the UK, because the Consumer Contracts Regulations 2013 exclude leisure services booked for a specific date.
- When an event is cancelled, ticket buyers are generally entitled to their money back, so ticketing software should be able to refund every order for an event in one action.
- Under the Consumer Rights Act 2015, a ticket resold online must come with its face value, its seat or standing area where relevant and any restriction on who can use it.
Ticketing software has to decide what happens to money and tickets when plans change: when an event is cancelled or postponed, when a buyer asks for a refund, when a ticket changes hands and when a payment is disputed. A refund policy is the set of rules an organiser publishes about when money is returned, and the software’s job is to apply those rules consistently and within UK consumer law. This is a planning guide and does not replace legal advice.
There is no cooling-off period for event tickets
Most things bought online in the UK come with a 14-day right to cancel under the Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013. Event tickets usually do not. The regulations exclude services related to leisure activities where the contract provides for a specific date or period, which covers most concerts, conferences, festivals and matches.
So an organiser can lawfully refuse a refund when a buyer simply changes their mind. The software should still let organisers offer refunds up to a set date, transfers or official resale, because a buyer with a legitimate way out has less reason to raise a chargeback.
The terms themselves must be fair and transparent under Part 2 of the Consumer Rights Act 2015. A term that let an organiser keep the money after cancelling the event is likely to be challenged as unfair. Show the refund policy before payment and store the version each buyer accepted with their order. Our guide to event registration and UK GDPR covers the personal data side of the same checkout.
Refund and transfer scenarios at a glance
| Situation | Usual position | What the software should do |
|---|---|---|
| Buyer changes their mind | No legal right to cancel; the organiser’s policy applies | Apply the published policy and offer a transfer or resale if allowed |
| Event cancelled | Buyer is generally entitled to a refund | Refund every order to the original payment method, showing progress and failures |
| Event postponed | Tickets usually stay valid, with refunds for those who cannot attend | Move the date, email holders and collect refund requests up to a deadline |
| Significant change, such as a new venue | Depends on the terms and how significant the change is; take advice | Let the organiser open a refund window for one event |
| Ticket passed to a friend | Set by the organiser’s terms | Cancel the old barcode, issue a new one and log the transfer |
| Ticket resold online | Consumer Rights Act 2015 information rules apply to the listing | Show face value, seat details and restrictions, then reissue the ticket |
Cancellations and postponements
When an organiser cancels an event, the buyer is generally entitled to their money back, so build for that as the default. Whether booking and delivery fees are refunded as well depends on the circumstances, so take advice and state the position in the terms. Since April 2025, the Digital Markets, Competition and Consumers Act 2024 has required mandatory fees, such as booking fees, to be included in the headline price. Record the price breakdown for each ticket as well as the order total, so that any refund of fees can be worked out from the record.
A postponement is different, because the event will still happen on another date. Common practice is to keep tickets valid for the new date and offer refunds to anyone who cannot attend. Build it as a single guided action for the organiser:
- Change the event date and keep every existing ticket valid.
- Email every ticket holder with the new date and a deadline for requesting a refund.
- Give each order a one-click refund request link that needs no login.
- Process approved refunds in batches through the payment provider, with a record of each one.
- After the deadline, close requests and report what was refunded.
A cancellation runs the same machinery without the request step. A large event can mean thousands of refunds at once, so run them as a queue that can pause, retry and report. The load looks a lot like an on-sale, which we cover in event software on sale day.
Refunds through the payment provider
Card refunds go back to the card that paid. The money leaves the organiser’s balance straight away but can take several working days to reach the buyer, so say so in the confirmation email. Settle these questions with your payment provider before the first event:
- Whether the provider returns its processing fee on a refund. Some do not, in which case every full refund costs the organiser money.
- What happens when the organiser’s balance cannot cover a batch of refunds.
- Whether the provider limits how long after a payment a refund can be made.
Name changes and transfers
A transfer moves a ticket from the buyer to someone else. A name change edits the name on a named ticket. Organisers restrict both to discourage touting, so the software should let them set the rules for each event.
Build transfers so that the original barcode is cancelled and a new one is issued to the recipient. If both barcodes stay valid, the same ticket can be used twice, and whoever reaches the gate first gets in. Record who transferred to whom and when, allow a cap on transfers per ticket, and send the new holder their own ticket and wallet pass. For named tickets, decide whether name changes are free, charged or closed after a set date, and show that rule at the point of purchase.
Some platforms use barcodes that rotate every few seconds inside an app, which stops screenshots being sold on. The cost is that every attendee then needs the app and a charged phone at the door.
Resale and the Consumer Rights Act 2015
The Consumer Rights Act 2015 has a chapter on secondary ticketing, meaning tickets resold through an online platform. When a ticket is resold that way, the buyer must be given:
- the information needed to identify the seat or standing area, such as the block, row and seat number, where that applies;
- any restriction on who can use the ticket, such as a minimum age;
- the face value of the ticket;
- the unique ticket number, where the organiser issued one.
Further disclosures apply where the seller is connected to the platform or to the event organiser, and general consumer law stops business sellers presenting themselves as private individuals. The Act also limits an organiser’s power to cancel a ticket just because it was resold. That is only possible where the original terms said so and the term was fair.
If you build a resale or fan-to-fan exchange, the cleanest pattern is to resell the returned ticket through the organiser’s own system, cancel the old barcode and issue a new one. Using software to get round an event’s purchase limit in order to resell at a profit is a criminal offence under the Breaching of Limits on Ticket Sales Regulations 2018, so enforce limits per person and per card as well as per order. The government has also consulted on capping resale prices, so check the current rules before designing a resale feature.
Fraud and chargebacks
A chargeback happens when a cardholder asks their bank to reverse a payment. The payment provider takes the money back, usually adds a dispute fee and gives the organiser a window to submit evidence. Ticketing sees both genuine fraud with stolen card details and disputes from real buyers about tickets they could have used. Software can help with both.
- Use Strong Customer Authentication through 3D Secure. For an authenticated payment, liability for a fraud chargeback generally moves to the card issuer.
- Record scan data: the time and gate at which each ticket was used.
- Keep evidence that the buyer accepted the terms, received the tickets and was offered a refund route.
- Watch for card testing, such as many small purchases or failed attempts from one device in a short time.
- Use a clear statement descriptor, so the charge on a bank statement names the event.
Buyers who pay by credit card also have rights under section 75 of the Consumer Credit Act 1974 where a single item costs more than £100 and not more than £30,000, which lets them claim against the card issuer if the event does not go ahead. A quick, visible refund process for cancelled events keeps those claims to a minimum.
Questions people ask
Do UK event tickets have a 14-day cooling-off period?
No. The Consumer Contracts Regulations 2013 exclude leisure services booked for a specific date or period, which covers most event tickets. Organisers can still choose to offer refunds, transfers or resale, and the terms they use must be fair under the Consumer Rights Act 2015.
Does an organiser have to refund tickets if an event is cancelled?
Generally, yes, because the service the buyer paid for will not be provided. Whether booking fees are refunded too depends on the circumstances and the terms, so take legal advice. Ticketing software should be able to refund every order for a cancelled event in one action.
What information must a resold ticket listing show?
Under the Consumer Rights Act 2015, the buyer must be told the face value, the seat or standing area where relevant, any restriction on who can use the ticket and the unique ticket number where the organiser issued one. Extra disclosures apply where the seller is connected to the platform or the organiser.