Check out the latest features, improvements, and product updates from RMS
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.
This release introduces a platform-wide maximum record limit of 50,000 across all REST API endpoints that accept a limit parameter. Requests exceeding this value will now return HTTP 400 Bad Request. Previously, oversized requests were silently truncated.
Partners using high-volume search queries should review the affected endpoints below and update their integrations before the Live release.
Global Maximum Query Limit — 50,000 Records
The following endpoints are affected:
POST /transactions/allocations/searchPOST /transactions/searchPOST /guests/searchPOST /reservations/searchWhat's changing:
limit value above 50,000 will return HTTP 400 Bad Request with an explicit error messageAction required: If your integration passes a limit value greater than 50,000 on any of the above endpoints, you will need to update your queries to use pagination or reduce the limit before the Live release. Partners identified as impacted have been contacted directly.
This Beta release introduces three new feature areas — guest classifications, company branch offices, and headless payment tokenisation — along with a platform-wide query limit change. Partners using high-volume search endpoints should review the Breaking Change section below ahead of Live.
New endpoints have been added to support full management of guest classifications, enabling retrieval, assignment, replacement, and removal of classifications on a guest record.
New endpoints:
GET /guestClassifications — Retrieve available classification typesGET /guests/{id}/classifications — Get classifications assigned to a guestPOST /guests/{id}/classifications — Add a classification to a guestPUT /guests/{id}/classifications — Replace the full classification set for a guestDELETE /guests/{id}/classifications/{classificationId} — Remove a specific classification from a guestNew endpoints have been added to support programmatic management of branch office relationships between company records. This removes the need to maintain these links manually in the RMS UI.
When adding branch offices, you can optionally copy all assigned rates from the master company to each branch office at the time of creation by passing "assignParentRates": true. Note: rate copying occurs at creation time only and does not establish an ongoing sync.
New endpoints:
POST /companies/{parentId}/branchOffices — Link one or more companies as branch offices of a master companyGET /companies/{parentId}/branchOffices — Retrieve all branch offices for a master companyDELETE /companies/{parentId}/branchOffices/{companyId} — Remove a branch office linkmerchantReference FieldPOST /guests/{id}/creditCard now accepts an optional merchantReference field. This integrator-supplied string (max 100 characters) is stored at token creation time and acts as the lookup key when retrieving token details via searchGuestRmsPayToken.
This enables fully headless payment flows — for example, AI voice agents collecting card details over the phone — to complete the rmsPay flow without requiring any UI interaction from the guest.
POST /guests/{id}/creditCardNote: RMS does not enforce uniqueness on
merchantReference. The integrator is responsible for managing reference values.
A global maximum record limit of 50,000 is being introduced across all REST API endpoints that accept a limit parameter. Previously, requests with limits up to 1,000,000 were accepted and silently truncated. From this release, any request exceeding 50,000 will return HTTP 400 Bad Request.
Affected endpoints:
POST /transactions/allocations/searchPOST /transactions/searchPOST /guests/searchPOST /reservations/searchAction required: If your integration currently requests more than 50,000 records in a single call on any of the above endpoints, you will need to reduce your limit value or implement pagination before this change reaches Live. Partners identified as using limits above 50,000 have been contacted directly.
Endpoints with an existing explicit limit lower than 50,000 are unaffected.
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+.
This Beta release includes two fixes and one new feature enhancement. Partners are encouraged to validate these changes in Beta and report any issues via standard support channels.
Guest Classifications — New Endpoints
New endpoints have been added to support full management of guest classifications, enabling retrieval, assignment, replacement, and removal of classifications on a guest record.
New endpoints:
GET /guestClassifications — Retrieve available classification types SwaggerHub ↗GET /guests/{id}/classifications — Get classifications assigned to a guest SwaggerHub ↗POST /guests/{id}/classifications — Add a classification to a guest SwaggerHub ↗PUT /guests/{id}/classifications — Replace the full classification set for a guest SwaggerHub ↗DELETE /guests/{id}/classifications/{classificationId} — Remove a specific classification from a guest SwaggerHub ↗Pencil Reservation — Dynamic Pricing Rate Consistency
PATCH /reservations/{id}, PUT /reservations/{id}/statusReservation Hold — 404 Error on Create
404 Not Found error was returned despite the hold record being successfully created.POST /reservations/{id}/holds now returns the correct 200 OK response with the hold record payload upon successful creation.POST /reservations/{id}/holdsYour 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:
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.
This Beta release includes one enhancement to company and travel agent note management via the API. Partners are encouraged to validate this change in Beta and report any issues via standard support channels.
Company & Travel Agent Notes — All Properties Support
The API now supports creating and updating notes scoped to All Properties for both company and travel agent records, by passing propertyId: 0 in POST and PUT requests. This aligns API behaviour with what is already possible in the RMS UI.
Previously, propertyId: 0 was rejected by the API, requiring notes to be managed on a per-property basis only.
Additionally, validation has been added to PUT requests to ensure the propertyId in the request matches the existing note's scope. Attempting to update an All Properties note with a specific property ID (or vice versa) will return a 400 error.
Endpoints affected:
POST /companies/{id}/notes — SwaggerHub ↗PUT /companies/{id}/notes/{noteId} — SwaggerHub ↗POST /travelAgents/{id}/notes — SwaggerHub ↗PUT /travelAgents/{id}/notes/{noteId} — SwaggerHub ↗Note: Using
propertyId: 0creates a note that applies across all properties the token has access to. API users should be intentional when using this scope — if your integration does not have access to all properties, use property-specific notes instead.