Knowledge Base

Chargebacks in travel.

A practical guide to chargebacks in travel — why travel chargebacks are distinctive, the reason-code landscape, prevention disciplines, authentication and liability shift, the representment evidence that actually wins, the real cost picture, and how chargeback handling fits a booking-level ledger.

Book a walkthrough See payment optimisation

Reasoncodes mapped to prevention

Evidenceready before the deadline

Ratiotracked to acquirer reviews

Why chargebacks look different in travel.

Most card-not-present industries deliver inside days. Travel does not. A booking made in January for August travel sits inside the chargeback window for the entire intervening period - and the customer experiences the product six months after paying for it. That single fact reshapes how every part of the chargeback conversation works in travel.

The longest delivery window in retail

Card-scheme chargeback windows can reach 540 days for "merchandise not received" disputes in some scenarios. A travel booking is exposed for almost the entire period between deposit and travel.

Supplier money has already moved

By the time a customer disputes, the operator has often paid suppliers - so a successful chargeback creates a double loss unless supplier recovery works.

Regulatory overlays

Package Travel Regulations, ATOL refund obligations, EU261 compensation and Section 75 customer-card protections all interact with the chargeback. The card-scheme dispute is one of several frameworks that apply.

How a travel chargeback actually unfolds.

The chargeback timeline is the same as any other industry - retrieval request, chargeback notification, representment, pre-arbitration, arbitration - but the travel-specific reason codes and the long delivery window change what evidence matters at each stage.

Retrieval first, sometimes

For some travel disputes - particularly higher-value or first-party disputes - the issuer requests transaction documentation before raising a formal chargeback. Responding fast and completely at this stage often closes the dispute before it becomes a chargeback at all. Many operators waste this opportunity by treating retrieval requests as informational.

Trigger Issuer request

Stage Pre-chargeback

Win path Fast evidence

See chargeback in the glossary

Chargeback notification with reason code

The reason code determines what evidence wins - "merchandise not received" needs delivery proof, "cardholder did not authorise" needs authentication evidence, "credit not processed" needs refund evidence. Travel businesses that respond with a generic evidence pack rather than reason-code-targeted evidence lose disputes they could have won.

Reason code Specific

Response Targeted

Deadline 7-30 days typical

See chargeback reason code in the glossary

Representment, then sometimes pre-arbitration

A successful representment closes the dispute. An escalation to pre-arbitration means the issuer has new information from the cardholder and the merchant either concedes or proceeds to arbitration - which carries scheme fees and an outcome that goes one way or the other. Most travel disputes that reach arbitration are not worth the fees unless the principle is established.

Stage 1 Representment

Stage 2 Pre-arbitration

Stage 3 Arbitration (rare)

See dispute resolution

Section 02

Prevention — the discipline that actually moves the ratio.

Most travel chargebacks are preventable. The discipline is mostly customer communication, descriptor clarity and refund speed - not anti-fraud tooling. Operators with low chargeback ratios get there through operational habits, not technology.

Clear descriptors and receipts

A descriptor the customer recognises six months later, and a receipt that names the booking, the dates and the parties. "Friendly fraud" disputes often start with the customer not recognising the charge - solvable at point of sale.

Pre-trip communication

A confirmation at booking and a reminder before travel, both naming the descriptor the customer will see on their statement. Both work as evidence in representment if a dispute follows.

Fast, decisive refunds

Customers who get a refund inside 48 hours of asking almost never chargeback. Customers who wait three weeks for a decision almost always do.

Cardholder authentication

3DS-protected payments shift liability to the issuer for most fraud-related disputes. Routing eligible transactions through authenticated flows is the single biggest fraud-side prevention lever.

Pattern review

Chargebacks that cluster - by supplier, route, channel, payment method or customer type - point to a fixable cause. Operators with low chargeback ratios review the pattern monthly, not yearly.

How authentication and liability shift work.

Where a payment carries cardholder authentication, the chargeback liability landscape changes materially. Knowing which flows shift liability where is what makes the prevention story economic.

3DS shifts fraud liability

For fraud-related reason codes - the most common chargeback driver - a successful 3DS authentication moves liability from merchant to issuer. The merchant still has to respond to the chargeback, but the evidence is the authentication record itself. Travel transactions that bypass 3DS forfeit this protection without saving meaningful friction.

Reason codes Fraud family

Liability Issuer

Evidence 3DS record

See liability shift in the glossary

MOTO carries no shift

