This new feature streamlines payment processes for multi-property customers by allowing them to utilize a single payment token across various locations, provided they are located in the same region. This enhancement not only simplifies financial operations but also enhances the guest experience by facilitating seamless transactions across properties. 

Key Benefits:

Unified Payment Processing: Operators can now manage payments more efficiently across multiple properties without the need for separate tokens for each location.

Enhanced Guest Experience: Guests can enjoy a more seamless payment process when interacting with different properties under the same enterprise owner.

Operational Efficiency: Reduces administrative tasks associated with managing multiple payment tokens, allowing staff to focus more on guest services.

An Inclusive Package Component set with Per Person Fees will use the number included for each Guest Type to determine how to apply the charges on the Reservation Account. We have improved this feature by allowing users to exclude all pax of a particular guest type by setting the number to include as 0. 

Help article

Hold Amount on an Owner gives the ability to hold back money from being paid out to an owner to cover future expenses. We have improved this feature to allow users to remove the hold back amount from an old owner to allow them to be paid out their remaining funds.

Help article

We’ve resolved the issue where payments made through the Guest Portal using the RMSPay gateway were not processing in the PMS. All transactions are now processing correctly.

No further action is required, but we recommend reviewing recent transactions to ensure everything is in order. Thank you for your patience while we worked on this.

We’ve resolved two issues in the Guest Portal to ensure accurate booking and compliance with property rules:

Correct Additional Guest Rates:

The Guest Portal now accurately reflects additional guest charges based on the rate table.

Max Pax Limit Enforcement:

The maximum occupancy (Max Pax) limits are now correctly enforced at the rate type level. Guests can no longer add more occupants than allowed per the rate table, maintaining consistency with property policies.

These updates improve pricing accuracy and booking reliability.

We are pleased to inform you that the issue affecting PayPal transactions in the Guest Portal has been resolved. What was the issue? When payments were made using PayPal via the Guest Portal, the transactions were not being assigned the correct card type. This was limited to Guest Portal transactions only, as payments via the IBE were functioning correctly. What’s been fixed? PayPal payments made through the Guest Portal now correctly display the card type as "PAYPAL." This aligns the Guest Portal functionality with the existing behavior for payments via the IBE. We’ve ensured that all payments processed through Windcave are consistent across platforms. Why is this important? This update improves the accuracy of payment records and ensures a seamless and reliable experience for our users. What does this mean for you? If you’ve experienced any issues or inconsistencies in payment records, you can now rest assured that all future PayPal payments via the Guest Portal will be accurately processed.