A refund for a reservation made through your direct booking engine needs a clear process and a clean record, and this walks through both.
A guest who booked through your direct booking engine asks for a refund, and unlike an OTA reservation, there's no platform handling the refund mechanics for you — your property is the one issuing it, recording it, and reconciling it. Getting the process and the paper trail right matters more here than on a channel where the OTA manages the guest-facing side of a refund.
On an OTA, a refund to the guest often runs through the platform's own payment and cancellation flow, with the OTA handling at least part of the guest-facing process even when the property is the one approving it. On a direct booking made through your own engine, your property is handling the full chain — confirming the cancellation policy applies, processing the actual payment reversal through whichever gateway or method took the original payment, and recording all of it correctly in your PMS. There's no second system quietly handling part of that for you.
This isn't a reason to avoid direct bookings — it's a reason to have a clear, repeatable refund process for them rather than figuring it out fresh each time one comes up.
The most common failure is a refund approved verbally or by email that never gets processed through the actual payment method, leaving the guest waiting and your records inconsistent with what was promised. The second is a refund processed correctly in the payment system but never reflected back in the PMS reservation record, so the booking still shows as a full-value stay when finance reviews it later. A third is applying the wrong cancellation policy — checking the booking's actual rate plan and its specific refund terms rather than a general policy that may not apply to that particular rate.
Start by pulling up the exact rate plan the reservation was booked under and reading its stated refund or cancellation terms, rather than applying your property's general policy from memory. Process the refund through the same payment method that took the original payment, since that keeps the guest's statement clean and avoids a mismatch between what was charged and what was reversed. Update the reservation record in your PMS immediately afterward, noting the refund amount and date, so anyone reviewing that booking later sees the complete picture rather than a stay that looks fully paid.
Activity history keeps a record of who changed what on a reservation, including cancellations and refund notes, kept for a meaningful window — so a refund that was approved, processed and recorded is traceable later instead of relying on someone's memory of what happened. This covers record-keeping for refunds you issue; Prime Host itself does not process or guarantee refunds on your behalf. If keeping a clean trail on direct-booking refunds has been a gap before, that activity record is the structural fix — the public demo at try.primehostpartners.com is open to try without signing up.