Declined Preauthorization Attempts for OTA Virtual Credit Cards (VCCs)

Article ID: WEA-934-EXP-VCC-001

Last Updated: 21/08/2025

Product: Juno Hospitality Suite

Overview

This article addresses the issue of declined preauthorization attempts when using an Expedia Virtual Credit Card (VCC) for a guest's reservation. Our Juno customers frequently report this problem.

The core issue:

OTA's VCCs are designed as a secure, single-use payment method that is not activated until a specific timeframe before a guest's arrival. When our system (or any other payment processor) attempts to perform a preauthorization before this activation period, the card is declined by the Acquirer (ACQ) because it is not yet active and cannot be charged.

Understanding the Process

Expedia Collect Bookings: When a guest makes a booking on Expedia and pays at the time of reservation, Expedia processes the payment and provides the hotel with a single-use Virtual Credit Card (VCC).

VCC Activation: OTA activates the VCC only once the cancellation window for the booking has closed. This window is determined by the cancellation policy attached to the rate plan configured in the PMS — not by a fixed timeframe before arrival. For example, a non-refundable rate may result in an active VCC shortly after booking, whereas a flexible rate with a 7-day cancellation window will keep the VCC inactive until that period has elapsed. This is a protective measure by the OTA: by withholding card activation until cancellation is no longer possible, Expedia ensures they cannot be charged for a reservation the guest could still cancel at no cost.

Preauthorisation Attempts: When you attempt to preauthorise the card for a security deposit or other charges before the VCC is active, the transaction fails. The PSP receives a "declined" response because the card is not yet valid for charging.

Common Errors

You may see a decline message in your Juno/Opera portal with a code indicating the card is inactive or has insufficient funds. This is a standard response for an inactivated VCC and does not mean there's an issue with the card details themselves.

Solution and Workaround

At the present time, the only guaranteed solution is to adhere to VCC activation policy. The workaround for our Juno customers is to wait until the guest's arrival is within the 48-hour window before attempting any preauthorization. This ensures that the VCC is active and the transaction will be successful.

Step-by-Step Guide:

1. Access the guest's reservation details in your system.
2. Check the guest's arrival date.
3. Do not attempt to preauthorize or tokenise the VCC until the cancellation window for the booking has elapsed. The activation point varies depending on the rate plan's cancellation policy — check the tariff conditions in your PMS to determine when the VCC is likely to become active.
4. If the preauthorization is still required, you can then process it through your Juno payment terminal.

Important Note: The VCC is specifically for the room and tax portion of the booking. Any additional charges, such as incidental fees, minibar usage, or resort fees, should be collected from the guest directly using their personal credit card upon check-in.

Permanent Solution: Juno Universal Token

For hotels running the Juno Hospitality Suite, the Universal Token feature provides a robust, automated solution that eliminates the manual workaround described above entirely.

How It Works

When the Universal Token is enabled, Juno tokenises the VCC at the point of reservation — regardless of whether the card is currently active or not. The token is securely stored within Juno's Universal Token Store and mapped to the guest's reservation in Opera. Once Expedia activates the VCC (i.e., once the cancellation window on the rate plan has closed), Juno automatically processes the preauthorisation or charge against the stored token without any manual intervention from the front desk team.

Key Benefits

• No timing dependency — the hotel no longer needs to monitor cancellation windows or wait for the right moment to attempt tokenisation.
• Fully automated — once configured, the process runs in the background without any front desk action required.
• Reduced decline rates — eliminates the acquirer-side declines caused by premature preauthorisation attempts against inactive VCCs.
• Consistent guest experience — payment processing proceeds seamlessly regardless of which rate plan or cancellation policy is attached to the booking.

How to Enable

To enable the Universal Token for your property, please contact the 934 support team via support@weare934.com or submit a request through the helpdesk console. Our team will confirm your current Juno configuration and enable the feature as part of your existing setup.

Note: The Universal Token is available to all Juno Hospitality Suite customers. No hardware changes or PMS reconfiguration are required.

Additional Information

We understand this may be an inconvenience for properties that require preauthorization well in advance of a guest's stay. Our development team is actively exploring potential solutions and integrations that could provide a more seamless experience for our customers, but this is a complex issue related to Expedia's security policies.

For any further questions or to report a related issue, please contact the 934 support team via support@weare934.com or visit weare934.com/support