Blog›Basics

Booking.com Virtual Credit Card Not Charging or Declined: What to Check

A Booking.com virtual credit card isn't charging, or it's being declined at your payment terminal, and this walks through what to check before contacting support.

The Prime Host Partners team13 Nov 2026 · 7 min read

Booking.com's virtual credit card is meant to let you collect payment for a reservation without holding the guest's real card details, but the card itself can fail to charge or come back declined when you try to run it. Before assuming the guest's booking is somehow invalid, it helps to work through the handful of reasons a virtual card specifically fails, since they're different from a normal card decline.

Full guide on this topic
What a failed virtual card charge looks like

You pull up the reservation, find the virtual card details in the Booking.com extranet, and attempt to charge it through your payment terminal or gateway the same way you would a guest's own card. The charge is declined, or the amount doesn't go through at all, even though the reservation itself is confirmed and the guest is expecting to pay through that method.

This is distinct from a guest's personal card being declined for insufficient funds — a virtual card's failure usually has a cause specific to how and when it's valid for use, not the underlying funds.

Why virtual cards fail to charge

A virtual card is typically valid only for the exact amount of the reservation, and only within a specific date window tied to the stay, so charging it too early, too late, or for the wrong amount can trigger a decline even though the card itself is fine. It's also usually single-use or limited to specific transaction types, so attempting to charge it twice, or running it through a terminal that isn't set up to accept virtual cards correctly, can fail for reasons that look identical to a normal decline but aren't. Occasionally the card details displayed in the extranet haven't finished generating or refreshing for that specific reservation, which produces a decline that has nothing to do with the guest at all.

Most common reasons a virtual card declines
1Wrong amount or timingVirtual cards are usually valid for an exact amount within a specific window tied to the stay — charging outside that fails.
2Already usedMost virtual cards are single-use; a second attempt to charge the same card for the same booking can be declined.
3Terminal or gateway mismatchNot every payment terminal is configured to accept virtual cards the same way it accepts a guest's own card.
How to check before escalating

Reopen the reservation in the Booking.com extranet and confirm the virtual card details currently shown — amount, expiry and any usage note — match exactly what you're trying to charge, since these can refresh or change. Confirm the date you're attempting the charge falls inside the valid window for that reservation rather than before check-in opens or after it's closed. If the amount and timing both look correct and the charge still declines, check with your payment processor whether their terminal is configured to accept this type of virtual card correctly, since not all are by default.

A declined virtual card is rarely about the guest's money — it's almost always about charging the right amount, in the right window, through a terminal that knows what kind of card it's looking at.
Avoiding repeat declines
Confirm the exact amount and valid date window shown for the virtual card in the Booking.com extranet before attempting to charge it.
Check whether the card has already been successfully charged once, since most virtual cards are single-use.
Confirm your payment terminal or gateway is configured to accept Booking.com's virtual card format correctly.
If the charge still fails, contact Booking.com support with the reservation ID and the exact decline message from your terminal.
Keep a note of which terminals or gateways at your property reliably accept virtual cards, if you operate more than one.
How Prime Host stops this from happening again

Bank-level reconciliation keeps track of the payout side of Booking.com reservations, including how payment batches and expected payment dates line up, so a virtual card issue doesn't also turn into a payout mystery later. Pairing that with Prime Shield, which compares the rate you sent, the rate you intended and what the guest actually paid, means a payment problem shows up as a flagged discrepancy rather than something you have to notice on your own. You can try both on the public demo at try.primehostpartners.com without signing up.

Frequently asked
Why would a Booking.com virtual card decline if the guest definitely has funds?
Virtual cards are usually valid only for an exact amount within a specific date window and are often single-use, so a decline is more often about those limits than the guest's actual funds.
Can I charge a virtual card before the guest checks in?
Only within the valid window shown for that reservation in the extranet — charging too early is a common reason for a decline that has nothing to do with the guest.
What should I do if a virtual card keeps declining for no obvious reason?
Confirm the amount, window and whether it's already been used, then check with your payment processor whether their terminal is configured for this card type before escalating to Booking.com support.
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