Money-back clauses: the exact lines in Booking.com's rules that say a refund is on the table

Here's a number nobody advertises. Booking.com's guest-facing rulebooks — the Terms and Conditions plus the "How We Work" page — run to tens of thousands of words, and the contract every hotel signs with the platform adds tens of thousands more. Out of all that, the lines that can put money back in a traveller's pocket add up to a few hundred words. Almost nobody reads them, which suits everyone except you.

This guide is those few hundred words, decoded. Which clauses say the money comes back, which ones carry your evidence, which ones the hotel signed without telling you — and, honestly, which ones push the other way. It's general information, not legal advice, and no one can promise you an outcome; what a named clause promises is a shorter argument.

Three rulebooks, one numbering trick

The lines below come from three documents, and the label tells you which:

• The Terms and Conditions — the contract you accepted at checkout. Its general part is numbered A1 to A22, the accommodation part B1 to B7.
• "How We Work" — the plainer companion page, numbered §1A to §1L. This is where the bluntest promises live, including the strongest one in this guide.
• The General Delivery Terms — the partner contract between Booking and every property, with dotted numbers like 2.6.1. You're not a party to it, but it binds the hotel — more on that below.

You don't need to be a lawyer for any of this. Every label shows a one-line plain summary when you hover or tap it, and the full documents are linked at the end. The skill isn't reading everything. The skill is matching your situation to the one or two lines written about it — and naming them in your message.

The four lines that move money

Between them, these cover the large majority of stays that go wrong. Read your situation against each; usually a single line fits, and that's the one your message is built on.

The honoured-booking rule — §1L. The strongest single line in either guest document. Once your booking is confirmed, the property is required to honour it — and if it can't, you cancel at no cost, receive a full refund, and get help finding a comparable place at a comparable price. If the only alternative costs more, the difference is refunded after your stay against the invoice. This is the clause for the overbooked hotel, the "we gave your room away", the arrival that meets a locked door. Note what it makes the room price: a floor, not a ceiling — the tiers of money a cancelled stay can owe you go beyond the booking itself.

The accurate-listing rule — §1K. Booking reserves the right to remove a property that gave an inaccurate description and failed to correct it. That one line reframes every "not as described" case: the missing kitchen, the fictional sea view, the "renovated" room from another decade aren't disappointments you should have expected — they're a breach the platform itself polices. The wider the gap between listing and reality, the more squarely this line applies, and a proportionate refund is the natural way a property makes such a gap right.

The exact-amount rule — A8. For cancellations inside a permitted free window, the refund is the exact amount initially charged, inclusive of applicable fees. Short, mechanical, and surprisingly often needed — for the charge that lands after a free-window cancellation, the "refund" that arrives with pieces missing, the processing fee nobody mentions. If you cancelled in time, this is the line that says the number, and the number is everything.

The override pair — A19 and A20. The quiet pair that keeps the rest of the document honest. The first admits the terms can't limit liability for fraud, for gross negligence, or for anything that can't lawfully be excluded — and that where mandatory consumer protections apply, those win. The second adds that consumers living in Europe can rely on their own country's consumer rules and courts. Together they mean the document you accepted has a built-in ceiling: when a stay plainly wasn't delivered as promised, no line of small print — "non-refundable" included — is the end of the conversation.

The clauses the hotel signed without telling you

Now the third rulebook — the one written between Booking and the property. Guests can't enforce it themselves (2.5.2), but Booking can and does, which turns these lines into a quiet second row of support: when a host insists "that's not how it works", one of these often says it's exactly how it works, and a factual report through the platform's channel puts it in front of the people paid to enforce it.

• No cancelling on you — 2.6.2. The property may not cancel an online reservation. The host who drops your booking because prices rose, then offers you the same room at a "new rate", is breaking this line — report it rather than rebook it.
• Rehousing on a deadline, at their cost — 2.6.1. Can't provide the booked room? Then the property owes an alternative of equal or better standard at no extra charge — and it must reimburse the reasonable costs the failure caused, from the pricier replacement to the taxi to the phone calls. Once Booking is told, deadlines run in minutes and hours, not days.
• The desk can't invent fees — 2.5.4. Beyond what your confirmation lists, the hotel can't add transaction, administration or card-payment charges. The "small fee for paying by card" at checkout isn't a local custom; it's a breach of the contract that keeps the hotel on the platform.
• The listing you booked from is binding — 2.5.3. The property must handle your reservation in line with what its page said when you booked, plus any requests it accepted. The partner-side twin of the accurate-listing rule above.
• A found lower price gets settled — 2.5.6. Where Booking's price-match promise applies to your booking and your claim is valid, the host must adjust the rate and settle or refund the difference by check-out.

The lines that carry your case

A second family of clauses won't put money on the table by themselves — they make the money-lines work. Skip them and a strong case turns into your word against the host's. Use them and the same case arrives pre-packaged, in the exact format the reader is trained to approve.

