Summary

This Live release brings together the improvements, fixes, and new features previously delivered across the Beta cycle, spanning error handling improvements, notes management enhancements, guest classification management, reservation reliability fixes, and new headless payment tokenisation support.

Included in this Live release:

• Error Handling & HTTP Status Improvements Fixes to incorrect HTTP status codes returned during transient errors in payment processing, and resolution of a 500 error on the NPS Results Report endpoint in Beta and Test environments. 👉 Beta details: https://releasenotes.rmscloud.com/rest-api-v10.26.65.2----beta-S8aju
  
  
• Company & Travel Agent Notes — All Properties Support New support for creating and updating notes scoped to All Properties for company and travel agent records via propertyId: 0, aligning API behaviour with the RMS UI. Validation added to PUT requests to enforce scope consistency. 👉 Beta details: https://releasenotes.rmscloud.com/rest-api-v10.26.77.4----beta-XO8UM
  
  
• Guest Classifications, Reservation Fixes & Stability Improvements New guest classification endpoints, a fix for dynamic pricing rate consistency on pencil reservations, and a fix for a 404 error incorrectly returned when creating reservation holds. 👉 Beta details: https://releasenotes.rmscloud.com/rest-api-v10.26.90.1----beta-104VXi
  
  
• Guest Classifications, Company Branch Offices & Credit Card Tokenisation New endpoints for managing company branch office relationships, and a merchantReference field for headless payment tokenisation via POST /guests/{id}/creditCard. 👉 Beta details: https://releasenotes.rmscloud.com/rest-api-v10.26.105.2----beta-4BL7va
  
  
• Availability & Rate Calculation Enhancements Improvements to availability and rate calculation workflows, along with new API support for managing guest correspondence notes. 👉 Beta details: https://releasenotes.rmscloud.com/rest-api-v10.26.10.1----beta-3ECvn2
  
  
• Reservation Workflow Fixes & Stability Improvements Fixes to reservation creation and update workflows, ensuring rate-based configuration fields are correctly applied and resolving timeout issues when overriding rates. 👉 Beta details: https://releasenotes.rmscloud.com/rest-api-v10.26.19.2----beta-1eL7Q4

Notes

• This release is now available in Live
• Release Date: April 22, 2026 (AEST)
• Partners can begin using these changes in production immediately
• ⚠️ Upcoming Breaking Change — June 2, 2026 (AEST): A global maximum record limit of 50,000 will be enforced across POST /transactions/allocations/search, POST /transactions/search, POST /guests/search, and POST /reservations/search. Requests exceeding this limit will return HTTP 400. If your integration requests more than 50,000 records in a single call on any of these endpoints, please reduce your limit or implement pagination before this date. https://releasenotes.rmscloud.com/rest-api-v10.26.105.2----beta-only-breaking-change---maximum-query-limit-4CTw1q
• Please report any issues through standard support channels: https://rmsapi.zendesk.com/hc/en-gb/requests

We've fixed an issue where some guests were seeing a "card type not supported" error when attempting to pay through the new Booking Engine, even when using a valid card. In some cases this also resulted in payment being taken without a receipt appearing in the reservation. Both issues have been resolved.

We've resolved an issue where a small number of bookings made through the new Booking Engine with RMS Pay were being processed and payment taken, but the booking wasn't being saved correctly in RMS - appearing as an abandoned quote with no receipt and the RMSPay merchant account showed the reference number as 'Undefined'. These bookings will now save and receipt correctly.

We've resolved an issue where guests completing a 3D Secure (3DS) payment challenge were not being redirected to the booking confirmation page successfully on the new Booking Engine for RMSPay customers. Guests will now land on the confirmation page as expected after completing their 3DS verification.

We've improved how the new Booking engine recognises accepted card types during checkout. Previously, cards set up in your RMS account using non-standard naming (such as "Vis Cred", "Visa Debit", or "M.Card debit") weren't always being recognised by the payment gateway, causing valid cards to be declined at the point of booking. This has now been resolved - a wider range of card naming conventions are supported, so guests experience fewer payment errors.

We've resolved an issue where some RazorPay bookings were not being confirmed after a successful payment.

What was happening? In certain cases, guests who navigated away, refreshed the page, or pressed the back button during the RazorPay payment process would have their payment processed but their booking not confirmed. This was because the frontend was not sending the final request to the booking confirmation API when the payment flow was interrupted by a page navigation.

What's been fixed? Guests are now kept on the payment processing page while their RazorPay transaction completes, preventing accidental navigation away before the booking is confirmed. This ensures the confirmation API is reliably called after a successful payment, so bookings are completed as expected.

Who does this affect? Properties using RazorPay as their payment gateway through IBE+.

Your guests can now pay with Apple Pay directly from the guest page- making checkout faster, more familiar, and more secure.

How it works

Apple Pay appears as a payment option on the guest page alongside existing methods. Guests on an Apple device can pay instantly. Guests on a non-Apple device will still see the option- they can select it and scan the QR code with their iPhone to complete the payment seamlessly.

Works just like your existing card payments

Tokens and receipts behave exactly the same as credit card transactions, so your team won't need to change a thing. That means:

• ✅ Refunds can be processed as normal
• ✅ Pre-auth tokens can be created for same-day arrivals
• ✅ All existing RMSPay workflows apply

A couple of things to know

Apple Pay will not appear as a payment option when a property's deposit rule is set to No Deposit & Tokenize. In that case, the option is automatically hidden - no action needed on your end.

Notifications triggered from the Guest Portal will no longer send email alerts to the primary admin user. 

All relevant notifications will instead be available within the Message Centre.

We have resolved an issue in the RMS Booking Engine (IBE+) where Google tag data was not being recorded upon booking confirmation.

Previously, Google tags were failing to fire on the confirmation page after a guest completed payment. This meant that transaction data - including booking conversion events - was not being captured in your connected Google Analytics account, resulting in incomplete or missing reporting data.

This issue has now been fixed. Google tags will fire correctly on the confirmation page, ensuring that all transaction and conversion data is accurately recorded as expected.

We have resolved an issue in the RMS Booking Engine (IBE+) where the Area URL modifier was not functioning correctly when check-in and check-out dates were not included in the URL.

Previously, when a guest landed on the booking engine via a URL containing only an Area parameter (without dates), the Area filter would be dropped once the guest manually selected dates and clicked Search - resulting in all categories being displayed rather than only those mapped to the specified area.

This issue has now been resolved. The Area filter will now persist correctly in both scenarios: when dates are included in the URL, and when a guest manually selects dates after landing on the page. Only categories mapped to the specified Area ID will be displayed, as intended.

If you have any questions or require further assistance, please reach out to our support team.