Software to Reconcile Booking.com Virtual Card Payments

HolsUK integrates with Booking.com through an official, secure API (Application Programming Interface) connection. Once you authorise the connection in your Booking.com extranet, our platform can programmatically and securely pull booking and payment information. This is a read-only process for sensitive data; we don't store the full VCC number on our servers. Instead, we retrieve the necessary details (last four digits, value, activation/expiry dates) and create a secure token to facilitate the payment via our integrated partner, Stripe. This direct line of communication means that as soon as Booking.com creates or updates a VCC for one of your bookings, the information is reflected in your HolsUK dashboard almost instantly. It’s a much more secure and efficient method than manually copying and pasting sensitive information, as it minimises the points at which human error or data exposure can occur. This API partnership is the foundation of our automated reconciliation capability.

A Booking.com Virtual Credit Card (VCC) is a temporary, digital-only Mastercard used to facilitate guest payments to you. When a guest books and pays online, Booking.com collects the money and loads it onto a unique VCC for that specific booking. They send you the details of this VCC instead of the guest's actual card. The primary reason for this system is security and payment guarantee. It guarantees you will be paid for your bookings (according to your cancellation policy) and protects you from fraudulent cards. For the guest, it means they don't have to share their personal card details with every property they book. The VCC has a specific amount loaded onto it and can only be charged on or after a set activation date, which is typically the guest's check-in day. This system, while secure, creates the administrative challenge that our software is designed to solve.

How a VCC is handled upon cancellation depends entirely on the cancellation policy you have set for that booking on Booking.com. If the guest cancels within a free cancellation period, the VCC will simply not be activated, and you will not be able to charge it. The booking will show as cancelled in HolsUK. However, if the guest cancels after the free cancellation period has passed and a fee is due, Booking.com will still activate the VCC for the amount of the cancellation fee. Your HolsUK dashboard will reflect this, showing the card as 'Ready to Charge' for the appropriate cancellation penalty amount. You can then charge it just like any other VCC. This is a key benefit of the VCC system: it guarantees your income from late cancellations without you needing to pursue the guest for payment directly. HolsUK accurately tracks these policy-based changes, ensuring you know when you are entitled to charge a cancellation fee.

HolsUK is an all-in-one platform designed to centralise your entire business, so it handles payments and payouts from all major channels, but each works differently. This specific automated VCC reconciliation feature is tailored for Booking.com's unique payment model. For Airbnb, you receive direct payouts to your bank account; HolsUK tracks these expected payouts and helps you reconcile them against your bank statement. For Vrbo, they often manage the payment collection and pay you out directly, similar to Airbnb. Our platform also tracks these payouts. The key is that HolsUK provides a single, unified revenue dashboard where you can see the income from Booking.com VCCs, Airbnb payouts, Vrbo payouts, and payments from your direct booking website all in one place. So while the reconciliation method is different for each channel, the end result is a consolidated financial overview within HolsUK.

Our goal is to reduce your time in the extranet by 90%, not eliminate it entirely. For day-to-day operations like checking new bookings, managing your calendar, updating rates, and communicating with guests, you can do everything from within HolsUK thanks to our two-way API connection. Specifically for payments, you will no longer need to log into the extranet to find and copy VCC details. However, there may be rare occasions where you need to access the extranet, for example, to manage property-level settings that are only available on Booking.com, to set up new promotions, or to handle a complex dispute that requires direct communication with their support team. Think of HolsUK as your central cockpit for 99% of your tasks, with the extranet being a tool you only need to access for specific, infrequent administrative functions. The VCC reconciliation process, however, is fully managed within HolsUK.

While rare, a VCC can sometimes be declined. The most common reason is trying to charge it before the activation date (usually 12:01 AM on the day of check-in). HolsUK's 'Ready to Charge' status helps prevent this. If a card is declined for another reason, the transaction will fail within HolsUK, and the VCC status will remain as 'Ready to Charge'. Your first step should be to double-check the activation date and the amount. If everything seems correct, the issue may lie with Booking.com's systems. In this case, you would contact Booking.com support directly through the extranet, providing them with the booking number. They can investigate why the VCC failed and, if necessary, re-issue it or provide an alternative payment method. HolsUK's clear logging helps in these situations, as you have a precise record of when you attempted to charge the card.