• The complaint process — A16. Every complaint raised with the platform is recorded identifiably and can be tracked, with urgent cases prioritised. Better still, the clause lists the evidence that helps: your confirmation number and PIN, a clear summary, the outcome you want, and supporting documents — pictures, receipts, bank statements. It's effectively the checklist for your own request, published by the other side.
• The report-it-promptly rule — B4. Your half of the bargain: anything broken, damaged or missing gets reported to the property at once, certainly before checkout. The same logic serves your whole case — a problem raised on day one, in writing, is one no reader can wave away as an afterthought invented at home. The line that obliges you also protects you: it proves when you spoke up.
• The complaints-flow rule — 2.5.5. In the partner contract, complaints about the stay are the property's to resolve, Booking may support the guest on request, and the host always gets a chance to fix things first. Useful to know before you're frustrated by it: "we've contacted the property and are waiting" is the agreed script, not a brush-off — and it's also why your own first message should go to the property.
• The reviews system — §1F. Reviews come from verified stays, and problem content can be reported for investigation. For your case, that cuts two ways: a pattern of past guests describing the same broken promise turns your complaint into documentation of a habit — and your own eventual review is part of why a property prefers settling a fair request over stonewalling it.
• The help promise — B3. Booking's own accommodation terms say what it will do for you: list the property, confirm the booking, and help with changes and cancellations within the booking's terms. Small, but useful — when an agent seems unsure whether helping you is their job, this is the line that says it is.

The lines that push the other way

An honest decoder shows both columns, because a request built on a line that doesn't apply collapses at the first reply. Check your case against these before you send anything. If one of them covers you, adjust the ask — or accept that this one may not be winnable and save your energy.

• "Non-refundable" and the policy you accepted — A9. The cancellation terms attached to your specific rate bind you: a non-refundable rate really does mean a change of mind carries the cost. What that label doesn't cover is the property's own failure — a room that wasn't delivered as promised is a different question from a guest who changed plans, and the money-lines above still apply to it.
• No-shows — §1H. Don't arrive, and any refund follows the property's own no-show policy. Expect little; ask politely anyway if circumstances were genuinely exceptional, but build no case on this ground.
• Obvious price mistakes — A7. The €9-a-night five-star was an error, and errors that are obviously errors aren't binding. The bargain that was too good to be true usually isn't a claim when it's corrected — though a price that was merely good and then quietly changed at checkout is a different story, worth its own complaint.
• The foreseeability cap — A19. The same clause that keeps liability alive also trims its edges: losses nobody could reasonably foresee at booking — the missed once-in-a-lifetime event, the consequential cost with no receipt — mostly fall outside what anyone owes. Keep your ask inside what a stranger could look at and call fair.

Turning a line into a message

Knowing the clause is half the job; the other half is a message that uses it without turning into a lecture. Keep it to four moves: say what was promised, say what happened, name the one line that covers it, and ask for a specific figure or fraction that matches what failed. Tone decides more than people expect — the named line is doing the arguing for you, so the words around it can stay warm and short. Send it to the property first; if that stalls, the same message goes through Booking's recorded channel, and your local consumer rules wait behind both.

The drafting itself — matching the line, keeping the tone level, landing on a fair number — is the job we built 2refund for: it turns your answers into a clear request that's yours to send.

Do I have to quote clause numbers to get anywhere?

No — a plain description of the promise works too. But naming the line does something a description can't: it shows the reader you've done the homework, and it turns a debatable opinion ('this isn't fair') into a checkable fact ('your own terms say a confirmed booking is honoured'). A message with a named clause tends to get a shorter, straighter answer, because there's nothing left to argue about except whether it applies.

Can I hold the hotel to its contract with Booking myself?

Not directly — that contract is between the property and the platform, and you aren't a party to it. What you can do is report the breach to Booking, factually, through its recorded channel: the people reading it are the ones whose job is enforcing that contract. 'The property added a card fee that isn't in my confirmation' lands differently when the reader knows their own partner terms forbid exactly that.

None of these clauses match my case — is that the end?

No. The terms themselves concede that the mandatory consumer rules of the place you live sit above them — a service that didn't match its description or wasn't delivered with reasonable care is a problem those everyday rules cover even when no specific line in the platform's document does. A calm written request, good evidence and a proportionate ask work in that space too; the clauses make a case faster, not possible.

The terms changed after I booked — which version counts?

The version in force when you made the booking. Booking's own modification clause says existing bookings stay governed by the terms that applied at booking time — so a rule that supported your case on the day you paid doesn't vanish because the document was updated before your stay.

If you keep only one label from all of this, keep §1L: a confirmed booking must be honoured. Everything else in these rulebooks is a variation on the same quiet theme — the promises were written down, and a guest who points at a written promise isn't asking anyone to be kind, only to keep it.

The cases in this article are illustrative composites, not real client records. We build them from the patterns we see again and again across the disputes we help with, because we can’t share real customers’ booking details. The stories are invented; the way they play out is true to our experience.

This article is general information, not legal advice. We’re a self-help tool, not a law firm. Rules, fees and deadlines change and vary by country, so always check the policy attached to your own booking and your local consumer protections.