How to charge a Booking.com virtual credit card, and when you cannot

How do I charge a Booking.com virtual credit card?

You charge it the way you would key in a card a guest read out over the phone, for the exact amount shown, inside the window Booking.com set on that one card. A virtual credit card is a card number Booking.com creates for a single reservation, loaded with that booking's money, usable only by you and only up to the loaded amount. The activation date is the first day that number will authorize anywhere.

Whether to take the guest's card yourself in the first place, on your own checkout, is a separate decision. I have covered it elsewhere: what it costs to build your own Stripe checkout for direct bookings at a small hotel, B&B or serviced apartment, and whether it is worth building at all.

1. Open the reservation and read the activation date first. Booking.com's own guide to virtual credit cards walks through charging one in the extranet or on a card machine, and the reservation page carries that date, which determines when a charge will succeed.
2. Charge the exact amount loaded on the card. Your own system may show a different balance for what the guest owes; ignore that number. Guesty's documentation for Booking.com virtual cards puts it plainly: "Guesty charges the exact amount provided by the channel, not the reservation balance." Ask for a cent more and the whole charge fails.
3. No card machine? Charge it where your bookings live. Beds24's Stripe page and Booking Automation's Stripe wiki both document charging platform virtual cards automatically the moment they turn valid, and both warn you about the same Stripe setting, further down this page.
4. If it declines, read the decline text rather than the amount. Booking.com publishes the message an early attempt returns: "Don't honor/the VAN can't be authorized prior to activation date," where VAN just means the card number itself. That message means you tried before the activation date opened. The card is fine and your account carries no fraud flag.
5. Come back for the rest if you need to. Booking.com confirms one card can be charged several times in part amounts until the balance reaches zero, so a split deposit and balance works once the card is open.

When is a Booking.com virtual card actually chargeable?

The first chargeable day is the one Booking.com stamped on that card. The booking has to land first to put money on the card. Then Booking.com has to lift its own lock, and that runs on a clock Booking.com controls. Which clock you are on depends on your rate plan and your invoice history with them. Every row below is from Booking.com's virtual credit card page except the two marked, which are Cloudbeds myallocator's. SuperControl confirms it from the other side: the window belongs to Booking.com, and its system will not let you take more than the loaded amount.

checked on October 2026

A guest on a free-cancellation rate who books in March for August therefore sits behind a card you cannot touch for months, and on a Pay Later booking Cloudbeds' myallocator documentation quotes the message hosts get, that the card has no funds because the guest chose to pay later. What Booking.com does do early is check the card: its Payments by Booking.com guide says it validates the guest's credit card on your behalf on non-prepaid reservations, handles cancellation and no-show fees you are owed, then sends the funds after check-out by bank transfer or virtual card. None of that money is yours before check-out, and a no-show before then costs you the full stay.

The four things that move you to the earlier window

Booking.com grants early charging to properties with a clean record, and publishes the test. You can charge the moment a reservation becomes non-refundable if you:

• paid every invoice on time for the last 12 months;
• have no virtual card refunds sitting past their due date;
• have paid at least one commission invoice, with validated guest stays and reviews;
• were never closed for fraud on the platform.

Eligibility gets reviewed every four months and you are emailed when it changes. There is no switch to turn it back off: I went looking on 4 October 2026 and found only the criteria, so a property that would rather keep refundable bookings on the later window has nothing to click.

What our own cards did, and why yours may not match

I own MINT @Naschmarkt with Maxine: 18 serviced apartments in Vienna, sold on the same platforms you sell on. Across about 10 Booking.com cards we followed at MINT, the money came off 2 to 5 days before check in. It came off at the time of booking only once, an outlier among the ten. We are in Austria, and our Booking.com contract leaves our own prices alone in a way a US or Canadian contract usually does not, so check your own activation dates against this pattern instead of expecting your numbers to match ours. Charge date, check-in date and payout date were three different days on every one of them, and the rest sits in the MINT case, the numbers with their caveats.

Can I charge a Booking.com virtual card on my own Stripe account?

Yes, after the activation date, and only if Stripe has your account filed under accommodation. A merchant category code is the four-digit label your processor puts on your business so the card networks know what you sell. Stripe's own merchant category list shows 7011 as Hotels, Motels, and Resorts, and that code is the gate.

Sirvoy's guide to charging virtual cards with Stripe is blunt about why: "Because of the nature of Booking.com's and Expedia's Virtual Cards, they are not automatically accepted by Stripe, therefore they are not automatically saved either." Its fix is to email Stripe and ask for code 7011, and Booking Automation's wiki and Beds24's carry the same instruction. Three things still kill a charge with the code set right:

