Deposit Capture and Release: Timing Across Four Channels

Deposits are the one part of the money flow that behaves differently on every channel, and the difference is almost always about timing rather than amount.

Last updated: September 26, 2026

A deposit is the same idea on every channel and a different process on each one. The guest's card gets committed, the money sits somewhere that isn't your account, and it goes back on a schedule you didn't set. What changes across Airbnb, Booking.com, Agoda and Trip.com is the timing, and that timing is what your cash flow has to absorb.

Key Takeaways

• Timing, not amount. The four channels differ far more on when a deposit moves than on how much it is.
• You don't set the clock. Release windows follow the platform's current terms, not your house rules.
• A hold isn't a charge. Committing an amount and receiving it are two separate events with two separate dates.
• Disputes start at release. Most deposit arguments happen when the money goes back, not when it's taken.
• Say the window upfront. A guest who expects the right timeline doesn't open a case about it.

How a deposit is taken, held and returned on each channel

Three moments matter, and they're separate events. Capture is when the guest's money gets committed or authorised. Holding is the stretch in between, when the amount sits somewhere that isn't your operating account. Release is when it goes back, in full or in part. A conversation about a deposit goes wrong when these three get treated as one.

On all four direct channels — Airbnb, Booking.com, Agoda and Trip.com — the mechanics are defined by the platform rather than by you. Some commit an amount at booking and settle at checkout. Others route the deposit through the property's own payment arrangement on that channel. Each one defines its release window itself, and those definitions get revised.

So the useful thing to hold in your head isn't a number of days. It's which party moves the money, and what has to be true before they move it. Airbnb's handling, Booking.com's, Agoda's and Trip.com's each follow their own rules, and each is governed by that platform's current terms and by local rules where you operate. Confirm both before you promise a guest anything.

The vocabulary differs as well, and that's where guest confusion starts. A platform may call it a hold, a deposit, a damage deposit or an authorisation, and the guest reading a bank statement sees another label again. When you write to a guest, use the same word the channel uses on the confirmation, so what you tell them matches what their bank shows.

One thing is consistent. You don't get to pick. Your house rules describe what a deposit is for; they don't set when a platform returns it.

Why the holding period differs, and what it does to your cash

A holding period exists for a reason, and the reason varies by channel. Some hold to cover a damage claim window. Some hold because the payment method itself settles slowly. Some hold because the deposit is collected as a transaction separate from the booking.

For your cash, the effect is a gap. An amount committed against a guest's card isn't money you can spend, and an amount held on a platform side isn't in your account either. Budget as though a deposit is income and you'll be planning against a balance that never arrives.

The practical move is to treat deposits as outside your operating float entirely. Plan the month on booking revenue. Treat any deposit that later becomes a charge as a recovery rather than as income. A slow release then doesn't create a hole, and a fast one doesn't flatter a weak month.

Where the money waits differs too. Some deposits sit with the platform, some sit with your payment provider. Either way the release triggers live on the platform's side, and those triggers can change between seasons. Re-read the terms when a platform notifies a change instead of assuming last year's window still applies.

The disputes that begin at release rather than at capture

Capture rarely produces an argument. The guest agreed to it at booking, the amount is on the confirmation, and nothing has happened yet.

Release is where it goes wrong, and four shapes cover most of it. The guest expected the full amount back and a deduction appeared. The guest expected it back by a date that passed. The deduction got explained after the money moved rather than before. Or the guest can't see the release at all, because it went back to a card that's since been cancelled.

The common thread is notice. A deduction a guest learns about while checking their balance reads as a charge they never agreed to. The same deduction, described with photographs and a line-by-line reason before the release, reads as a settlement.

So sequence it deliberately. Decide the deduction while the guest is still reachable. Send the evidence and the reason. Give the guest room to respond before the money moves. Then let the platform release on its own schedule, and say which schedule that is rather than guessing at it.

What you can control is how much of the timeline is visible to both sides at once. Airbnb, Booking.com, Agoda and Trip.com connections sit in one channel list at localsbnb.com, each row showing its connection state, so you know which channels are live before you promise a guest a date. The list doesn't move the money. It tells you where to look.

What to put in the listing so guests expect the right timeline

Guests don't argue about a wait they were told about. They argue about a wait they discover. So the timeline belongs in the listing, in plain language, before the booking rather than in a message afterwards.

Four things are worth saying. What the deposit is for. That it isn't a charge unless something goes wrong. That the return is handled by the channel rather than by you, so the timing follows that platform's current terms. And what the guest should do if the window passes and nothing has come back.

That last line is the one hosts skip and the one that saves the most time. A guest who knows who to contact, and knows it isn't you, files one enquiry instead of five. It also sets the expectation that the deposit follows the channel's rules rather than your calendar.

Keep the wording short, and put it in the house rules as well as the listing description. House rules are what a guest opens later, once the stay has already happened and the question has actually occurred to them.

Review that wording whenever a channel changes its payment terms. A listing sentence describing last season's window becomes a promise you can't keep, and a guest who was told the wrong thing has a fair complaint. Put a reminder in your calendar to reopen the listing after any platform notice about payments, rather than waiting for the first guest to notice.

FAQ

Is a deposit the same as a security hold?

Not always. A deposit gets collected and then returned, in full or in part. A hold commits an amount without moving it, and it expires on its own. Which one a channel uses is set by that platform's current terms, so check rather than assume.

Who decides how long the money is held?

The channel does, for money sitting on its side, and it can change between seasons. Local rules can also affect what you're allowed to hold and for how long. Neither is a fixed number you can carry from one market to another, so treat every window as something to confirm instead of something to remember.

What if the guest disputes a deduction after release?

Then you're inside the channel's own dispute process, and your evidence is whatever you assembled before the money moved. That's the argument for deciding the deduction and sending the reason while the guest is still reachable, rather than after the release has run.

Deposits are small amounts of money and large amounts of timing. Know who moves the money on each channel, keep deposits outside your operating float, and describe the return in the listing before anyone books. The channels you sell on and their connection states are visible in one place at localsbnb.com, so you can check what's live before you promise a timeline rather than after a guest asks.

---

This article is general guidance for hosts and isn't legal or platform policy advice; deposit handling, holding periods and release windows are set by each platform's current terms and by local authorities, and those prevail.