Knowledge Base / Knowledge Base

Refund management for travel businesses

A practical guide to refund management in travel — why travel refunds are harder than other industries, customer-side discipline, supplier-side recovery, the regulatory floor under PTR/ATOL/EU261, refunds as chargeback prevention, and the audit trail behind every decision.

Why travel refunds are harder than other industries.

// 01 — section

In most industries, a refund is a single decision: the merchant pays the customer back, the books are updated, the conversation ends. In travel, a single refund touches the customer, one or more suppliers, an acquiring bank, an ATOL or trust arrangement and a regulator - often all at the same time, often with different timing on each side.

01

Customer money, supplier obligations

The customer has paid for travel; the operator has paid suppliers for the components. A refund to the customer almost always has to be matched by a recovery from the supplier - and the supplier timeline rarely aligns with the customer deadline.

02

Long lifecycle, late decisions

A booking made twelve months in advance can be refunded at any point in that window. Each refund moment carries different regulatory framing, different supplier exposure and different operational urgency.

03

Refund discipline = chargeback defence

Travel businesses with poor refund discipline produce chargeback waves. Customers who cannot get a refund through the operator go to their card issuer, and the operator pays the cost twice - the refund and the chargeback fees on top.

How to run customer-side refunds cleanly.

// 02 — section

The customer side of a refund is mostly communication and timing discipline. Done well, the customer feels treated fairly even when the answer is no; done badly, the customer becomes a chargeback regardless of whether the operator was right.

01

Answer fast, even with bad news

A clear "no" today beats a vague "maybe" for three weeks.

02

Frame the answer to the booking, not the rule

Reference the specific booking, dates and terms, not a generic policy.

03

Process refunds to the original rail

Card refunds go back to the card. Open-banking goes back by transfer. BACS reverses by BACS.

Supplier-side recovery — getting back what you paid.

// 03 — section

For every customer refund, there is usually a supplier the operator has already paid. The supplier-side recovery is where most refund losses actually happen, because suppliers operate on their own timelines and their own contractual frameworks.

01

Track supplier deposits per booking

Every supplier deposit attached to the booking it relates to, with the cancellation policy that supplier offers visible alongside.

02

Match recovery to the trip

Where a supplier refunds part of a deposit, the recovery should sit against the same booking that triggered it - so the net position per booking is always visible.

03

Chase early, document everything

Supplier recoveries that drift past 30 days rarely recover at all. Early, written recovery requests against contractual terms are the discipline that works.

How the regulatory floor shapes the refund.

// 04 — section

UK travel refunds sit inside the Package Travel Regulations, with overlays for ATOL holders, ABTA members and various scheme rules. The regulatory floor sets what the operator must do; commercial discretion sits above that.

01

Package Travel Regs set the baseline

PTR 2018 gives customers specific refund rights on cancelled packages.

02

ATOL adds protection mechanics

ATOL-protected components carry CAA-administered refund mechanics if the operator fails.

03

Insurance-backed schemes parallel

ABTOT, trust accounts and insurance-backed schemes carry similar customer-protection frameworks.

Refund discipline as chargeback prevention.

// 05 — section

Most chargebacks against travel operators are refund disputes that the operator could have prevented. Treating refund operations as chargeback prevention reframes the work - and changes the economics of the team running it.

01

A chargeback costs more than the refund

A chargeback typically carries a fee (£15-£25 from most acquirers), the original transaction amount and a quality-score hit on the merchant relationship. A clean refund costs only the refund.

02

Speed beats accuracy at the margins

At the margins - the £150 dispute, the £400 partial refund - a fast refund beats a slow win every time. The cost of a chargeback investigation often exceeds the disputed amount.

03

Refund-first culture lowers the ratio

Operators with a "default to refund" culture for borderline cases run materially lower chargeback ratios than operators who fight every dispute. Lower chargeback ratios drive lower MDR at the next acquirer review.

How to keep the refund evidence audit-ready.

// 06 — section

Refund evidence has multiple audiences - the customer, the acquirer (if a chargeback follows), the auditor at year-end, the trustee on a review cycle. Building the evidence trail once, at the moment of the refund, means it serves all of them.

01

Tie the refund to the original payment

The refund record carries the original transaction reference, the booking, the rail.

02

Record the decision, not just the outcome

Why the refund was issued, who decided, on what evidence.

03

Match supplier recovery to the refund

Where the operator recovers funds from a supplier, that recovery sits against the same booking.

What refund management looks like in felloh.

// 07 — section

felloh keeps every refund attached to the booking, the original payment and the supplier movement behind it - so the audit, regulator, trustee and chargeback responses share one evidence trail.

01

Refund evidence at the booking

Every refund records the original transaction, the booking, the decision and the supplier-side movement against the booking that produced it.

02

Chargeback defence ready

When a card chargeback lands, the refund record - and the evidence behind the refund decision - is already attached to the booking. Representment becomes a query, not an investigation.

03

Audit and trustee ready

Auditors and trustees reviewing the operation see refund movements as connected events against bookings, not as orphan ledger entries that need explaining.

See how this works around your bookings.

Bring one payment, reporting or cash-position problem. We will show how felloh connects the booking-level money trail behind it.

Book a walkthrough