Blog›Basics

Booking.com Payment Options for Properties: Collect Yourself vs. Payments by Booking.com

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.

The Prime Host Partners team13 Nov 2026 · 7 min read

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.

Full guide on this topic
The two payment models, in plain terms

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.

Why confusing the two models causes problems

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.

What to check per reservation
1Which model this specific booking falls underCheck the reservation details in the extranet rather than assuming it matches your property's usual setup.
2Whether a virtual card is presentA virtual card to charge usually signals the collect-yourself model; its absence usually signals Booking.com-processed payment.
3Who should issue a refundDepends on who processed the original payment — check before assuming it's always the property's responsibility.
How to confirm which model a reservation is using

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.

The payment model isn't a detail to assume from habit — it's the one thing a reservation can quietly be different about from the last ten that looked just like it.
Handling both models without confusion
Check the specific reservation's payment details in the extranet rather than assuming it matches your property's usual setup.
Treat the presence of a virtual card as a signal for the collect-yourself model, and its absence as a signal for Booking.com-processed payment.
Confirm who should issue a refund for a given reservation based on who actually processed the original payment.
Train front desk staff to check the payment model per booking rather than applying one process to every reservation by default.
If a payout seems to be missing, confirm the reservation wasn't actually set up for you to collect directly before escalating.
How Prime Host stops this from happening again

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.

Frequently asked
How do I know if I'm supposed to charge the guest's card myself on Booking.com?
Check the specific reservation in the extranet — a virtual card presented for you to charge indicates the collect-yourself model; its absence usually means Booking.com processed the payment directly.
Can the payment model differ between reservations at the same property?
Yes — it can vary by market or promotion type even at a single property, which is why checking each reservation individually is worth doing rather than assuming a single default.
Who issues a refund if Booking.com processed the original payment?
Generally Booking.com, since it held the guest's payment — check the specific reservation's payment model before assuming the refund is the property's responsibility.
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