Channel manager & PMS · November 16, 2026 · 8 min read

Homestay Security Deposit in Malaysia: How to Collect, Hold and Refund It Without Chasing Guests

Homestay security deposit in Malaysia, from the operator's side: which bookings should pay one, when to collect it, card hold vs charge, why the door PIN should wait for the money, refunding back to the original method, bank batches, carrying a deposit to the guest's next booking, and who keeps a forfeit.

Bahasa Melayu → · 中文 →

Short answer: a homestay security deposit in Malaysia works best when four things are decided in advance: which bookings pay one, when it is collected, what has to be true before the guest gets the door code, and how the money goes back. Most of the work, and most of the arguments, sit in the refund, not the collection.

We run 100+ homestay units in Johor Bahru and Desaru and we built the software we use for it, AntlerHub. This article is how deposits actually move through our system, written from the operator's chair. If you want the guest's side, what we deduct and what we don't, read our deposit deduction article.

Can you even take a security deposit on Airbnb bookings?

Check this before anything else. Airbnb's help page on fees says that most hosts are not allowed to charge a security deposit or a credit card hold for incidentals. The exception is "select software-connected hosts", who may collect a deposit off the platform only if it is disclosed in the right fee field before the guest books, and who must return it or release the hold within 7 days of checkout if nothing was damaged (14 days for hotels). Damage on an ordinary Airbnb listing goes through AirCover instead, and that claim has to be filed within 14 days of checkout.

So "take a deposit on every booking" is not a decision you can make alone. Agoda, Booking.com and direct bookings each have their own position, and you should read the current rule for each before you switch the deposit on for that channel. Our system lets you choose per platform for exactly this reason. It does not decide for you whether a platform allows it.

Which bookings should pay a deposit?

We check three rules, in this order, and the first one that answers wins:

OrderRuleWhat it does
1PlatformIs this booking's channel on the "collect deposit" list? If not, no deposit.
2Trusted guestHas this guest logged in with an account whose email matches the booking, verified their identity, and reached the review count and average score you set for that listing? If yes, no deposit.
3DefaultEveryone else pays the deposit.

The trusted-guest rule is the one worth thinking about. Asking a repeat guest with a clean record to pay again every time is friction for no gain. But we only waive it when three things line up: the account, the identity check, and the reviews. Any one missing and the booking falls through to the default.

When should the deposit be collected?

Our current setting, decided on 7 October 2026, is that deposits are collected on the day, not weeks ahead. The reason is practical: money taken a month early sits through cancellations, date changes and refunds that have nothing to do with damage.

That decision created a wording problem we had to fix. A booking that needs a deposit later used to look exactly like a booking that needs none, and a guest told "no deposit needed" who is then asked at the door will argue. So the guest's checklist now has four states, not two:

StateWhat the guest is told
noneThis booking takes no deposit.
paidThe deposit is in. Nothing owed.
laterA deposit is coming, on check-in day.
duePay it now.

Only "due" puts a payment step on the guest's checklist, on the website and in WhatsApp alike.

Why should the door code wait for the money?

Because the step is not the money. In our system a dozen places can mark a unit ready: the portal, the chat flow, the inbox buttons. Three times between 2 and 11 October 2026 a guest received the door code without the deposit being paid, and each fix closed only one of those places. The last fix changed the question: before check-in releases the code, it now asks how much deposit is actually held against the booking, not whether a step was ticked. If it cannot read the payment, it refuses.

If you build or buy a system, this is the test to run. Mark a booking ready by every route you have and see whether the code goes out with no deposit paid. (Codes themselves are covered in our smart lock article.)

Card hold or real charge?

