We’ve added Vault support to the new Booking Engine. Deposits are no longer accepted, but credit cards can still be captured and tokenized for future payments. If deposits are configured in the online options, the Booking Engine will now default to “No Deposit” and capture the card only.

We’ve resolved an issue where the last four digits of tokenized cards were not visible in 9+ when payments were processed through Windcave or Stripe. Tokenized card information will now display correctly, improving visibility for reporting and reconciliation.

We’ve fixed an issue where site categories could appear bookable even if the selected RV type or length did not match the property’s configured restrictions in 9+. Guests will now only see sites that meet the RV type and length requirements, preventing errors or invalid bookings.

We’ve fixed an issue where the cancellation policy on the confirmation page was hard-coded and not reflecting the property’s configured policy. The confirmation page now correctly displays the cancellation policy as set up in the property settings.

We’ve resolved an issue where IBE transaction reference numbers in Stripe were displaying in a new format that differed from the previous standard. Reference numbers will now return to the original format, ensuring accurate reporting, reconciliation, and transaction tracking.

We’ve improved the Booking Engine to clearly communicate when a minimum length of stay requirement prevents a booking. Guests will now see a clear message indicating the minimum stay required, helping them understand why no availability is shown. Flexible dates are not automatically extended.

We’ve resolved an issue where promo codes containing special characters such as # or & could return an “Invalid” error when creating, editing, or using the promotion. Promo codes can now include these characters without error.

We’ve added a mandatory GDPR consent checkbox to the Booking Engine Guest Page for properties with a privacy policy configured in 9+. The checkbox appears below the credit card fields and above the Confirm/Complete Booking button. Guests must tick the checkbox to complete their booking. The checkbox includes a link to the privacy policy and will not display if no policy is configured.

We’ve updated RMS Pay to be fully hosted directly on the Guest Page of the Booking Engine. Guests will now complete their payment without being redirected to an external payment shell, providing a more seamless and streamlined checkout experience.

We’ve resolved an issue where bookings with multiple add-ons displayed only one add-on and an incorrect total on the confirmation page and confirmation email. All selected add-ons and the correct total amount will now display accurately.