A MOTO payment has no 3DS step-up, so any fraud-related chargeback comes back to the merchant by default. The substitutes - call recording, AVS, CVC capture, confirmation emails - are evidence the merchant has to assemble manually, in contrast to the 3DS record that comes for free with an authenticated flow.

Authentication Verbal only

Liability Merchant

Substitute Manual evidence

See MOTO payments in travel

Open banking has no chargeback at all

The flip side of having no chargeback path is that customer disputes stay merchant-side - resolved through refund discipline rather than acquirer escalation. The bank-app authentication record is the strongest evidence of authorisation. Open-banking disputes shift the workload to refund operations rather than dispute teams.

Chargeback path None

Authentication Bank-app

Dispute path Merchant-side

See open banking for travel

Section 04

Representment — the evidence that actually wins.

A representment package is read by an issuer dispute analyst on a deadline. It needs to be specific, reason-code-targeted and easy to scan. Generic evidence packs lose more disputes than they win.

Lead with the reason code

Open the response by stating the reason code, the rebuttal and the evidence supporting it. Dispute analysts process volume - they need to see the answer in the first 30 seconds of reading.

Authentication evidence first

For fraud-family chargebacks, the 3DS record (or alternative authentication evidence) is the single piece of evidence that wins. Lead with it.

Booking and traveller context

The booking confirmation, the traveller details, the itinerary and the supplier confirmation prove the merchandise was delivered or ready to be delivered. Each one against the booking the chargeback relates to.

Communication trail

Booking confirmation email, balance reminder, pre-trip communication, post-trip follow-up. Each item dated, each one delivered to the email address on the booking.

Refund history (or absence)

Where a refund was processed, the record of when and how. Where a refund was declined, the contractual basis for the decision.

How the real cost picture of a chargeback stacks up.

The headline cost of a chargeback is the transaction value. The real cost is materially higher once fees, time, MDR impact and acquirer-relationship damage are counted. Travel businesses with mature dispute operations price the full picture.

The headline plus the fees

A typical chargeback carries a £15-£25 fee from the acquirer just to raise it. Some acquirers also charge a representment fee. Pre-arbitration and arbitration add scheme fees of £150-£500 if the dispute escalates. Before any time is spent, the gross cost of a £400 dispute can be £450-£475.

Transaction Full value

Chargeback fee £15-£25

Arbitration £150-£500

See chargeback in the glossary

Time cost on representment

For low-value disputes, the fully-loaded cost of representment exceeds the disputed amount. That is why operators with mature dispute operations write off below-threshold disputes rather than fighting them - the time goes into prevention work that reduces the next month's count.

Per dispute 30-90 min

Below threshold Concede

Above threshold Defend

See financial control

The MDR and reserve picture

Acquirers monitor chargeback ratios against scheme thresholds (Visa's VAMP, Mastercard's ExSP). Operators close to or above thresholds face MDR increases, reserve hikes, and in extreme cases programmes that require monthly attestation. The cost of a high chargeback ratio is paid on every transaction, not just the disputed ones.

Visa threshold VAMP scheme

Mastercard ExSP scheme

Pricing impact All transactions

See chargeback ratio in the glossary

Section 06

Friendly fraud and the patterns worth watching.

Friendly fraud - where the legitimate cardholder disputes a charge they actually authorised - has become the largest single category of CNP chargebacks. Travel is particularly exposed because of the gap between payment and delivery.

The "I forgot" dispute

Customer sees a charge six months after booking, does not recognise the descriptor, disputes. Clearer descriptors and pre-trip reminders prevent most of these.

The "family member" dispute

Customer's card was used by a family member with consent, but is disputed when the bill arrives. Booking-level evidence showing the traveller relationship usually wins representment but the prevention is the same booking-confirmation discipline.

The "buyer's remorse" dispute

Customer regrets the booking and tries to recover funds through chargeback rather than the operator's cancellation policy. Strong terms, strong evidence and the contractual cancellation framework defend the position.

Subscription-style misframing

Where balance schedules look subscription-shaped to the customer, "cancel this subscription" disputes can appear. Clear naming of each scheduled payment - balance for booking X, not "monthly charge" - prevents this.

What chargeback handling looks like in felloh.

felloh keeps payment, authentication, booking, communication and refund evidence attached to the booking - so the representment package is already in place when the dispute lands, and prevention work is grounded in real pattern review rather than instinct.

See this guide running on your booking data.

Bring the workflow or rail you want to improve and we will show how felloh keeps the booking-level evidence connected end to end.