Learning how to handle event refunds well comes down to two things: giving money back without watching the platform keep its cut, and doing it in a way that leaves the attendee wanting to come back. Get the policy clear, refund fast, and keep the seat filled where you can, and a refund request stops being a crisis and becomes a two minute admin job. This guide covers the refund policy that actually protects you, the fee traps hiding in the small print, and the alternatives to a straight refund that keep revenue in your account.
First, the reassuring bit: most refund requests are not people demanding their money back out of spite. They double booked, a child got ill, the train was cancelled, work exploded. Treat them like humans, make the process painless, and a chunk of them will rebook or transfer rather than vanish forever.
Start with a refund policy a stressed person can read in 30 seconds
The single biggest cause of refund drama is a policy nobody can find or understand. The best event refund policy is one a flustered buyer can read in half a minute and immediately know where they stand. Lead with the question everyone actually asks, "Can I get a refund?", and answer it in the first line. Then list your scenarios as short, scannable statements instead of a wall of legalese.
A few rules that keep you out of trouble, drawn from refund policy best practice:
Name your cutoff date explicitly. "Full refund up to 14 days before the event" beats "refunds available in advance" every time. Vague dates cause disputes.
Put the timeline in bold. People want to know both the deadline to request and how long the money takes to land (card refunds typically show up in 5 to 10 working days).
Show the policy everywhere. On the ticket page, in the confirmation email, and on the ticket itself. If it is only buried in your terms, expect "I never agreed to that".
Set a response standard. Aiming to action refund requests within one working day turns an angry email into a grateful one.
A clear refund policy is not you being generous. It is you deciding the terms in calm daylight instead of arguing them at 11pm the night before doors open.
The fee trap: who keeps the fee when you hit refund
Here is the part that quietly costs organisers money. On percentage based platforms, the booking fee is usually not returned when you issue a refund, which means the money can leave your account even though the platform keeps its cut.
On Eventbrite, ticketing fees are not refunded by default. The attendee gets their money back minus the fees, unless you choose to cover those fees yourself out of your payout to give a genuine full refund. Eventbrite only credits the fees back to you automatically in specific cases: the event is cancelled or postponed, a duplicate order, or a COVID related reason, and even then you have to contact them with the receipt. For a normal "sorry, I cannot make it" refund on a paid ticket, someone eats the fee, and it is either you or the attendee. On Eventbrite in the US that fee is 3.7% plus $1.79 per ticket plus 2.9% processing, so on a run of refunds it adds up fast.
Humanitix works similarly: passed on booking fees are not refundable by default, so buyers get the face value back minus the fee, though any fee the organiser absorbed is returned. And on every platform, the card processing fee (roughly 2.9% plus $0.30) is the one nobody gets back, because the payment processor has already done the work.
The fee that does not come back when you refund. Every percentage platform has one. · credit: Braňo / Unsplash
What the fee models actually do on a refund
| Platform | Booking fee on a standard refund | Processing fee |
|---|---|---|
| Eventbrite (US) | Not refunded by default; organiser can opt to cover it | Not refunded |
| Humanitix (US) | Passed on fee not refunded; absorbed fee returned | Not refunded |
| Ticket Tailor | Flat per ticket fee, small; own processor handles the refund | Not refunded |
| Flat fee / own Stripe (e.g. eventcloud) | No per ticket platform fee to lose | Not refunded (Stripe standard) |
The pattern is simple. The more your platform charges per ticket, the more a wave of refunds hurts, because that per ticket fee is the bit most likely to stay behind. On a flat fee model where the platform charges $0 per ticket and you run payments through your own Stripe account, there is no per ticket service fee to forfeit in the first place. You still lose the processing fee, because that is the card networks, not the platform, but the platform is not taking a second bite. It will not make refunds free, nothing does, but it stops turning every cancellation into a double cost.
The alternatives that keep the seat (and the money)
A refund is the nuclear option. Before you send the cash back, there are gentler moves that keep the attendee happy and the revenue in your account. Offer these first, clearly, in the same breath as the refund:
Ticket transfer or name change. The single most underrated tool. A ticket that changes hands is a seat that still gets used, an attendee who still shows up, and zero money leaving your account. Make it self service and a good share of "I cannot come" turns into "my colleague will come instead".
Credit towards a future event. If you run a series, a credit note keeps the relationship and the revenue. Many people prefer this to a refund because it feels like they lose nothing.
Move to another date. For multi date runs, swapping someone onto a later session costs you nothing and solves their actual problem.
Partial refund with a clear rule. A common structure is refunding a percentage (say 80%) excluding fees up to a cutoff, then nothing after. For multi day events, a pro rata refund when one day is missed is fair and easy to explain.
The trick is to present these as the default and the full refund as the fallback, not the other way round. Most people just want the problem solved. If a transfer solves it, they will take the transfer.
Handle the messy cases before they happen
Three scenarios cause most of the pain, so decide your line now:
The no-show who wants a refund afterwards. Your policy should state plainly that refunds are not available after the event or after the request cutoff. This is exactly why the cutoff date needs to be bold and visible. No ambiguity, no case by case pleading.
You cancel the event. This is the one where you refund in full, fees and all, and do it fast. It is not the attendee's fault, and a slow or partial refund on a cancelled event is how you torch trust permanently. Good news if you are on a platform that credits your fees back on cancellation: this is the case that qualifies. Communicate the cancellation and the refund timeline in the same message.
The chargeback. If someone skips your refund process and disputes the charge with their bank instead, you can lose the money and the fee and pay a dispute cost on top. The best defence is a fast, obvious refund route so nobody feels forced to go to their bank. Keep records of your policy and their agreement to it.
Build the process once, run it on autopilot
Handling refunds without losing money or goodwill is mostly a systems job, not a customer service heroics job. The organisers who stay calm have set this up in advance:
| Ingredient | Why it matters |
|---|---|
| A clear, visible policy with a named cutoff | Ends 90% of disputes before they start |
| Self service transfers and name changes | Converts refund requests into filled seats |
| A flat or low per ticket fee model | Limits what you forfeit when you do refund |
| Your own payment account | You control the refund, funds are not held by a middleman |
| A one working day response habit | Turns frustration into loyalty |
An honest caveat: if you run a single small free event a year, none of this needs a system. Free tickets carry no fee to lose, and a quick email handles the odd cancellation. This matters when money changes hands, when you run events regularly, and when a wave of refunds could genuinely dent your cash flow.
If you want to compare how the fee models stack up when refunds are on the table, our Eventbrite comparison lays out where the per ticket costs bite, and our guide to cutting no-shows covers the transfers and reminders that stop refunds happening in the first place. When you are ready to see refunds handled without a platform taking a second cut, take a look at how eventcloud handles ticketing and payments.
