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+.

Summary

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.

New Features

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 ↗

Fixes & Improvements

Pencil Reservation — Dynamic Pricing Rate Consistency

• Issue: When a rate type was applied to a pencil reservation via the API, the quoted rate was not being preserved. If dynamic pricing changed before the pencil was converted to Unconfirmed/Confirmed, the reservation would be re-quoted at the new rate — producing a different rate than originally presented to the guest.
• Fix: Applying a rate type to a pencil reservation via the API now correctly preserves the quoted rate and occupancy snapshot. The rate will be retained when the pencil is subsequently converted.
• Endpoints affected: PATCH /reservations/{id}, PUT /reservations/{id}/status

Reservation Hold — 404 Error on Create

• Issue: When creating a new reservation hold via the API, a 404 Not Found error was returned despite the hold record being successfully created.
• Fix: POST /reservations/{id}/holds now returns the correct 200 OK response with the hold record payload upon successful creation.
• Endpoint: POST /reservations/{id}/holds

Notes

• Release Date: April 8, 2026 Beta only
• Dependencies: None
• There is no impact to Live environments.
• Please report any issues through standard support channels: https://rmsapi.zendesk.com/hc/en-gb/requests

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.

Summary

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.

New Features

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: 0 creates 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.

Notes

• Release Date: March 25, 2026  Beta only
• Dependencies: None
• There is no impact to Live environments.
• Please report any issues through standard support channels: https://rmsapi.zendesk.com/hc/en-gb/requests

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.

The icons at the top of the Generated Report have been updated with new sizes and a revised display order to improve overall clarity.

What was the issue?

For IBE+ bookings where guests paid via RMS Pay, staff were unable to process refunds directly from within RMS (9+). Attempting to do so returned an error, leaving teams with no option but to manually intervene at the payment gateway level — a time-consuming workaround that also carried financial risk if not actioned promptly.

What's been fixed?

RMS Pay refunds for IBE+ bookings can now be processed directly from within the reservation in RMS, just as you'd expect. Both full refunds and partial refunds are supported. When a refund is submitted, it communicates with RMS Pay, returns the funds to the guest's original payment method, records the transaction in the reservation ledger, and updates the balance — all in one smooth step.

If a refund attempt fails at the gateway, the system will now correctly prevent the refund from being recorded, keep the original payment intact, and display an error message so your team knows what's happened.

What do you need to do?

Nothing — this fix is automatic. Refunds for RMS Pay transactions made through the new Booking Engine can now be processed directly from the reservation in RMS as normal.

What was the issue?

When a property configured specific card types in Online Options (for example, Visa and Mastercard only), the new Booking Engine was not respecting that configuration for RMS Vault payments. Guests could still complete a booking using a card type that wasn't assigned - such as Amex or Diners - bypassing the intended payment restrictions entirely.

What's been fixed?

The Booking Engine now correctly validates card types against your Online Options configuration at the point of payment. Only card types that have been assigned to the IBE will be accepted. If a guest enters a card type that isn't configured, the card field will be flagged and they won't be able to proceed with that card.

This applies to both desktop and mobile.

What does this mean for your guests?

The checkout experience remains smooth for guests using an accepted card - they'll see clear visual confirmation that their card is valid. Guests using an unsupported card type will be prompted to use an accepted alternative before completing their booking.

Do you need to do anything?

No action is required. Just make sure your accepted card types are correctly configured in Online Options - the Booking Engine will handle the rest.