Ticket refund protection is an optional add-on your attendees can buy at checkout that lets them claim their money back from an insurer if something stops them attending. The key thing to know up front: the attendee pays for it, not you, and if a claim is approved the insurer pays the refund while you keep the ticket revenue. Whether it is worth switching on depends on your event, your refund policy and how much friction you want at the point of sale. Here is how ticket refund protection actually works, who pays, and when it earns its place at checkout.
What is ticket refund protection?
Ticket refund protection (sometimes called ticket insurance or refundable tickets) is a small optional fee, usually shown as a tick box during checkout, that covers the buyer for specific reasons they might miss your event. If they later cannot attend for a covered reason, they claim directly from the protection provider and get their money back. It is underwritten by third parties, not by the ticketing platform: the big names are XCover, Booking Protect and Protecht, and several platforms plug one of them in behind their own branding.
Think of it as the "add insurance?" prompt you see when buying flights or concert tickets. It is a genuine insurance product with terms and exclusions, not a goodwill gesture from the organiser. That distinction matters, because it changes who is on the hook when a refund is due.
Who actually pays for ticket refund protection?
The buyer pays. Refund protection is buyer-funded and opt-in: it appears as an extra line at checkout, the attendee chooses whether to add it, and the fee sits on top of the ticket price. For the organiser it is meant to be cost-neutral. You keep your ticket revenue whether or not a buyer opts in, and if a covered claim succeeds the insurer pays the refund, not you.
That is the pitch, and it is largely accurate. The nuance is the fee size, because a buyer-funded add-on still shapes how expensive your checkout feels. On Eventbrite the refund protection option is priced at around 6.5% of the order value, while some platforms running XCover calculate it at roughly 8% of the ticket cost. On a £60 ticket that is another £4 to £5 the buyer sees before they reach the pay button.
| Question | How refund protection works |
|---|---|
| Who pays the fee? | The attendee, as an optional add-on at checkout |
| Is it compulsory? | No, it is opt-in and can be declined |
| Who issues the refund? | The insurer (XCover, Booking Protect, Protecht), not the organiser |
| Do you keep your revenue? | Yes, your ticket income is unaffected by a claim |
| Typical fee | Around 6.5% to 8% of the order value |
| When can it be added? | Only at the time of booking, never retrospectively |
What ticket refund protection covers (and what it does not)
Coverage is built around unforeseen personal circumstances, not buyer's remorse. A typical policy pays out when the buyer or an immediate family member falls ill or is injured, when a public authority issues a travel warning, or when emergency services need the buyer at home shortly before the event. Providers publish their own lists, so the exact wording varies.
What it usually does not cover is just as important to understand: changing your mind, double-booking your diary, forgetting the date, or the event simply not living up to expectations. If the organiser cancels the event, that is a different matter entirely and is handled by your own refund policy, not the buyer's protection add-on. Refund protection is there for the attendee who genuinely cannot make it, not for anyone who would rather not.
Claims go straight to the provider. The attendee files with the insurer, the insurer assesses it, and if approved the insurer pays. You, the organiser, are not asked to adjudicate whether someone's excuse is good enough, which is quietly one of the better features for anyone who has ever had to referee a "my cat was unwell" refund request.
Refund protection does not make refunds disappear. It just moves who pays for them off your plate and onto an insurer the buyer chose to use.
Is ticket refund protection worth offering?
Honestly, it depends, and anyone who tells you it is a no-brainer is selling something. Here is the balanced version.
The case for switching it on: it can lift buyer confidence for higher-value or further-in-advance tickets, where the fear of losing money is a real reason people hesitate. For a £120 gala seat booked four months out, a £6 safety net can be the nudge that closes the sale. It also deflects refund admin away from your inbox, because covered buyers claim from the insurer instead of emailing you.
The case against: it adds a line to your checkout and a few percent to the total the buyer sees, which is the opposite of what you want when you are trying to reduce cart abandonment. For low-priced tickets, cheap community events or anything with a generous refund policy already in place, the add-on can feel like clutter that slows people down for little gain. And because it is insurance, some attendees will resent being upsold at the very moment they are trying to pay.
A sensible rule of thumb: the higher the ticket price and the longer the lead time, the more refund protection tends to earn its place. For cheap, near-term or free events, it is usually more friction than it is worth.
Refund protection or a flexible refund policy?
It helps to see refund protection and your own refund policy as two separate levers, because organisers often confuse them. Your refund policy is the promise you make: full refund up to 14 days before, 50% after that, nothing in the final week, whatever you choose. Refund protection is a product the buyer purchases to cover the situations your policy does not, usually the personal emergencies that stop them attending a strictly non-refundable ticket.
The two can happily coexist. A generous refund policy reduces the need for protection and tends to lift conversion on its own, because buyers feel safe committing. A strict policy paired with an optional protection add-on lets you hold firm on refunds while still giving nervous buyers a way to feel covered. What you want to avoid is a strict policy with no safety valve at all, because that is where refund disputes, chargebacks and grumpy reviews breed. Decide your policy first, then ask whether protection fills a gap your policy leaves open. If your policy is already flexible and your tickets are cheap, protection may simply be answering a question nobody was asking.
One more practical point: refund protection can quietly reduce chargebacks. A buyer who genuinely cannot attend and has no way to recover their money is exactly the person who calls their bank and disputes the charge. Give them a legitimate route to a refund from an insurer, and that pressure eases. It is not a cure for chargebacks, and it will not help against outright fraud, but for the honest-but-stuck attendee it turns a potential dispute into a claim someone else pays. That alone can justify offering it on higher-value tickets where a single chargeback stings.
The better fix: give people fewer reasons to want a refund
Refund protection treats the symptom. The cause is usually something you control. Clear joining details, honest event descriptions, easy self-service changes and a sane refund window all cut the number of people reaching for a refund in the first place. So does letting attendees fix their own mistakes: someone who can swap to a later session or transfer their ticket to a colleague does not need to cancel and claim at all.
The other half of the equation is what your platform does with the money in between. Some ticketing tools hold your funds and process refunds through their own account, which is where refunds get slow and awkward. On a flat-fee platform like eventcloud, payments land in your own Stripe account and you keep unlimited events and tickets for a predictable monthly cost, so a refund is just a refund rather than a fight to get your own money back. If you are weighing up the per-ticket cost of your current setup against a flat fee, our Eventbrite comparison runs the maths.
Refund protection is a useful tool for the right event. Just make sure you are offering it because it genuinely helps your attendees, not because it papers over a checkout or a refund process that could simply be better. Want to see what a cleaner setup looks like? Take a look at eventcloud pricing.
