GCash, Maya and bank transfer: taking guest payments

What proof of payment actually needs to include

A screenshot of a GCash or Maya transfer showing the amount, the reference number and the timestamp is the standard proof — and it's worth asking for all three specifically, because an amount alone, without a reference number, is much harder to match confidently to a specific booking days later when three similar deposits have come in the same week.

Matching a transfer to a booking without ambiguity

Asking a guest to include a reference in the transfer note — their name, or a booking code if one exists — turns matching from a guessing exercise into a lookup. Without it, a property juggling several pending deposits in the same week is relying on timing and amount alone, which breaks the moment two guests send similar amounts on the same day.

Setting the rule once, instead of negotiating it every time

The downpayment itself — a percentage or a fixed peso amount — is set once in Payments settings, not decided fresh in every chat thread, and the property's accepted methods and a QR code guests can scan to pay show up consistently on every booking that needs one, whether it was entered by staff or arrived through a connected channel. What still happens outside the system is the transfer itself — GCash and Maya aren't wired to automatically confirm a payment landed, so someone still needs to see the screenshot and mark it received.

That's the actual division of labour: the rule and the QR are structured and consistent, the confirmation is a human glancing at proof and recording it — the booking marked with the deposit received, the amount, and the date, the same way every time, rather than left as a screenshot in a phone's gallery only one staff member can find.

Bank transfer is slower — plan the confirmation window for it

A GCash or Maya transfer usually confirms in seconds. A bank-to-bank transfer, especially between different banks, can take hours or land the next business day — worth stating clearly to a guest making a bank transfer so they don't assume a booking is unconfirmed for a full day when the payment is actually just still clearing, and worth staff knowing so they don't chase a guest for a payment that's already genuinely on its way.

What this does and doesn't automate

None of this replaces the downpayment policy itself — the percentage, the cancellation rule, what happens on a no-show. What it changes is how cleanly that policy gets applied: a deposit that's clearly proven, clearly matched to the right booking, and clearly recorded is a policy enforced consistently. The same policy applied against vague, hard-to-trace transfers is a policy applied unevenly, which is where most payment disputes actually come from.

The refund side is worth the same discipline

A refund sent back by GCash, Maya or bank transfer deserves the exact same proof-and-record habit as the original deposit — the reference number, the amount, the date, written against the booking rather than left to memory. A guest disputing whether a refund was actually sent, months later, is a much shorter conversation with a reference number on record than without one.

Setting guest expectations about which methods you take

Stating clearly, before a guest is asked to pay, which of GCash, Maya and bank transfer a property actually accepts avoids the awkward moment of a guest attempting a transfer method that isn't supported and then needing a second, more complicated conversation to redo it. A single line in the booking confirmation — payment accepted via GCash or bank transfer only, for instance — removes an entire category of friction before it happens.

For guests paying from abroad

A guest booking from outside the Philippines usually cannot send a GCash or Maya transfer directly — those are domestic wallets tied to a Philippine number — which leaves bank transfer, often through an international transfer service, as the realistic option. Worth stating explicitly to an international guest rather than assuming they'll work out which of the three methods actually applies to them, since guessing wrong wastes a transfer fee and a day of back-and-forth neither side needed.

International bank transfers also often arrive short of the agreed amount, after the sending or intermediary bank takes its own fee — worth flagging in advance so a deposit that lands ₱200 light isn't mistaken for a guest trying to underpay, when it's simply a bank fee neither side controlled.

Why cash-on-arrival still needs the same discipline

A guest who agreed to a deposit but ultimately pays the full balance in cash on arrival still deserves the same consistent recording the digital transfers get — a handwritten note that's easy to lose is not meaningfully better than no record at all. Treating every payment method the same way, digital or cash, is what keeps the whole system trustworthy rather than only the transfers that happen to leave a digital trail on their own.

The record that protects the property, not just the guest

A guest disputing a deposit months later — claiming it was never sent, or sent for a different amount — is exactly the scenario a consistent record protects against on the property's side too. The same reference-number discipline that makes life easier for the front desk today is what makes an old dispute resolvable in thirty seconds instead of an unwinnable argument about who remembers what correctly. That protection runs both ways, which is exactly why it's worth building as a habit rather than something reached for only when a dispute has already started.