934 + Oracle Hospitality
From hotels and restaurants to cruise, Juno connects the Oracle Hospitality environments you already run — OPERA Cloud, OPERA v5, Oracle MICROS Simphony and Oracle Hospitality Cruise SPMS — to one secure payment layer.
Most hospitality groups evaluating payment do not have a blank sheet. They have OPERA running the property, Simphony running the outlets and, for cruise operators, Oracle Hospitality Cruise SPMS running the ship. Each environment has its own supported integration path, and payment is too often designed three separate times. The question this page answers is a single one: can an enterprise standardise payment across its Oracle estate without replacing the Oracle systems at the heart of the operation?
The integration challenge
The difficulty is rarely the payment itself. It is the number of moving parts between the guest, the Oracle environment and the acquirer — and the fact that they differ per environment and per deployment.
Hotels, outlets and ships are typically procured, integrated and supported separately, so a group can end up with three unrelated payment architectures inside one Oracle estate.
Juno provides one payment layer across the supported environments, so the group operates a consistent payment model even where the Oracle integration path differs.
OPERA Cloud, OPERA v5, Simphony and Oracle Hospitality Cruise SPMS expose different integration surfaces, and the available payment and posting flows depend on the product, version and deployment scope.
934 confirms the applicable flows against the customer's actual Oracle estate during solution design rather than assuming a single standard path.
The Oracle Hospitality Integration Platform (OHIP), Oracle Payment Interface (OPI), the Simphony Transaction Services (STS) Gen 2 cloud API and Oracle Hospitality Payment Cloud Service are distinct things, and it is easy to conflate them when scoping an integration.
Juno uses the supported Oracle integration path for the environment in scope, with each interface kept distinct rather than treated as interchangeable.
Payment activity may post correctly into the Oracle environment yet still leave finance reconciling settlement across acquirers, outlets and properties by hand.
Juno carries transaction, settlement and reconciliation context beyond the property so group finance can trace payouts back to the source.
Oracle Hospitality ecosystem
Oracle provides the hospitality operating environments and the interfaces around them. Juno provides the payment layer connecting the environments it supports to payment infrastructure. These are the environments Juno works with today — not the whole Oracle Hospitality catalogue.
Oracle OPERA Cloud and OPERA v5
Oracle runs the property: reservations, stays and the guest folio. Juno provides the payment layer around the supported hotel payment workflows, from capture to posting.
Explore Juno Hospitality SuiteOracle MICROS Simphony POS
Oracle runs the outlet and the check. Juno Pay@Table connects with Oracle Simphony through the Simphony Transaction Services (STS) Gen 2 cloud API — a cloud-based connection that needs no additional on-property integration middleware — rather than through OPI, while pay-at-counter service uses the Simphony Payment Interface (SPI). Juno provides the payment layer for supported restaurant and outlet payment workflows across counter, table and mobile service models. For Simphony sites, Juno Pay@Table takes the open check and the payment to the guest: staff can take full or split payment, capture tips and return the payment to the point of sale.
Explore Juno F&B SuiteOracle Hospitality Cruise Shipboard Property Management System (SPMS)
Oracle manages the shipboard guest, reservation and folio environment. Juno connects the payment lifecycle through Oracle Payment Interface (OPI).
Explore Juno Cruise SuiteIntegration interfaces
OHIP is Oracle's API-based integration platform for operational and data integration and, to date, applies to OPERA Cloud rather than the other Oracle Hospitality products. It is not a payment interface. Juno uses supported OHIP paths for OPERA Cloud where the customer's deployment and scope call for them.
STS Gen 2 is the Oracle cloud API through which Juno Pay@Table integrates with Oracle MICROS Simphony, giving access to revenue centres and open checks and posting payments and tips back to the check. It is distinct from OPI and from the Simphony Payment Interface (SPI) — SPI is the interface used for pay-at-counter service — and OHIP does not apply to Simphony.
OPI is Oracle's standard payment interface, used with OPERA Cloud, OPERA v5 and Oracle Hospitality Cruise SPMS. Juno uses OPI according to the Oracle environment and deployment in scope.
Reference architecture
Three Oracle operating environments, each with its own payment interface, converging on one Juno payment layer. OPERA Cloud, OPERA v5 and Oracle Hospitality Cruise SPMS use the Oracle Payment Interface (OPI); Oracle MICROS Simphony connects through the Simphony Transaction Services (STS) Gen 2 cloud API. OHIP provides OPERA Cloud data and context where applicable and is not a payment interface. 934 confirms the applicable configuration and deployment scope during solution design.
Relevant Juno products
Business outcomes
Bring hotel, food & beverage and cruise payment environments onto a consistent Juno payment layer while retaining the Oracle systems each operation depends on. Integration paths still differ by environment; the payment model does not have to.
Support the payment and data flows that help properties, outlets and ships collect, post and manage transactions against the correct account.
Carry supported payment and settlement context into the workflows finance teams use to close accurately across the estate.
Platform proof
Oracle-connected hotels, outlets and ships run on the same Juno platform, gateway and acquiring relationships as every other deployment. Values below come from the canonical platform statistics registry.
OPERA Cloud, OPERA v5 and Oracle Hospitality Cruise SPMS are supported Juno payment environments through Oracle Payment Interface (OPI), and Oracle MICROS Simphony through the Simphony Transaction Services (STS) Gen 2 cloud API. OHIP provides OPERA Cloud data and context where applicable.
Juno integrates with Oracle Hospitality Cruise Shipboard Property Management System (SPMS) through Oracle Payment Interface (OPI), supporting the cruise payment lifecycle. This validation is specific to the Cruise/SPMS capability.
Supported flows are confirmed against the customer's Oracle products, versions and deployment scope during solution design rather than assumed.
Knowledge
Oracle provides the hospitality operating environments and the interfaces around them. Juno provides the payment layer connecting the environments it supports — OPERA Cloud, OPERA v5, Oracle MICROS Simphony and Oracle Hospitality Cruise SPMS — to supported payment infrastructure. It does not replace Oracle's property-management, point-of-sale or shipboard products.
Juno works across three Oracle Hospitality operating environments: OPERA Cloud and OPERA v5 property management for hotels, Oracle MICROS Simphony POS for food and beverage outlets, and Oracle Hospitality Cruise Shipboard Property Management System (SPMS) for cruise. OPERA Cloud, OPERA v5 and Cruise SPMS connect through Oracle Payment Interface (OPI); Juno Pay@Table connects with Simphony through the Simphony Transaction Services (STS) Gen 2 cloud API. Oracle Hospitality Integration Platform (OHIP) applies to OPERA Cloud only, for data and context where the deployment calls for it. Juno does not integrate with every product in the Oracle Hospitality catalogue.
Yes. An enterprise group running several Oracle Hospitality environments can operate one Juno payment layer across them rather than treating each as an unrelated payment architecture. The Oracle systems stay in place, and the supported integration path still differs by environment and deployment — OPERA, Simphony and Oracle Hospitality Cruise SPMS are not integrated identically — but payment capture, orchestration and financial context run on the same Juno platform.
Related: Juno Hospitality Suite, Juno F&B Suite, Juno Cruise Suite
Oracle manages the shipboard guest, reservation and folio environment in Oracle Hospitality Cruise Shipboard Property Management System (SPMS). Juno connects the payment lifecycle through Oracle Payment Interface (OPI). The full cruise proposition — onboard payment lifecycle, fleet rollout and acquiring model — is covered on the Juno Cruise Suite page.
Related: Juno Cruise Suite, Cruise
No. Supported authorisation, capture, token exchange, posting, settlement visibility and reconciliation flows depend on the Oracle products, integration path and deployment scope. The 934 team confirms the applicable flow during solution design.
They are distinct Oracle interfaces and are not interchangeable. Oracle Hospitality Integration Platform (OHIP) is Oracle's API-based integration platform for operational and data integration and, to date, applies to OPERA Cloud only; it is not a payment interface. Oracle Payment Interface (OPI) is Oracle's standard payment interface, used with OPERA Cloud, OPERA v5 and Oracle Hospitality Cruise SPMS. Juno Pay@Table connects with Oracle MICROS Simphony through the Simphony Transaction Services (STS) Gen 2 cloud API, a cloud-based connection that is distinct from both OPI and the Simphony Payment Interface (SPI), which is used for pay-at-counter service. Oracle Hospitality Payment Cloud Service is a separately named Oracle product, not a synonym for OPI.
Start by confirming which Oracle environments are deployed — hotels, outlets, ships or a combination — in which versions, and how the estate is structured. That determines the integration paths and the payment flows available. From there the relevant Juno suites and acquiring model can be mapped across the estate.
Related: Hospitality, Juno Hospitality Suite, Juno Cruise Suite
No. Juno does not replace Oracle's property-management, point-of-sale or shipboard products. It sits alongside OPERA Cloud, OPERA v5, Simphony and Oracle Hospitality Cruise SPMS as the payment layer, connecting through the supported Oracle integration path for each environment.
Where the integration path supports it, authorised and captured payments are matched to the correct guest folio in the Oracle environment so front-desk and outlet staff see an accurate balance without re-entry. Oracle owns the folio; Juno manages the payment behind it. The specific posting behaviour depends on the Oracle product, version and integration path in place.
Related: Reconciliation
Juno is designed to operate across a group estate running Oracle Hospitality products, with the applicable integration path — OPERA Cloud, OPERA v5, Simphony or Oracle Hospitality Cruise SPMS — confirmed per property or ship during solution design.
Related: Hospitality Suite
A summary of which Oracle environments are deployed (OPERA Cloud, OPERA v5, MICROS Simphony, Oracle Hospitality Cruise SPMS), their versions, the estate structure across properties, outlets and ships, and the current acquirer or gateway setup. That lets 934 confirm the integration paths and applicable payment flows during solution design.
Supported payment and data flows depend on the Oracle environments you run, your deployment and your operating model. Share what you run — hotels, outlets, ships or all three — and we will confirm the integration paths with you.
Still researching? Read the hospitality proposition
Related on 934
See the market proposition around hotels and resorts.
Simphony-connected outlet payment in the F&B market.
Explore the product layer behind the integration.
What a native PMS and POS payment integration covers commercially.
Move from integration context into implementation.
What OPI and OHIP each do, how OPERA Cloud differs from OPERA 5, how tokenisation reduces PCI scope, and how a payment reaches the folio and reconciles to settlement.
