Refundable Deposits Across Channels: Where the Money Actually Sits

A deposit is not one thing. On one channel it is a hold, on another it is a charge, and on a third it is a promise nobody has implemented.

Last updated: September 30, 2026

Ask five hosts what a deposit is and you'll get five answers, because the word covers at least three different mechanisms. On some channels a deposit is an amount ring-fenced on the guest's card. On others it's a sum actually taken and refunded later. On others again it's a line in your policy that nothing ever collects. The difference isn't academic. It decides where the money sits, who can move it, and what you can honestly tell a guest who asks. This article follows a deposit from booking to release, then settles on one policy you can keep across every channel.

Key Takeaways

• A deposit is at least three mechanisms wearing one word. A hold, a charge, and a promise nothing implements. The label hides the difference.
• Where the money sits decides everything else. Who holds it, when it moves and what a guest can be told all follow from the mechanism.
• One policy won't run identically on every channel. What's technically possible is set by each channel's terms, not by your preference.
• Vagueness is what turns this into a complaint. A guest who can't tell whether money was taken or merely held assumes the worse reading.
• Write one policy, then translate it per channel. A promise you can't keep on one channel only exists on paper.

Three things hosts call a deposit

The first mechanism is a hold. Some channels ring-fence an amount on the guest's card without taking it, and release the fence when the stay ends without a claim. The guest sees a pending amount rather than a charge. From your side, no money arrives, and nothing needs refunding.

The second is a charge. Here the amount is genuinely taken, and a refund is issued later if nothing is claimed. The difference from a hold isn't cosmetic. A charge is money that left the guest's account, and the refund is a separate event that follows the channel's process rather than yours.

The third is a promise. Some listings state a deposit in the house rules and nothing collects it at all. The guest read a number, believed it was secured, and no mechanism exists behind it. This is the version that produces the worst conversations, because the guest was given a protection that was never real.

Because one word covers all three, "what's your deposit policy?" is unanswerable until you name the mechanism. That's the first thing to fix, and it's a wording problem before it's a systems problem.

Following the money from booking to release

The useful way to think about a deposit is to follow it. At each stage, ask one question: who can move this money right now?

At the booking stage, the answer depends on the mechanism. With a hold, nobody has the money; it's ring-fenced and visible but not collected. With a charge, whoever collected it holds it until release. That difference shapes the guest's experience long before check-out, and it shapes what you're able to promise.

Through the stay, little changes. The guest can't spend it, and you can't either. What matters here is the thing a claim would be judged against, which is the state of the property, and the record of that state is something you write rather than something the channel collects for you.

At check-out, the decision point arrives. If there's no claim, the amount should be released. If there is one, somebody has to decide what a fair deduction is, on what evidence, and by when. That decision sits with whoever holds the money, and it's governed by the channel's booking terms and, in many places, local consumer protection rules.

At release, timing is the part hosts most often promise wrongly. You don't control when a refund appears; the channel's process and the guest's bank do. Naming a firm date you don't own is a promise you can't keep, and a guest who was told one figure and waited longer remembers the host, not the bank.

One structural point worth stating plainly: the tools you use to manage listings and availability don't collect, hold or move deposits. Deposits sit with the channel or with you, under the channel's terms. Anything that claims otherwise is describing something it can't do.

Answering a guest who asks where their money is

This is the question that turns a small policy gap into a complaint, and it deserves a written answer rather than an improvised one.

First, find out which mechanism actually applies. Don't answer from memory, because the answer differs by channel and can change over time. Look at the booking, read what the channel says about that specific reservation, and answer from that. If the guest booked through a channel that uses a hold, saying "you've been charged" is wrong and alarming. If that channel uses a charge, saying "it's only a hold" is just as wrong.

Then explain two facts separately: whether money left the account, and when it comes back. Those are different things, and guests conflate them largely because hosts do. A sentence that keeps them apart prevents most of the follow-up messages.

Keep guest details where they belong while you work through this. A deposit question often arrives with a payment reference, a phone number and sometimes an ID. None of that needs to sit in a shared inbox where anyone can read it. The guest details your system handles are masked automatically, so a name, a phone number or an ID number doesn't sit in plain sight, and access is scoped by domain, which means the person checking availability doesn't automatically see payment history. Your calendar shows each connected channel's source rate and source status at localsbnb.com, and that's usually where a deposit question starts, because the first thing you need is which channel the booking came through and what that channel's booking terms say about it.

When you can't answer yet, say so plainly and give a time. A holding answer you keep beats a confident answer you have to retract, and guests can tell the difference between a host who doesn't know yet and a host who's guessing.

Choosing one policy you can keep across channels

The goal isn't one identical mechanism on every channel, because the channels won't allow it. The goal is one policy you can state, then translate per channel without changing the promise.

Write the policy in plain words first. What is the deposit for? How much, using your own figures? What would have to happen for any part of it to be retained? When should the guest expect it back? That paragraph is your policy, and it should read the same everywhere a guest could compare it.

Then check it against each channel's terms. Where a channel supports a hold, use the hold. Where it only supports a charge, use the charge, and adjust your wording so the guest understands money left the account. Where neither exists, don't advertise a deposit at all, because a promise nothing implements is worse than no deposit.

Keep the wording identical across your listings, so a guest comparing two of your properties reads the same commitment in both. And decide, in writing, who on your team can see deposit details and who may discuss them. Domain-scoped access exists for exactly this, and whoever handles housekeeping doesn't need payment history to do their job.

Finally, don't promise a release date you don't control. Say what the channel's process is and say when you'll follow up. That version of the policy survives contact with a real month, and it's the one you can repeat without checking your notes.

FAQ

Why do different channels handle deposits differently?

Because a deposit is several mechanisms rather than one. Some channels ring-fence an amount without taking it, some take a sum and refund it later, and some offer no mechanism at all. What's available on a given channel comes from that channel's own booking terms.

Is a hold the same as a charge?

No, and the difference matters to guests. A hold ring-fences an amount without moving money out of the account. A charge takes the money, and the refund that follows is a separate event with its own process. Telling a guest the wrong one of those creates a problem where there wasn't one.

Can my booking or channel software hold the deposit for me?

It doesn't, and it shouldn't claim to. The software you use to manage listings and availability doesn't collect, hold or move deposits. Deposits sit with the channel or with you, under the channel's booking terms and the local consumer rules that apply.

A deposit is a mechanism, not a sentence in your house rules, and the mechanism differs by channel. Follow the money stage by stage, answer guests by separating whether it left their account from when it returns, and write one policy you can translate rather than repeat verbatim. When you want to see which channel a booking came through and what that channel is carrying, localsbnb.com keeps each connected channel's source rate and status on one calendar, and masks guest names, phone numbers and ID numbers, so a payment question doesn't become a data question.

---

This article is general guidance for hosts and isn't financial, legal or platform policy advice. Deposit mechanisms, refund timing and consumer protection rules differ by place and change over time; check the current booking terms of each platform you use and the rules that apply where the property sits.