Booking.com offers more than one way for a property to actually receive guest payment, and choosing between them changes who handles the card and who handles the risk.
Properties on Booking.com can be set up to collect payment from the guest directly, or to have Booking.com process the payment and pay out the property afterward, and the two models work differently enough that mixing up which one you're on causes real confusion about cards, refunds and timing. This covers the practical difference and how to tell which one applies to a given reservation.
Under the collect-yourself model, Booking.com passes you the guest's payment details — often as a virtual card standing in for the guest's actual card — and your property charges it directly through your own payment terminal or gateway, the same way you'd charge a card for a direct booking. Under payments processed by Booking.com, the guest pays Booking.com directly at or around the time of booking, and the property receives a payout afterward rather than ever handling the guest's card.
Which model applies can vary by property, by market, or even by individual reservation depending on your setup, which is exactly why checking the specific booking rather than assuming is worth doing.
If a reservation is actually under payments processed by Booking.com but your front desk tries to charge a card as if it were the collect-yourself model, there's often no card to charge, or charging one that does exist double-charges the guest. The reverse causes a different problem — expecting a payout that isn't coming because the reservation was actually set up for you to collect directly, and the guest's payment was never routed through Booking.com's own processing at all. Refund handling also differs by model: who issues a refund and how depends on who actually processed the original payment.
Open the specific reservation in the Booking.com extranet and look for payment details — a virtual card presented for you to charge indicates the collect-yourself model, while a reservation with no card details and a note about Booking.com handling payment indicates the other model. If it's genuinely unclear from the reservation itself, your property's overall payment setup in the extranet's account settings should show which model your property is configured under, though individual bookings can still vary from the default depending on market and promotion type.
Bank-level reconciliation matches payout batches and computes expected payment dates for Booking.com, which gives you a clear structural answer to whether a payout should be arriving for a given reservation rather than guessing based on habit. Prime Shield adds a check on the price side, comparing the rate you sent, the rate you intended and what the guest actually paid, regardless of which payment model processed it. You can try both on the public demo at try.primehostpartners.com without signing up.