Taking Payment Directly for Your Shortlet: Transfers, Deposits & Fake Alerts (2026)

The short answer: take a deposit before you block dates, take the balance before check-in, and treat only a confirmed credit visible in your own banking app as proof of payment — never a screenshot, never an SMS, never a "the transfer is processing". For amounts above ₦100,000, give the transfer time to clear before handing over keys. Those three rules prevent almost every payment loss a Nigerian shortlet host suffers.

Direct bookings are the highest-margin channel available to you. No platform commission, no currency conversion, instant naira settlement — worth roughly 20% more than the same booking taken on Airbnb once the full payout fee stack is accounted for. But going direct means you absorb the risks the platform was quietly handling. This is how to absorb them properly.

Structure the money before you discuss the apartment

Most payment disputes are actually structure disputes. Decide these once, write them into your standard WhatsApp reply, and apply them without exception:

Stage	What you collect	What it buys the guest
Enquiry	Nothing	Availability confirmation and a quote, held briefly
To hold dates	Deposit — commonly 30–50% of the stay	Dates blocked on your calendar
Before check-in	Balance in full, plus caution fee	Check-in details and access
After checkout	Refund of the caution fee, less any deduction	Closure — and a reason to book again

Two rules make this work. Dates are not held until the deposit lands — "I am sending it now" is not a booking, and treating it as one is how you end up with two guests for one night. And the balance clears before the key moves, not at the door, not after check-in, not "on Monday".

State your caution fee, and state when it comes back. A guest who knows they will get ₦50,000 back within 48 hours of a clean checkout behaves differently from one who suspects you will keep it.

Fake alerts: how the scam actually works in 2026

This is the single most common way Nigerian hosts lose money on direct bookings, and it has become considerably more sophisticated than a badly Photoshopped screenshot.

Fraudsters use purpose-built apps that generate convincing transaction notifications carrying a sender name, account number, amount, reference number and date. SMS spoofing lets them make the message appear to come from your bank's sender ID, so it lands in the same thread as your genuine alerts. Two refinements are worth knowing by name:

• The double alert. The guest sends a small genuine transfer — say ₦20,000 — which you really do receive. Then a fake alert arrives for the remaining ₦280,000. Because the first one was real, you trust the second.
• The value date trick. The fraudster explains that the money has left their account but is showing a future value date, or blames "bank network issues" for the delay. It creates a plausible reason for your app to show nothing while pressuring you to release the keys anyway.

Both attacks exploit the same weakness: relying on a notification rather than a balance.

The verification rule

Open your banking app. Look at your balance. If the money is not in the balance, it has not been paid.

Not the SMS. Not the screenshot the guest sent. Not the email. Not the transfer receipt with your correct account number on it — receipts are trivially edited. The balance in your own app, checked by you, on your own device.

Additional discipline that costs you nothing:

• For anything above ₦100,000, allow time to clear. Roughly 90 minutes covers the settlement windows within which some transfers can still be reversed. For a large booking or a same-day arrival from a stranger, that wait is cheap insurance.
• Treat urgency as a red flag, not a reason to hurry. "I am already at the gate", "my flight lands in an hour", "the bank system is slow" — genuine guests accept a short wait. Pressure to skip verification is the tell.
• Check the amount against the exact figure you quoted. Overpayment followed by a request to refund the difference is a well-established scam: the original credit reverses, your refund does not.
• Never refund to a different account from the one that paid you, and never refund before the incoming payment has genuinely settled.

The structure above is easier to hold to when the booking itself is doing the remembering. In Nookpal a deposit, a balance and a caution fee are three separate payments recorded against one booking, each with its own date and amount, and the booking shows what is still outstanding — so "have they paid the balance?" is something you read rather than reconstruct from a WhatsApp thread at the gate.

Rails: what to actually use

Bank transfer is the default and it is fine, provided you verify by balance. Where volume justifies it, a payment link or a dedicated account number adds real operational value — not because it is safer for the guest, but because it removes the verification problem entirely. A gateway confirms settlement itself, so there is nothing to fake.

Method	Indicative cost	Why a host would use it
Direct bank transfer	Free	Universal, instant — but you carry the verification burden
Moniepoint / Monnify	~0.5% capped ~₦1,000; transfers ~1.5% capped ~₦2,000	Cheapest gateway; dedicated account numbers per guest make reconciliation automatic
Flutterwave	~1.4% local cards, capped ~₦2,000	Payment links you can send straight into a WhatsApp thread
Paystack	~1.5% local cards, capped ~₦2,000	Same, with strong reliability and clean receipts

Note the caps. On a ₦600,000 booking, a capped ₦2,000 fee is about 0.3% — against roughly 20% total leakage on the same booking through Airbnb. For direct bookings of any size, a gateway is close to free, and it hands you an unforgeable settlement record.

The dedicated-account-number model is particularly well suited to shortlets: each guest gets their own account number to pay into, so an incoming credit identifies itself against a booking without you matching names and amounts by hand.

Records: the part hosts skip and later need

Every direct payment should leave you with five things: who paid, how much, when it settled, which booking it belongs to, and what it was for — deposit, balance, caution fee, or extension. A WhatsApp thread is not a record. Neither is a bank statement on its own, because it tells you money arrived but not which of your six units it was for.

You need this in four situations, all of which will eventually happen: a guest disputes what they paid; a caution fee refund is questioned weeks later; an agent claims a booking was theirs; and your accountant asks what a unit actually earned. In each case, the host with dated payment records tied to bookings settles it in a minute and the host without spends a week arguing.

This is exactly why Nookpal treats payments as records attached to a booking rather than a status flag on it — multiple payments per booking, each with its own date, amount and type, with off-platform naira transfers as a first-class case rather than a workaround. A caution fee is visible as a caution fee, so what you owe back is never a matter of memory.

Reconciliation is the quiet win here. Because each payment is attached to a booking and a unit, month-end is a report rather than an afternoon matching bank credits to names — and a caution fee you owe back is visible as a caution fee rather than something you have to remember.

Corporate and agent payments

Two exceptions to the pay-before-check-in rule are worth planning for rather than improvising:

• Corporate guests often cannot pay upfront — company finance departments work on invoice and payment terms, frequently 30 days after the stay. That is a cashflow decision, not a payment failure, and it is the price of access to the most valuable guest segment. Get a purchase order or written booking confirmation from the company, invoice properly, and know that you are extending credit.
• Agent-sourced bookings introduce a third party to the money. Decide explicitly whether the guest pays you and you settle the agent, or the agent collects and remits. The first is safer. Either way, the guest-facing price and your host revenue are different numbers and should be recorded separately — covered in managing shortlet agents and co-hosts.

And when the money does land, issue a receipt rather than replying "received, thanks". Nookpal generates one against the booking with your business details on it, which costs you nothing, settles caution-fee arguments weeks later, and quietly signals to the guest that they are dealing with a business rather than an account number.

A five-line policy you can send today

1. Dates are held once the deposit reflects in our account.
2. The balance and caution fee clear before check-in details are shared.
3. We confirm payment from our bank app, not from screenshots — please allow a short wait for larger transfers.
4. The caution fee is refunded within 48 hours of checkout, less any documented damage.
5. Payment is only to the account details sent from this number. Please confirm with us before paying anyone else.

That last line does double duty: it protects the guest from the cloned-listing fraud that is widespread in Lagos, and it protects you from being blamed for it. Adapt these into your standard replies alongside our WhatsApp templates for shortlet hosts.

Gateway pricing is indicative as of 2026 and negotiable at volume — confirm current rates directly. Nothing here is financial or legal advice.