Blog›Pricing

OTA Payment Status Mismatch: Extranet vs. Front Desk on Prepaid or Pay at Hotel

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.

The Prime Host Partners team16 Nov 2026 · 7 min read

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.

Full guide on this topic
Why payment status confusion happens at check-in

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.

Where the payment status actually lives

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.

Before charging or not charging a guest
1The OTA extranet's own payment fieldThe authoritative source for whether a booking was marked prepaid or pay-at-hotel at the time it was made.
2Whether a prepaid charge actually succeededA booking can be marked prepaid while the platform's charge to the guest's card failed or is still pending.
3Whether a modification changed the arrangementA date change or added night can alter what's owed without the front-desk note being updated to match.
How to check it properly before check-in

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.

Prepaid and paid are not always the same word on every platform — checking which one the extranet actually means is worth thirty seconds before a card gets charged twice.
Building this into a check-in routine
Read the reservation's current payment status directly from the OTA extranet at or just before check-in, not from an earlier note.
For prepaid bookings, confirm the charge actually succeeded rather than assuming the prepaid label guarantees it.
Check whether a modification happened after the original booking that could have changed the payment arrangement.
If status is genuinely unclear, ask the guest to show their booking confirmation rather than guessing either direction.
Flag any booking where your PMS and the extranet show different payment statuses, so the mapping issue gets investigated, not just this one guest.
How Prime Host stops this from happening again

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.

Frequently asked
How can I tell if a prepaid booking's charge actually succeeded?
Check the specific reservation in the OTA extranet — most platforms show whether a prepaid charge was successfully processed, separately from the prepaid label itself, since the two aren't always guaranteed to match.
What should front desk do if payment status is unclear at check-in?
Ask the guest to show their booking confirmation rather than guessing, and treat it as safer to verify than to charge a card that may already have been billed.
Can a booking modification change whether it's prepaid or pay-at-hotel?
Yes — a date change or added night can alter the payment arrangement, and the updated status may not reliably reach every note your front desk relies on, so the extranet is the safer source to check.
Want to see all of this working for real?
Walk through the actual system in read-only mode. Nothing to fill in.

Read next

© 2026 Prime Host Partners
Privacy PolicyTerms of Service