Quick answer: On Booking.com, “security deposit” almost always means a damage deposit, money collected to cover damage, not to secure the stay itself. Booking.com gives you two ways to handle it: collect and manage the deposit yourself, or let Booking.com facilitate a damage programme on your behalf. Either way, deposits are a separate mechanism from prepayments (which secure the stay) and pre-authorisations (which just verify a card works) and confusing the three is where most host disputes start.
This guide covers all three mechanisms and how they fit together, so you know which one solves which problem. For how Booking.com’s payments and deposits compare to Airbnb and Expedia, see our OTA payments, deposits & fees guide.
In this guide:
- Security deposit vs. prepayment vs. pre-authorisation, at a glance
- How damage deposits work, and your two options as a host
- How prepayments work
- How pre-authorisations work, and what to do when a guest’s card fails
- Why manual payment management breaks down at scale
- Alternatives to deposits that don’t cost you bookings
- FAQs
Table of Contents
Security Deposit vs. Prepayment vs. Pre-Authorisation
These three terms get used interchangeably by hosts, and Booking.com’s own interface doesn’t always make the distinction obvious. They are not the same thing, and mixing them up is one of the most common causes of guest disputes.
| What it is | When money moves | What it covers | |
| Damage deposit | An amount held or claimed against property damage | Before, during, or after the stay depending on setup | Property damage only |
| Prepayment | Part or all of the booking cost, paid in advance | Before arrival | The stay itself, per your cancellation policy |
| Pre-authorisation | A temporary hold to verify a card is valid | No money is actually taken | Card validity, not damages, not the stay |
How Damage Deposits Work
A damage deposit exists to cover the cost of repairing or replacing something a guest damages during their stay not to secure the booking itself. Booking.com gives hosts two ways to handle this, and picking the right one matters more than most hosts realise:
- Self-managed deposit. You set the amount, collect it directly from the guest (cash, bank transfer, or payment link), and refund it yourself if the property is undamaged. You keep full control, but you also own the entire collection, tracking, and refund workload.
- Booking.com-facilitated damage programme. You don’t collect anything upfront. If damage occurs, you submit a claim to Booking.com within a set window after checkout, and Booking.com pursues payment from the guest on your behalf. This removes the upfront friction for guests, but claims are capped and time-limited.
This policy has to be set and shown to guests upfront in your Booking.com listing settings collecting a deposit the guest wasn’t told about beforehand risks disputes and a guest reporting you to Booking.com
How Prepayments Work
A prepayment is a partial or full payment of the booking price, charged before arrival and governed by your cancellation policy. It has nothing to do with damage it exists to protect your revenue, not your property.
Why hosts set one up:
- Fewer last-minute cancellations. A guest who’s already paid – especially non-refundably – is far less likely to cancel.
- Guaranteed partial revenue, even if the guest cancels after the free-cancellation window closes.
How it’s collected depends on your payment setup:
- Using Payments by Booking.com: Booking.com charges the guest automatically according to the prepayment policy you set up in your Extranet
- Handling payments yourself: You’re responsible for charging the guest’s card directly, or charging the virtual credit card (VCC) Booking.com issues for the booking.
How Pre-Authorisations Work
A pre-authorisation is a temporary hold on a guest’s card, no money is taken. It exists purely to confirm the card is valid and has enough available credit to cover things like a cancellation fee or the first night’s stay. It cannot be used to cover damage. That’s what the deposit is for, and treating a pre-auth as your damage cover is a common – and costly – mistake. You set up pre-authorisation directly in your Extranet, under your payment settings.
What to do when a guest’s card is invalid
If a pre-authorisation fails, Booking.com has a defined, commission-safe process:
- Mark the card as invalid in the reservation details in your Extranet.
- Booking.com contacts the guest automatically by email and SMS, requesting updated card details.
- The guest has 24 hours to provide a valid card.
- You can cancel without penalty. If the guest doesn’t respond in time, you can cancel the reservation with no commission charged.
Why Manual Payment Management Breaks Down
If you manage one property, chasing a bank transfer or collecting cash on arrival is annoying but manageable. If you manage several – especially remotely, without in-person check-in – it stops being a minor inconvenience and starts being a structural problem:
- Deposits and prepayments get requested inconsistently, because there’s no forcing function
- Refunds get delayed because nobody’s tracking which deposits are still open
- Guests dispute charges because the policy wasn’t communicated clearly before arrival
- Staff time goes into chasing payments instead of running the property
This is the point where most multi-property hosts stop handling these mechanisms manually and build collection, holding, and release into their check-in workflow instead – typically through a property management system that can pre-authorise a card automatically as part of online check-in, release the hold on a set schedule, and flag failed cards without a human having to notice. A channel manager that keeps policies consistent across every OTA you list on reduces the chances of a guest seeing one deposit policy on Booking.com and a different one elsewhere.
Automation solves the collection problem, but it doesn’t answer a separate question: whether requiring a deposit at all is costing you bookings in the first place.
What If a Deposit Puts Guests Off Booking?
This is a legitimate concern, because damage deposits on Booking.com are optional – which means requiring one puts you at a disadvantage against listings that don’t. Some guests see a large hold on their card as a hassle, or as a signal of distrust, and simply book elsewhere.
The alternative: screening and guarantees instead of a large deposit
A growing number of hosts are moving away from large refundable deposits and toward a two-part model instead:
- Guest screening before booking. Identity verification and cross-referencing against known problem-guest records, so risky bookings are flagged before they’re confirmed rather than disputed after the fact – this is typically built into the ID verification step of a property management system’s booking process.
- A damage guarantee instead of a deposit. Rather than holding a large sum on a guest’s card, the booking is covered by a third-party guarantee up to a set amount. No large hold, no friction at checkout – but the host still has protection if something goes wrong.
The trade-off is straightforward: you give up direct control over the claims process in exchange for a smoother guest experience and, for many hosts, a higher conversion rate on their listing. Whether that trade is worth it depends on your risk tolerance, your property type, and how much of your booking volume you think a visible deposit is actually costing you.
Where deposits still make sense
Guarantees typically cap out at a fixed amount, and Booking.com’s own facilitated damage programme is capped and time-limited too. For higher-value properties, or ones with expensive furnishings, that cap may not be enough – a self-managed deposit still gives you uncapped flexibility to claim what you actually need, provided you can prove it.
FAQs
Does Booking.com collect the security deposit for me?
Not by default. If you choose the self-managed option, collection is entirely on you. If you enrol in Booking.com’s facilitated damage programme instead, Booking.com pursues payment from the guest after you submit a claim – but you don’t collect anything upfront either way.
Can I charge a deposit through Booking.com’s payment system?
Booking.com’s payment processing (Payments by Booking.com) handles prepayments and pre-authorisations directly. A self-managed damage deposit still has to be arranged directly with the guest, outside that system.
What’s the difference between a pre-authorisation and a deposit?
A pre-authorisation is a temporary hold used only to verify a card is valid – no money moves, and it can’t be used to cover damage. A damage deposit is a separate amount actually held or claimed specifically to cover damage.
Is a Booking.com damage deposit refundable?
Yes, under the self-managed option, it’s fully refundable if the property is left undamaged, and it’s the host’s responsibility to process that refund promptly. Delays are one of the most common sources of guest complaints and negative reviews.
Can a guest refuse to pay the deposit and still keep their booking?
If your policy is clearly set and shown upfront in your listing, a guest agrees to it as part of booking. If they then refuse to pay, you can report the issue to Booking.com as guest misconduct, which can affect their ability to book with you or other hosts in future.
Do I have to require a security deposit at all?
No; deposits are optional on Booking.com, and so is enrolling in the facilitated damage programme. Some hosts skip both and rely on guest screening or a third-party damage guarantee instead, trading direct control for less booking friction.
What happens if a guest’s card fails pre-authorisation?
Booking.com marks it invalid, contacts the guest automatically for updated details, and gives them 24 hours to respond. If they don’t, you can cancel the booking without being charged commission.