• You went a day early. ChargeAutomation's page on Stripe declining virtual cards says most of these cards are locked until a specific date, usually check-in or the day the booking becomes non-refundable, and charging or even authorizing one a day early returns a Stripe decline.
• Your account asks for 3D Secure. The same page notes many virtual cards do not support it, and there is nobody behind the card to approve a text message or an app prompt.
• The card may belong to Agoda instead of Booking.com. Sirvoy's current wording, as of October 2026, is that cards starting with 553397 cannot be charged with Stripe at all and you will need another payment method.

Our own property system at MINT wanted 1% of every card payment it handled, which is one reason guest cards there run through a Stripe account in our own name rather than the system's managed one. The same trade is in Cloudbeds Payments versus your own Stripe account and in Mews Payments versus Stripe: whoever holds the merchant account takes a cut before you see the money. Whoever holds it, the activation window stays Booking.com's.

Can I move a Booking.com booking off virtual cards and take the guest's card myself?

Sometimes you can, and the four routes below are nowhere near equally priced.

checked on October 2026

Option 1 is free, so try it first. Sirvoy's explainer on virtual cards notes that Booking.com only collects payment and sends card details if alternative payment methods are switched on in your account. I could find no self-service way on Booking.com's own pages to decline the cards short of leaving Payments by Booking.com, so treat this as a phone call whose outcome nobody documents.

Option 2 is the paid version of the same relief. Booking.com offered to handle the money for our apartments at 1.1% to 3.1% on top of the commission we already pay, which applies per property, all or nothing; MINT did not adopt this option. You stop chasing cards and watching activation dates, and pay on every platform booking from then on. If a bookkeeper is keying cards two hours a week, that may still be the better buy.

Option 3 is the one I would pick if anyone technical is within reach: set the code, let your property system charge on the activation date, and the money lands in your own account. It also leaves you holding the merchant relationship, which matters on the day a charge is disputed. Stripe versus Lodgify Payments covers what you give up when the property system holds the account instead.

Option 4 is where most operators end up, and not every system can do it. A host who takes guest payments directly wrote on Hospitable's own community forum in March 2026 that her old property system charged every guest at booking, the new one does not, and her bookkeeper now keys cards by hand. Hospitable's community manager Petra Podobnik confirmed it on the thread: "Hospitable does not currently support automated charging of Booking.com guests. When a property is connected to Hospitable as a channel manager, Booking.com's Virtual Credit Card (VCC) data is not accessible through Hospitable (we receive a raw token but can't pull the VCC details yet)."

What does it cost to charge a virtual card?

The cost runs from nothing extra to roughly three times a normal card fee, depending on who processes it. Tab is the only provider here that publishes a virtual card rate separately from its ordinary one.

checked on October 2026

The Tab figures come from its own page on taking platform payments with virtual cards. Put them on a real stay: three nights at $540 costs $43.66 to collect from the virtual card and $16.66 from the guest's own card on the same provider. The gap is $27.00 on one booking, and thirty of those in a season is $810 you never see as a line item, because a processing fee comes off before the money arrives.

I checked Guesty's, Cloudbeds myallocator's and SuperControl's virtual card pages on 4 October 2026 and none says what a virtual card charge costs through its own payment path. If you are on one of those, the number is in your contract, so ask for it. The same goes for the figure underneath all of this: Booking.com publishes no commission rate on any partner page, and the page meant to answer it would not load when I tried on 4 October 2026, so anyone quoting you one number for your own commission is guessing.

What a refund takes back out of your account

A refund on a card you already charged has a deadline: 45 days from the first refund reminder email, after which Booking.com raises a chargeback and takes the money itself. The clock starts at that email, so if it goes to an address nobody reads, the first you hear of it is the chargeback. Two more things about the back end of these cards:

• You cannot top one up. It is loaded once, and nothing adds funds back.
• It may be dead before you find the damage. ChargeAutomation notes that once check-out passes these cards are often deactivated or the balance wiped, so a later charge for a broken lamp declines. Collect for damage on something else.

Price this into your cancellation terms, because the platform keeps its cut on a refunded booking, and your processor keeps its percentage on the original charge too. Ask your own processor whether it returns the fee on a refund. Ours does not, and most do not.

If you would rather not handle these cards at all

A booking taken on your own website arrives as a payment on your own account, on the day you set, with the guest's own card stored for the balance: no activation window, no 45-day refund clock, no card expiring 12 months after check-out. We build that kind of site. Run your own numbers through the commission savings calculator, then Book a call and bring the last three Booking.com reservations you had to chase.