Rules for Virtual credit cards VCC
The core issue is simple: VCCs are still not handled separately.
In Europe, each reservation has its own VCC. Treating them the same as guest cards forces unnecessary manual work.
What’s missing:
A distinct VCC card type
Auto-charge by rate type, not deposit logic
Non-refundable → charge at booking
Standard → charge on a set date (e.g. arrival)
Applied to the full reservation balance
Until this exists, the pilot feature does not solve VCC handling.
Please advise if this is planned
Hello,
We have recently released this functionality - see more details here. Hope this helps! https://stayntouch.freshdesk.com/support/solutions/articles/24000098324-stayntouch-pms-release-notes-v5-96-#8.-Auto-Charge-Routed-Deposits%3A-Virtual-Card-Setup-&-Copy-Information-On-Routed-Bill-From-Billing-Information-(In-Pilot)
Also requested by Zoku Hotels
Also requested by Village Hotels
3 people like this idea
Current Situation: Our system currently applies uniform charge/no-charge rules to all credit cards. However, VCCs are unique because they present no risk of chargebacks. Additionally, VCCs can be charged using MOTO (Mail Order/Telephone Order) without any risk, ensuring that the payment is always guaranteed. VCCs can be easily identified as the cardholder name is typically the OTA (Online Travel Agency).
Feature Request: To optimize our handling of VCCs, I would like to request the following options be added to the system:
These enhancements would streamline our billing process, reduce manual intervention, and ensure a more efficient operation.