Guest Disputed the Charge on Booking.com: The Non-Airbnb Chargeback

Hosts who work across platforms learn the difference the hard way, usually about six weeks after a damaged stay. On Airbnb a disputed charge is largely the platform’s problem. On a Booking.com reservation where you took the payment, the dispute is yours: your acquirer, your deadline, your evidence bundle, and a fee whether you win or lose.

Work out who took the money

Everything depends on this and hosts often do not know the answer until they look. Two broad setups exist. In one, the platform collects from the guest and pays you, which puts most payment disputes with the platform. In the other, you collect from the guest, either by charging a card at the property or through your own processor, which makes you the merchant.

Check your reservation and payment settings before an incident rather than during one. If your bookings arrive with a virtual card number, note what that card is authorised for: it typically covers the accommodation cost, and it is not a general-purpose card you can charge extras to. Booking.com host damage and partner claims covers how damage is handled on that platform, and damage protection across platforms compared puts Airbnb, VRBO, Booking.com and direct side by side.

Why the defence is different from an Airbnb dispute

The consent row is the one that decides most of these. A card issuer is not asking whether the damage happened; they are asking whether the cardholder authorised this specific charge. That is a documentation question, and it is answered by your terms plus a written agreement in the reservation thread, not by photographs of a broken table.

Get the authorisation before you need it

The practical sequence on a non-Airbnb booking is: document the damage, cost it with an invoice or quote, then ask the guest in writing to authorise the specific amount before you charge anything. A message that says “the repair is $340 per the attached invoice, please confirm you agree to this being charged to your card” and a reply saying yes is worth more in a dispute than any photograph.

If they refuse, you are not out of options, but you are out of the easy one. What remains is the deposit or pre-authorisation you took at booking, if any, and then the ordinary debt routes. The mechanisms to have in place beforehand are in collecting a damage deposit for direct bookings, which apply equally to partner-platform stays where you handle payment.

The bundle that defends a charge

• The booking confirmation and your terms, showing the damage clause the guest accepted.
• The written exchange where the amount was presented and, ideally, agreed.
• Dated before-evidence showing the item intact, with metadata intact.
• Dated after-evidence of the damage, unedited.
• The third-party invoice or quote, itemised, on letterhead.
• A short factual timeline, in plain language, with the amounts reconciled.

Submit it as one coherent document rather than a folder of files, and answer the reason code the issuer actually cited rather than telling the whole story again. The mechanics of representment, and how the reason codes shape the response, are in the chargeback defence guide. The Airbnb-side version of the same problem, where the platform absorbs more of it, is in Airbnb chargeback: what to do when a guest disputes the charge.

Deadlines are strict and short

Unlike a platform claim, this process runs on the card scheme’s calendar. Your acquirer will pass you a deadline that is typically measured in days, and a bundle submitted after it is not considered no matter how strong it is. Diarise the date the moment the notification arrives, and prepare the bundle before you research the arguments.

Note also that the damage evidence has to have been collected long before this point. A dispute arriving six weeks after checkout cannot be answered by going back to photograph anything, which is why the documentation habit rather than the dispute skill is the thing that decides these. Why Airbnb rejects your photos applies here too: an issuer that cannot verify when an image was taken treats it as an assertion.

What the platform will and will not do

Partner platforms do provide help, and it is worth asking for, but the help is administrative rather than financial. Support can usually contact the guest, pass on your message, mark the reservation, and in serious cases act against the account. What they generally will not do is stand behind the money the way a first-party damage programme does, because on a stay you were paid for directly, they were never holding the funds.

Damage tooling on partner platforms also varies by market and by how your property is set up, so the honest instruction is to check your own account rather than to trust a general description. Find out, before the season, whether you can collect a deposit through the platform, whether your reservations arrive with a virtual card, and what the terms say about damage charges. Those three answers determine your entire recovery route.

Ask support in writing and keep the reply. A dated message from the platform confirming how damage charges work on your account is useful twice: it tells you what you can do, and it becomes part of the bundle if you ever have to explain to an issuer why the charge was legitimate.

Prevention is a payment decision, not a cleaning decision

Three changes remove most of this exposure on partner-platform and direct stays. Collect a deposit or a pre-authorisation at booking, so there is something to release rather than something to charge. Put the damage clause and the charge authorisation in the terms the guest accepts. And document every turnover so the before-record exists for every channel, not only for the platform that asks for it.

Damage waiver versus security deposit versus deposit-free compares the collection models honestly, including which ones create friction at booking. Direct-booking damage with no AirCover covers the wider recovery sequence when there is no platform programme behind the stay at all.

The honest summary

On any stay where you took the money, a disputed damage charge is a merchant problem with a short deadline and a documentary answer. Get written authorisation for the specific amount before charging, keep dated before-and-after evidence for every channel, and submit a single coherent bundle that answers the issuer’s reason code.

Where the guest paid by virtual card and refuses to authorise anything further, accept that the charge was never really available and put a deposit mechanism in place for next season. That is a pricing decision, not a dispute.