A critical issue has been resolved where a successful payment through RMSPay could result in the booking failing to transfer into RMS 9+ - leaving guests charged with no confirmed reservation.

This has now been fixed. When a payment is successfully processed through RMSPay, the booking will always be created in RMS 9+ - complete with a receipt and all guest details - even where Create Direct Booking (CDB) is set to False.

No action is required. This fix applies automatically for all IBE+ properties using RMSPay.

Apple Pay is now live for all RMS Pay customers. Guests can complete payments using Face ID, Touch ID, or their Apple Watch — without entering a single card detail. It works automatically across all your guest-facing RMS Pay channels.

What you'll see

• Instant checkout for guests with Apple devices
• Biometric security improves payment authentication, reduces chargebacks
• Nothing to configure, it's automatically enabled with RMS Pay

Who can use it

Available at no additional cost to all RMS Pay customers using Pay By Link, Guest Portal, Booking Engine, Corporate Portal, and RMS Pay terminals.

Learn more in the Knowledge Centre.

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.

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.

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.