The extranet says a booking is prepaid while the front desk is about to charge the guest again, and this explains how to check payment status before money changes hands twice.
A guest checks in, and your front desk is unsure whether the OTA already collected payment or whether it's due on-site, because what the reservation note says and what the extranet actually shows don't agree. Getting this wrong in either direction is costly — charging a guest who already paid, or letting a pay-at-hotel guest leave without paying — so it's worth a clean way to check before assuming either status is correct.
Many OTAs support both prepaid bookings, where the guest's card was charged by the platform at the time of booking, and pay-at-hotel bookings, where the property collects payment directly. The reservation that reaches your PMS should carry that distinction, but the label can be missing, outdated, or simply not surfaced clearly on the screen your front-desk staff actually look at during check-in. When that happens, staff either guess, ask the guest — which is awkward if the guest already paid — or default to charging again, which is the expensive mistake.
This is distinct from a pricing mismatch. The rate can be entirely correct while the payment status attached to it is wrong or unclear, and the two problems need different checks.
The OTA extranet holds the authoritative version of whether a booking is prepaid or pay-at-hotel, along with, for prepaid bookings, whether the platform has actually processed that charge successfully. Your PMS is supposed to receive and store that same status as part of the reservation, but depending on how your channel manager maps incoming bookings, that field can be dropped, defaulted incorrectly, or displayed in a way that front-desk staff don't immediately recognize as the payment instruction it is. A booking modification — a date change, an added night — can also change the payment arrangement without the updated status reliably reaching your PMS.
Open the specific reservation directly in the OTA extranet and read its payment field as it currently stands — not the note on the original booking confirmation, since a modification can have changed it since. If the booking is marked prepaid, check whether the extranet shows that charge as successfully collected rather than assuming prepaid means paid; some platforms distinguish between the two. Only once you've confirmed the current, authoritative status should front desk decide whether to collect payment, and if there's any doubt, it's safer to ask the guest to show their booking confirmation than to charge twice or let a payment slip.
Prime Shield is built for the money side of this problem — it compares the rate you sent, the rate you intended, and what the guest actually paid, and flags any gap worth more than 5% in plain money, which catches a prepaid charge that never actually went through as well as a rate mismatch. Bank-level reconciliation adds the payout side for Booking.com specifically, matching payout batches against expected payment dates so a prepaid booking's money is tracked through to the bank, not just the reservation record. If payment status confusion keeps causing awkward moments at check-in, that combination is the structural fix — the public demo at try.primehostpartners.com is open to try without signing up.