Payments and administration

Why is an OTA virtual credit card declined, and when can my hotel charge it?

A failed virtual card payment needs a targeted check. Use this sequence to establish what your hotel can collect, resolve the cause and hand over a useful support case.

Quick answer

An OTA virtual credit card can be declined because it is not yet chargeable, has insufficient funds, uses a different currency or is restricted for your merchant account. First check whether a payment already succeeded. Then compare the latest OTA payment instructions with the attempted transaction. Charge only within the permitted window and amount; resolve the cause before retrying, and escalate unclear results.

When can your hotel charge the card?

Use the activation date, funding status and collection deadline for the specific reservation. Neither the guest’s arrival nor a visible card number alone establishes permission to charge. Booking.com’s VCC documentation distinguishes cards awaiting activation, activated but unfunded cards, and cards ready to charge. It also distinguishes the OTA’s deactivation date from the card issuer’s expiry date.

Read the latest reservation payment instructions after an amendment or cancellation. Booking.com’s UK accommodation terms tie virtual cards to the assigned reservation, amount and currency. Do not turn a rule from one OTA or contract into a universal check-in or check-out rule.

Check a declined VCC in this order

Assign one person to investigate and pause competing manual attempts. A timeout or pending response needs a status check with the processor before another charge.

Safe checks before another payment attempt
CheckCompareNext action
1. Previous attemptProcessor reference, status and payment record in the PMS.Resolve pending, authorised or captured payments before creating another transaction.
2. Correct card and windowBooking reference, latest card, activation, funding and collection deadline.Wait if not chargeable; ask the OTA about closed or expired cards.
3. Available amountOTA amount authorised for collection, remaining funds and earlier charges.Investigate differences; do not keep trying smaller amounts to discover a balance.
4. Currency and changesRequired charging currency, amended stay and excluded extras.Use current OTA instructions, not an old confirmation or the entire guest folio.
5. Card data and merchant setupSecurely stored details, processor response, permitted transaction type and merchant category.Ask your processor to check acceptance restrictions; never invent billing details.
6. Retry permissionSpecific decline reason and processor or issuer retry advice.Retry only after correction and when permitted; otherwise escalate.

Merchant restrictions are a separate issue from available funds. For example, HBX Group’s VCC guidance requires a hospitality terminal classification and the contract currency. It also warns that premature attempts may block a merchant code.

A generic decline is not a diagnosis. Adyen’s refusal documentation separates insufficient balance, invalid card details, restricted cards and transactions not permitted for a merchant or terminal. Its raw response guidance includes both timed retries and instructions not to retry. Follow your own processor’s response.

Illustrative example: a shortened stay

A fictional York guesthouse tries to collect £360 from an OTA card. The stay has been shortened, and the latest OTA instructions specify £270 in GBP. The card is active, with £270 available and no earlier successful or pending charge. A separate £30 parking bill is outside this payout.

  1. Confirm the amendment in the OTA record and correct the stale £360 payment request in the PMS.
  2. Verify that £270 is the amount currently authorised for collection. The £90 difference is an amendment, not a reason to chase the guest.
  3. If the processor permits a corrected attempt, collect £270 and check the resulting transaction status. Handle parking separately under the agreed guest terms.

£360 − £90 = £270. The separate £30 does not increase the VCC instruction to £300. These are fictional payment figures, with no additional VAT or commission calculation; they are not a RoomRaccoon quote.

Escalate with evidence, not repeated attempts

Contact the OTA for activation, funding, reservation changes or card replacement. Contact your payment processor for transaction status, decline interpretation or merchant restrictions. Involve the PMS provider if OTA details are missing or inconsistent. Give the case one owner and record the next review time.

  • Property and OTA booking references; relevant amendment or cancellation.
  • Attempt date, time and time zone; amount and currency; processor transaction reference and exact decline code.
  • Displayed activation date, available balance, collection deadline and previous payment status.
  • Masked card identifier only, plus redacted evidence through the provider’s approved support channel.

Do not include a full card number or security code in an ordinary email, screenshot or demo request.

Make the workflow testable in a RoomRaccoon demo

When evaluating integrated hotel payments, ask how your team identifies a declined VCC, verifies the underlying response and follows the case to completion. RoomRaccoon’s help documentation describes VCC charging through RaccoonPay and requires booking channels to deliver card details. It also describes exceptions for cancelled reservations and cards received after the scheduled charging run.

For your UK property, confirm the supported payment provider, OTA connection, package or upgrade requirements, fees and refund permissions. Have the demonstrator show an amended booking, an uncertain payment result and a failed automatic charge. Ask which VCC fields update and which checks remain manual. Separately establish whether reconciliation covers only processed card payments or also external OTA bank payouts.

Bring a redacted version of your own declined-card scenario. Ask: “How would my team detect the changed amount, prevent another attempt while the result is uncertain, and escalate the exception?”

Explore virtual card management in a demo

Questions after a VCC decline

Should I charge the guest instead?

A declined OTA card does not establish that the guest owes the accommodation charge. Verify who collected payment. HBX explicitly tells hotels not to charge guests again for the covered booking; distinguish any genuinely unpaid extras.

Can I test the card with a pre-authorisation?

Do not use a test hold as your default diagnosis. Expedia’s official documentation states that its virtual cards do not need pre-authorisation. Check the instructions for the particular card and processor.

What if the booking is cancelled after I charged it?

Confirm the refund decision and follow the OTA’s current repayment instructions. Booking.com’s UK terms distinguish money already transferred to the property from money not yet transferred. Do not independently refund the guest as well as the OTA, or assume cancellation reverses a captured payment.

Does a zero balance mean I was paid?

No. Check card status and transaction history: zero funds alone do not distinguish an unfunded card from a completed collection. Match the processor’s payment evidence to the booking before closing the case.

Sources and scope

Checked on 10 November 2026. Apply the current instructions for your reservation and payment provider.