What happens when you have to give the money back?

Three different things, one word

“Refund” covers three situations with different causes, different obligations and different amounts of goodwill available. Treating them as one is the first mistake.

The third column is the one nobody writes a policy for, and it is the one that generates the most correspondence, because the attendee has not got what they bought and has also not been told they can have their money back.

The money is already committed

Refund policy is usually written as a customer-service question. It is a cash-flow question. What decides whether you can afford a generous policy is the shape of two curves: money you have collected, and money you can no longer get back.

Most published refund deadlines are set at a round number of weeks that sounds fair. The defensible way to set one is to find the date your caterer's final-numbers deadline falls — that is usually the moment your costs stop being recoverable — and put your refund deadline a few days before it, so a wave of late withdrawals cannot land after you have guaranteed the covers.

A refund policy is a schedule, not a sentence

One line saying “refunds up to 14 days before the event” answers one case out of five. What a working policy names:

Publish it where the ticket is bought, not only in the terms and conditions. A policy the attendee did not see is a policy you will be arguing about, and in a chargeback the question of what was disclosed at the point of sale is precisely what gets examined.

What the law may decide for you

In the EU, distance selling to consumers normally carries a 14-day right of withdrawal — and events are one of the places where it may not apply. Article 16(l) of Directive 2011/83/EU exempts:

“the provision of accommodation other than for residential purpose, transport of goods, car rental services, catering or services related to leisure activities if the contract provides for a specific date or period of performance”

Two conditions have to hold together: the contract fixes a specific date or period, and the service falls in one of those categories. A ticket to a dated event satisfies the first easily. The second is where it stops being obvious, because the operative words are “services related to leisure activities”, and a professional conference is not self-evidently leisure.

Three things narrow it further, and all three are routinely missed:

• It only applies to consumers. A ticket bought by a company for an employee is a B2B contract and this Directive does not govern it at all.
• It is a directive, not a regulation. Each member state implements it in national law, and the details differ.
• The exemption is about the withdrawal right, not about your policy. Nothing stops you offering refunds more generously than the law requires, and most organisers should.

The two mistakes here are symmetrical. Assuming the exemption covers you, so you publish a no-refunds policy that turns out to be unenforceable. Or assuming it does not, so you carry a 14-day liability you never had. Which one you are in depends on your jurisdiction, your audience and your event — ask someone qualified in the countries you sell into, once, and write the answer down. What is certain in the meantime is that your published policy is the document that governs the cases the law does not, which is most of them.

The fee does not come back

Payment providers generally do not return the processing fee on the original transaction when you refund it. Stripe's documentation states it plainly — the fees incurred on the original transaction are not refunded — and most providers work the same way.

So a refunded order is not a neutral event. You return the full ticket price to the attendee and you keep the cost of having taken it. On a €450 ticket with a two-percent fee that is €9 gone per refund, and on a wave of two hundred withdrawals it is the price of a piece of AV equipment.

Two mechanics are worth knowing, and both are the provider's, not the platform's:

• A refund issued very soon after the payment may be processed as a reversal instead. The original charge disappears from the cardholder's statement rather than appearing alongside a credit, and no fee is withheld. Same-day corrections are therefore materially cheaper than corrections a week later.
• If you expect a lot of refunds, authorise and capture separately. Money that has been authorised but not captured can be released without a refund at all. This is a real lever for waitlists and provisional registrations, and it is decided when the integration is built rather than when the refunds start.

Refunds go back the way they came

A card refund can only return to the card that was charged. Not a different card, not a bank transfer, not a credit note. Nor is the money conjured: refunds are paid from your available balance with the provider, and if that balance is short — because the payout already ran — card refunds sit pending until it covers them, refunds on some methods fail outright, and in some regions the provider will debit your bank account to recover the difference.

Both constraints point at the same setup decision: the entity that took the payment is the only one that can return it, so it has to be the entity that owes the refund. Where that is decided — before sales open, not after — is the subject of the companion guide to this one.

One more, for the attendee-facing side: a refund typically shows on the cardholder's statement several business days after you issue it, and if it fails at their bank the funds can take weeks to come back to you. Tell them the range when you confirm the refund. Most “where is my money” emails are sent during a wait nobody warned them about.

When the event moves instead of stopping

A postponement is treated as good news internally and as a broken promise externally. The attendee bought a date. Some of them cannot make the new one, and until you say otherwise they do not know whether they have lost their money.

What has to be decided in the first announcement, not the third:

• Tickets carry to the new date automatically — say so first, because it is what most people want to hear.
• A refund is available on request, and until when. A stated window is what stops a slow trickle of disputes over the following months.
• What happens to add-ons and accommodation, which are on the supplier's schedule, not yours.
• Who to write to, with a named route rather than a general inbox.

The offer costs you the refunds you were always going to owe. Announcing without it costs you those refunds as chargebacks instead, which is the same money with a fee attached and a mark on your account.

A chargeback is not a refund

A refund is you returning money. A chargeback is the cardholder's bank taking it back and asking you to justify the sale. The difference matters in three ways: you pay a fee whether or not you win, the outcome is decided by evidence rather than by your policy, and a high enough rate puts your payment account itself at risk.

The evidence that decides them is generated at the point of sale, not at the point of dispute: what the statement descriptor said, what the attendee agreed to, whether the refund policy was visible on the page where they paid, and whether the event happened as described. All of that is set months before anyone disputes anything.

One sequencing trap worth naming: if a dispute is opened while a refund of yours is still pending, both can complete and the cardholder is credited twice. The provider's guidance in that situation is to respond to the dispute rather than to keep refunding. Check before refunding a payment that has been disputed — the interface will not always stop you.

What actually goes wrong

These follow from how the mechanics work rather than from bad luck, which is why each is preventable in setup and expensive afterwards:

• The refund deadline falls after the catering guarantee. Withdrawals land in the window where you are already paying for those covers, and every one of them is a full refund out of money that is no longer there.
• A cancellation is announced without a refund instruction. The gap between “the event is cancelled” and “here is how you get your money back” is filled by disputes, and disputes cost more than the refunds would have.
• Refund obligations outlive the payout. The balance was paid out weeks ago, so refunds come from working capital — or sit pending until the account is topped up.
• No-shows are not addressed in the policy. Silence is read as a right, and the argument happens after the event, when there is nothing left to negotiate with.
• Add-ons are refunded on the ticket's schedule. The accommodation was non-refundable from a date the ticket policy never mentioned, and the difference comes out of your budget.
• A disputed payment is refunded anyway. The cardholder is credited twice, and recovering the second credit is a manual argument with someone who has already got their money.

Where software actually helps

Four places, and they are the ones to test a system against before you need any of them — ours included:

• Partial refunds, not just full ones. Whether you can return the ticket and keep a non-refundable add-on, in one action, with the reporting following it.
• Refunds issued where the payment was taken. Whether the refund goes back through the original method from the account that charged it, without anyone moving money between entities by hand.
• Name changes as a first-class action. Whether a seat can be transferred to a colleague without cancelling and rebuying — the concession that costs you nothing and saves the sale.
• Reporting that nets refunds off revenue. Whether the revenue figure you are shown is after refunds and after the fees on them, or whether it is gross and you find out later.

None of that writes the policy. The deadline, the tiers and what happens when a date moves are decisions about your own costs and your own audience — which is why they are worth making against your caterer's calendar rather than against a number that sounded fair.