MethodWhat happensRefund
Credit card (Stripe)Can be an authorise-only hold: the money is reserved, not takenRelease the hold; nothing to refund
Other cards, FPX, e-wallets (Touch 'n Go, GrabPay, ShopeePay, WeChat Pay, Alipay), Apple Pay, Google PayReal chargeBack through the original channel where the gateway allows
Bank transfer, cashGuest uploads proof, staff confirmBank transfer from you

A hold is the cleanest for a deposit, but only cards support it. FPX and the wallets cannot do an authorise-only payment at all.

Gateway fees are the other thing to decide. The guest pays the processing fee on top of the deposit, and by default that fee is not refunded: you tick, per method, whether it is kept. Where it is kept, the guest is told on the payment page before paying. Guests do not like it, and you should expect the question. Telling them before they pay is what keeps it from becoming a complaint.

How should the deposit go back?

Every deposit closes in exactly one of three ways: full refund, partial refund (you keep part, the rest goes back), or full forfeit. The refund route is chosen per payment method:

  • Back to the original method is our default wherever a gateway was involved. It is cheaper and needs no staff time.
  • Bank transfer where there is no original channel (cash, bank transfer), or where the gateway cannot do this particular refund. Two real examples: Xendit cannot refund FPX at all, and Xendit WeChat Pay can do a full refund but not a partial one. In those cases the system drops to a bank transfer by itself instead of failing when staff press "Mark as paid".

Bank transfers can be done by hand one guest at a time, sent automatically through Xendit Payout, or grouped into one bulk-transfer file for Public Bank. The bulk file was the one that broke our books: the bank showed one debit for the whole batch plus a handling charge, while the ledger had one line per guest, so nothing matched one-to-one and the handling charge was never recorded. Now each refund goes to a clearing account and one entry per batch moves the total out of the bank, with the charge booked as a bank charge. If you do OTA payout reconciliation, it is the same idea.

"Paid" should mean the money left

Staff often set up a bank transfer that the bank sends days later. If they mark it paid when they set it up, the guest gets "your deposit is back" before the money moves. So a refund can now be scheduled: pick the time, and at that time it is marked paid exactly as if the button had been pressed then, which is when the guest's message goes out. One deposit can sit in only one pending schedule, so it cannot be paid twice.

The guest can also see a timeline of their own deposit: when it was taken, when it went back, whether any of it was kept and why. Every line comes from something somebody did. Where the refund has not happened yet, the guest sees the refund time you published for that payment method (our default setting is 7 days), not a date the system made up.

What if the same guest books again right away?

A guest checks out of unit A and into unit B. Refunding the deposit and collecting it again would invent two bank movements that never happened. So the deposit is carried to the next booking:

Unit B needsWhat happens
The same amountCarry it, collect nothing
MoreCarry it, collect only the difference
LessCarry the whole amount; the extra is settled at B's checkout

In the books, a deposit is money you owe the guest, a liability. Carrying it posts no entry because nothing changed except which booking it belongs to. Stay extensions follow the same thinking: finance cannot refund the deposit while the extended stay is still running.

Who keeps a forfeited deposit, you or the owner?

If you manage units for owners, decide this in the agreement. Our system has three settings: all to the operator, all to the owner, or shared by the owner's share percentage. Under fixed-sum arrangements (sublet, guaranteed return) a forfeit is always the operator's. A forfeit is not booking revenue, so it does not count towards revenue tiers. How this appears in the owner's month is in our owner statement article.

What a deposit will not do for you

  • It will not cover big damage. A deposit sized for a homestay is small next to a broken TV or water damage. That is what insurance and platform claims are for.
  • It will not settle a denial. If the guest says it was not them, the deposit only means you hold the money while you argue. Photos at checkout matter more.
  • It costs guests money they don't get back if you keep the processing fee. That is a fair choice, but say so first.
  • On Airbnb it may not be allowed at all for your account. Check before you switch it on.

Do you need software for this?

With a handful of units and only bank transfers, a spreadsheet and a disciplined person can do it. It starts failing when you have several payment methods, refunds that must go back to cards and wallets, owners who share forfeits, and guests who move from one unit to the next. That is the point where we stopped doing it by hand.

AntlerHub handles deposits as part of the booking, payment and refund flow described above. See what AntlerHub does and the current pricing.

This describes how our own system works and what Airbnb's help pages say as of 16 November 2026. It is not legal or accounting advice; check the current rules of each platform and with your accountant.

One calendar for every platform

AntlerHub syncs rates and availability across Airbnb, Agoda, Booking.com and direct bookings, and pays credits only for units you list.

See AntlerHub