What's new?
In this months release improvements have been made to calendar-driven version of the Booking Engine and now there is a dedicated OHIP payment mapping table.
Access digital assistant
Get help without leaving your CRS workflow. The Access digital assistant in CRS provides instant access to support articles and system guidance directly within the application. Find answers to questions without switching between systems or searching through external help resources.
Additional digital assistant enhancements are coming over the next few months to make finding support information even faster.
Calendar-driven version of the booking engine
The calendar-driven version of the booking engine will indicate dates unavailable for check-out directly in the calendar, so guests can see at a glance which departure dates aren't selectable for your property or offer. The calendar legend explains what the unavailable for check-out date indicator means.
Payment method mapping with OHIP PMS interface
The OHIP PMS interface now includes a dedicated mapping table for the Payment Method entity, giving your team greater flexibility and a cleaner data flow between your PMS and CRS.
Opera maintains two distinct payment-related code tables:
First option, pre-populated with recommended values.
The second that hotels configure themselves.
Previously, both tables shared the same mapping codes pointing to a single CRS table. When hotels switched payment providers or added new payment methods, this created unnecessary complexity and potential for mismatches.
A dedicated mapping screen is now available for the Payment Method entity within the OHIP integration configuration in the PMS mapping screen. This is structured similarly to the existing PMS Transaction Code mapping screen. Credit card types enabled at property level will be mapped here as Payment Methods, as well as within the mapping table dedicated to Credit Card codes.
Your current credit card (CC) mapping configuration is retained and will now serve specifically as the CardType mapping. No historical configuration is lost during the transition.
When the integration sends payment data to the CRS, the following logic applies:
If a Payment Method mapping exists, it is used as the Payment Method value.
If no Payment Method mapping is defined, the system automatically falls back to using the existing CC mapping for both Payment Method and Card Type, ensuring uninterrupted processing.
This update applies to hotels using the OHIP PMS interface with payment processing enabled. It is particularly relevant for properties that:
Manage multiple or frequently changing payment methods.
Have recently switched or are planning to switch payment providers.
Have encountered code mapping conflicts between Opera's two payment code tables.
Action maybe required from 11th March 2026
⚠️ Important: No changes are made to your existing CC mapping automatically.
Review the options below and take the action that applies to your property:
To use the new Payment Method mapping – update the new mapping screen after the release date.
If you don't manage your property or group’s PMS mapping – open a support case so the team can update this on your behalf.
If you take no action – your current behaviour continues as normal via the fallback logic.
Learn more about the OHIP integration or request the latest OHIP certification guide from the support team.