Missing Payment Options Are Costing Hosts Bookings, Booking.com Finds

Nearly two-thirds of UK accommodation professionals say they have lost a booking because a guest couldn't pay the way they wanted to, according to new research commissioned by Booking.com. For hosts and property managers who still route every payment through a single card processor, that's a direct case for auditing what happens in the final seconds before checkout.
What the research actually claims
Booking.com says its survey found around 65% of accommodation professionals have seen guests drop out of a booking when their preferred payment method wasn't available. The company has not published the full sample size, the mix of property types surveyed, or the exact wording put to respondents. That matters, because self-reported recall of lost bookings is a perception metric, not a measured conversion rate pulled from transaction logs. Treat the figure as a signal worth acting on, not a precise industry benchmark.
Why payment friction hits rentals harder than hotels
Short-term rental guests are more international, on average, than a typical hotel's local or domestic mix, and payment habits vary sharply by market. A Dutch traveler expects iDEAL. A Belgian guest may look for Bancontact. Swiss travelers increasingly use Twint, and buy-now-pay-later options such as Klarna have become a default expectation for younger UK and European bookers rather than a nice-to-have. A host or manager whose booking engine only accepts Visa and Mastercard is filtering out guests before they ever reach a confirmation page, and the drop-off happens silently: there's no complaint email, just an abandoned cart.
Direct booking sites are the most exposed. OTAs like Booking.com and Airbnb already support a wide range of local payment rails on the guest's behalf, which is part of why they convert well.
What operators should actually check this week
Start with the processor settings, not the website design. Most hosts never look past the default payment methods a platform ships with. Checking which local wallets and bank-transfer options are enabled, and whether they match the top origin countries in last year's guest list, costs nothing and takes an afternoon.
Second, strong customer authentication under the EU's PSD2 rules already adds a verification step to many European card payments; stacking a second point of friction, such as a payment method the guest doesn't recognize or trust, compounds the drop-off risk rather than offsetting it. Property managers running multi-country portfolios should treat payment configuration as a per-market setting, not a single global default.
Third, adding payment methods isn't free. Buy-now-pay-later providers typically charge merchants a higher percentage fee than standard card processing, and some bank-transfer rails carry slower settlement times that affect cash flow for operators running tight margins between a confirmed booking and the cleaning and maintenance costs it triggers. The decision to add an option should weigh the conversion upside against the processing cost and settlement delay, not assume more options is automatically better.
What comes next
Booking.com has its own payment processing product, Booking.com Payments, which it has been expanding to properties that book through the platform, and this research reads as groundwork for pushing that further. Hosts should expect more messaging from major OTAs framing payment flexibility as a competitive feature over the next few quarters, often alongside a pitch for the platform's own processing tools. The practical test for any operator is simpler than the marketing: pull last year's booking data, check which countries guests traveled from, and confirm the payment stack actually covers what those guests use at home.
Newsletter


