Index
What is this integration?
The Oracle Opera integration connects Golfmanager with the Opera PMS (hotel management system) from Oracle. From the Golfmanager POS, it lets you locate the guest's reservation and charge their purchases to the room.
The amount is no longer collected at the till and is added to the guest's account in Opera, which they pay at check-out. The modern version works with Opera Cloud through Oracle's integration platform (OHIP).
A PMS (Property Management System) is the program the hotel uses to manage reservations, rooms and each guest's account. Oracle Opera is one of the most widespread. OHIP (Oracle Hospitality Integration Platform) is the modern way to connect to Opera Cloud.
What problem does it solve?
The guest does not pay at the moment: they consume at the golf course, the shop or the bar and everything accumulates on their room.
Locates the reservation easily by searching by room or name.
Avoids double handling: the charge travels to Opera instantly.
Respects the hotel's rules (for example, reservations that do not allow charges).
Allows refunds on the same reservation (or, in Opera Cloud, on a different room).
Which systems does it connect and in which direction does the data travel?
It connects the Golfmanager POS with Oracle Opera Cloud (through OHIP), in real time:
Golfmanager queries Opera for reservations to locate the guest (by room or name).
Golfmanager sends the charge (or the refund) to the reservation's account/folio.
Opera responds whether the operation was carried out, and Golfmanager records it.
It is a real-time communication via API. In the classic (on-premise) variants the communication is done against a local Opera server; see the Variants section.
What information is exchanged?
Information | Direction | Purpose |
Reservation search (by room or name) | Opera → Golfmanager | Identify who to charge |
Charge: amount, concept and folio/reservation | Golfmanager → Opera | Add the charge to the guest's account |
Confirmation / refund | Golfmanager ↔ Opera | Confirm or cancel the charge |
Prerequisites (before enabling the integration)
That the hotel uses Oracle Opera Cloud with the OHIP integration platform enabled.
Have the Opera Cloud module installed in your Golfmanager, together with the POS and invoicing modules.
The OHIP credentials: Client ID, Client Secret, Application Key (App Key), Enterprise ID and the gateway URL.
The hotel identifier (Hotel ID) in Opera.
Permissions to manage Opera in Golfmanager.
Authorization form
To authorize the integration between your company and Opera through an API, you normally need to send Golfmanager a document filled in and signed by both parties before you start. It is a prerequisite to enabling the connection.
Your implementation team will tell you the specific form and how to submit it. Until the authorization is complete, you cannot operate against the real Opera.
How to set it up (step by step)
The configuration is done once, with the credentials provided by Oracle or the hotel's IT team.
Step 1 — Connection data
Go to Opera Cloud > Settings.
Enable Test mode (recommended at the start: it does not make a real connection).
Enter Client ID, Client Secret and Application Key.
Enter the Gateway URL (by default
https://api.platform.opera-cloud.com/ohip) and the Enterprise ID.Indicate the Currency (by default
EUR).Optional: enable Send non-Opera payments to Opera Cloud if you want all sales reflected in the folio.
Check Active.
Save the changes.
Step 2 — Register the hotels
Go to Opera Cloud > Hotels.
Create each hotel with its Opera Hotel ID and an identifying name.
Save.
Step 3 — Transaction and cashier codes (recommended)
In each product subfamily, enter its Opera Cloud Code (the transaction code Opera should use to record those products).
In each POS, enter its Opera Cloud Cashier ID if the hotel requires it for the daily settlement.
If you enabled sending non-Opera payments, assign the Opera Cloud Code to each payment method you want to report.
Step 4 — Test the connection
Use the test connection option to check that the credentials are correct.
When it works, disable Test mode to operate live.
⚠️ Recommendation: start with Test mode enabled and, once the connection works, disable it to operate live. In live mode, charges are real on the guest's account.
The configuration fields in detail
Below is an explanation of each field in the Opera Cloud integration.
1) Active
• Field name: Active
• Description: Master switch that enables or disables the Opera Cloud integration.
• Impact on the system: If it is disabled, the room-charge payment method does not operate against Opera.
• Usage example: you enable it once the connection has been tested.
What happens when it is used: the POS can start charging sales to rooms.
System behavior: with it disabled, the integration stays inactive even if the credentials are set.
2) Test mode
• Field name: Test mode (no real connection)
• Description: Makes the integration work against a simulated environment, without sending real charges to Opera.
• Impact on the system: It lets you validate the configuration and the flow without affecting guest accounts.
• Usage example: you enable it during the setup.
What happens when it is used: the "charges" do not reach the hotel; only the circuit is tested.
System behavior: when you disable it, charges become real on the guest's folio.
3) Client ID
• Field name: Client ID
• Description: The client identifier of the OHIP credentials provided by Oracle/the hotel.
• Impact on the system: It is part of the authentication. If it is incorrect, the connection fails.
• Usage example: you copy it from the hotel's OHIP panel.
What happens when it is used: together with the rest of the credentials, it authenticates Golfmanager to Opera.
System behavior: a wrong value causes a connection/credentials error.
4) Client Secret
• Field name: Client Secret
• Description: The secret key associated with the Client ID. It is sensitive information.
• Impact on the system: Required to authenticate. It must not be shared.
• Usage example: you paste it next to the Client ID.
What happens when it is used: it completes the authentication with Opera.
System behavior: if it expires or is incorrect, the connection stops working.
5) Application Key (App Key)
• Field name: Application Key
• Description: The OHIP application key that identifies the application to Oracle's platform.
• Impact on the system: Essential for the requests to be accepted by OHIP.
• Usage example: Oracle provides it when enabling OHIP.
What happens when it is used: requests are correctly identified to Opera Cloud.
System behavior: without a valid App Key, OHIP rejects the calls.
6) Gateway URL
• Field name: Gateway URL
• Description: The address of the OHIP service Golfmanager connects to. By default https://api.platform.opera-cloud.com/ohip (may vary by region).
• Impact on the system: It defines which Opera Cloud server the requests go to.
• Usage example: the hotel tells you the correct URL for its region.
What happens when it is used: queries and charges travel to that gateway.
System behavior: an incorrect URL produces connection errors.
7) Enterprise ID
• Field name: Enterprise ID
• Description: The organization's identifier in Oracle, required in the OHIP requests.
• Impact on the system: It places the requests within the correct Oracle account.
• Usage example: Oracle provides it together with the rest of the credentials.
What happens when it is used: requests are associated with the correct company.
System behavior: if it is missing or wrong, Opera does not process the requests.
8) Currency
• Field name: Currency
• Description: The currency in which charges are sent to Opera (by default EUR).
• Impact on the system: It must match the currency the hotel uses for that property.
• Usage example: you leave EUR for a hotel that invoices in euros.
What happens when it is used: charges reach Opera in that currency.
System behavior: an inconsistent currency may cause the hotel to reject them.
9) Send non-Opera payments to Opera Cloud
• Field name: Send non-Opera payments
• Description: An option so that payments made with other methods (cash, card…) are also reported to Opera.
• Impact on the system: It lets the hotel see all sales in the folio, not just room charges. Only payment methods that have an Opera Cloud Code assigned are reported.
• Usage example: you enable it to have full visibility of split payments.
What happens when it is used: cash/card payments of a sale are also notified to Opera.
System behavior: if a payment method has no code, it is not reported.
10) Hotel ID
• Field name: Hotel ID (in Opera Cloud > Hotels)
• Description: The identifier of each hotel/property in Opera, together with its name.
• Impact on the system: It indicates which Opera property the searches and charges are directed to.
• Usage example: you register the hotel with the Hotel ID the hotel gives you.
What happens when it is used: when charging, you choose the hotel and its reservations are queried.
System behavior: a wrong Hotel ID means no reservations are found.
11) Opera Cloud Code (subfamily)
• Field name: Opera Cloud Code, in each subfamily
• Description: The Opera transaction code with which the products of that subfamily are recorded.
• Impact on the system: It lets the hotel correctly classify consumption (golf, shop, restaurant…).
• Usage example: you set the Opera restaurant transaction code on the "Restaurant" subfamily.
What happens when it is used: charges for those products reach Opera under that code.
System behavior: without a code, the charge may not be classified as the hotel expects.
12) Opera Cloud Cashier ID (POS)
• Field name: Opera Cloud Cashier ID, in each POS
• Description: The cashier identifier the hotel assigns to each POS for the daily settlement in Opera.
• Impact on the system: It associates the charges with the correct cashier in Opera.
• Usage example: the hotel gives you a Cashier ID per point of sale.
What happens when it is used: the charges of that POS are allocated to that cashier.
System behavior: if the hotel requires it and it is missing, charges may be rejected.
13) Opera Cloud Code (payment method)
• Field name: Opera Cloud Code, in each payment method
• Description: The Opera code associated with a payment method, to report it when sending non-Opera payments is enabled.
• Impact on the system: Only payment methods with a code are reported to Opera.
• Usage example: you set the "cash" code on the Cash payment method.
What happens when it is used: cash payments are reported to Opera with that code.
System behavior: payment methods without a code are left out of the report.
ℹ️ Note: the exact names may vary slightly depending on your version and language. The function of each field is as described.
How it is used day to day
Charging a sale to the room
In the POS, add the products to the cart as usual.
As the payment method, select "Opera Cloud - Room Charge".
Choose the hotel (if you have several registered).
Locate the reservation by searching by room or guest name.
Select the reservation and confirm. The charge is sent to the guest's account (folio) in Opera.
ℹ️ If the reservation has the "No Post" flag enabled in Opera, the hotel does not allow charges to that room and the operation will be rejected indicating so.
Refunds
To refund, cancel/void the charge from Golfmanager: the system sends Opera the refund on the same reservation. In Opera Cloud, you can also direct the refund to a different room if necessary.
Checking the transactions
In Opera Cloud > Transactions you will see all the operations sent to Opera, with the guest, the room, the amount, whether they were successful or failed and the error detail if there was one. It is the first screen to check when a charge has not been completed.
Each transaction has a type:
Charge (payment): an amount was added to the room.
Refund: a previously charged amount was subtracted.
External payment / Rejected: a notification of a non-Opera payment, or an operation the hotel did not accept. When Opera rejects a charge, Golfmanager undoes the payment on its side and the line is left as pending payment.
Each record stores the request sent and the response received, which helps support diagnose.
Variants of the Opera integration
There are several ways to connect to Opera depending on the hotel. The behavior for the user (charging to the room) is equivalent; the connection data and the infrastructure change. Your implementation team will tell you which applies to your hotel.
Opera Cloud (OHIP): the current and recommended version, via REST API in real time, described in this article. The payment method is "Opera Cloud - Room Charge".
Opera 2.0 (via server/proxy): connection against an on-premise Opera through an intermediate server. It allows configuring subtotals and revenue center per subfamily.
Opera (classic, on-premise): the original room-charge integration. The payment method is "(OPERA) Room Charge".
About the classic (on-premise) variant
In classic installations, Golfmanager does not talk directly to the hotel's Opera, but to a local Opera server (a program installed on a club terminal that forwards the requests to the final Opera). Some aspects specific to this variant:
Local server address: the local server IP is configured (for example
http://127.0.0.1:8081), always with thehttp://prefix.Opera subtotals: each subfamily can be assigned to a subtotal group (Opera allows up to 16) so the hotel receives sales grouped its own way (for example, "Restaurant" in one subtotal and "Shop" in another).
Taxes: you can choose to send the amounts with taxes broken down or with the total including taxes.
Sending invoicing to Opera: in addition to the charge at the moment, invoicing can be synchronized. There is a manual send (the "Send to Opera" button in the sales view, which sends the sales not yet sent) and a configurable periodic automatic send.
These options are specific to the classic variant. In Opera Cloud, product classification is done with each subfamily's Opera Cloud Code.
Limitations to keep in mind
It depends on the hotel: Opera and OHIP must be reachable. If the service does not respond, rooms cannot be charged.
The guest must have a reservation locatable in Opera (checked in).
Reservations with "No Post" do not allow charges.
It requires the correct OHIP credentials and the Hotel ID.
Do not mix test mode with live mode: in live mode charges affect the guest's account.
The classic variant requires a local server installed and running at the club.
Frequently asked questions
What is a PMS, Opera and OHIP?
A PMS is the program the hotel uses to manage reservations, rooms and each guest's account. Oracle Opera is one of the most used. OHIP is Oracle's modern platform to connect to Opera Cloud via API.
Does the guest pay at the till?
No. With the room charge, the amount is not collected at the till: it is added to the guest's account at the hotel and they pay it at check-out.
I get "This reservation has the No Post flag". What does it mean?
It means the hotel has marked that reservation as not eligible for charges. You must use another collection method, or the hotel must remove the "No Post" flag in Opera.
The reservation does not appear when searching. Why?
The guest may not have a locatable reservation (not checked in) or Opera/OHIP may not respond. Verify that the guest is registered and that the hotel's service is reachable.
I get a connection or credentials error.
Check Client ID, Client Secret, Application Key, Enterprise ID and the Gateway URL. Use the test connection option to confirm they are correct.
The charge is rejected even though the connection works.
Opera did not accept the movement. Check the detail in Transactions: the reservation may have been closed, have restrictions or be missing some data. When Opera rejects, Golfmanager undoes the payment and the line is left pending.
What is the difference between test mode and live mode?
In test mode no real charges are sent to the hotel: only the circuit is validated. In live mode, each charge really affects the guest's account.
Can I make refunds?
Yes. When voiding/cancelling the charge, Golfmanager sends the refund to Opera. In Opera Cloud you can even direct it to a different room if necessary.
What happens with non-Opera payments (cash, card)?
By default they are not sent to Opera. If you enable the "Send non-Opera payments" option and assign an Opera Cloud Code to those payment methods, they will also be reflected in the folio.
What is the subfamily "Opera Cloud Code" for?
It is the transaction code with which Opera classifies products (golf, shop, restaurant…). It lets the hotel see consumption in the correct categories.
Which Opera versions are compatible?
The recommended one is Opera Cloud (OHIP). There are also on-premise variants (Opera 2.0 via server and classic Opera). For the user, charging to the room works the same; the connection changes.
Do I need to install anything at the club?
With Opera Cloud, no: the connection is over the internet (API). With the classic variants, yes: a local Opera server installed and running on a club terminal is needed.
Do I need to sign any document to enable it?
Yes. You normally need to send the signed authorization form for the API integration before operating live.
Where do I see if a charge has failed?
In Opera Cloud > Transactions. Each operation shows whether it was successful or failed and the error detail.
Who provides the OHIP credentials?
They are provided by Oracle or the hotel's IT team. Gather them before configuring the integration.
Recommended best practices
Test first in test mode and with "test connection" before operating live.
Gather the OHIP credentials with the hotel's IT team.
Configure the Opera Cloud Code on the subfamilies so consumption arrives well classified.
Always confirm the reservation and the guest before charging.
For a failed charge, check Transactions first: the error detail usually indicates the cause.
Complete the authorization form before you start operating.
Need help?
If you have questions about the OHIP credentials, the configuration or a charge that does not complete, our support team is available to help you. Write to us through the blue bubble in your management software. For the connection data and the hotel's rules (No Post, transaction codes, Hotel ID…), also rely on the hotel's IT team, who is the one managing Opera.