Skip to content
934 logo
Hotel operations team reviewing payments at the front desk.

Hospitality Payment Orchestration

The financial control layer for hospitality.

Juno orchestrates every transaction between your PMS, payment processors, terminals and ERP — from reservation to reconciliation. Keep the systems you trust. Gain control you've never had.

Explore integrations

One layer. Every transaction.

From pre-authorisation at booking to the reconciled statement in your ERP, Juno gives finance and operations a single, controlled environment for the money that moves through your property.

The guest lifecycle

One platform. The entire guest lifecycle.

01
Step 01

Before arrival

Juno reads booking data from your PMS and handles pre-authorisations and deposits via secure pay-by-link. The financial record of the stay starts clean.

02
Step 02

During the stay

Front desk, restaurant, bar, spa, online — payments from every department converge into one ledger in real time, with hotel spa and other outlet charges postable to the guest folio where the hotel workflow requires it. Card-present, card-not-present, local methods: one source of truth.

03
Step 03

At checkout and beyond

Folio posting, settlement and reconciliation flow automatically into your back office. No exports. No manual matching. No month-end firefight.

Capabilities

Built for the people accountable for the numbers.

Juno Portal — your transaction command centre

Every payment, every method, every property in one dashboard. Real-time visibility for the people accountable for the numbers.

Juno Nexus — keep your terminals

Already invested in card terminals? Nexus bridges your existing hardware to Juno's cloud platform. No forklift upgrade.

Pay-by-Link — capture revenue earlier

Send a secure payment link from inside your hotel system. Guests pay deposits on their terms; you secure the booking on yours.

Native integrations — depth, not adapters

Purpose-built connectivity to Oracle OPERA via OPI, Oracle Simphony (Juno Pay@Table via STS Gen 2), SIHOT, and a growing ecosystem of PSPs and ERPs.

600+
Active payment locations
14
Years in hospitality payments
23
Systems integrations
PCI DSS L1
Security compliance

Supported integrations

Oracle OPERA · Oracle Simphony · SIHOT · Worldline · Saferpay · PostFinance · Recurly · SAP · and a growing ecosystem.

View all supported integrations

Control

Everything finance and operations need to stay in control.

One dashboard, every property

Every booking, deposit and folio charge across every property in one view. Real-time visibility for the people accountable for the numbers.

Automatic PMS posting

Payments post straight back to your PMS — no manual entry, no night-audit mismatch.

Pre-auth, capture and refunds

Handle deposits, incidentals and refunds cleanly across the stay, with a full audit trail.

Settlement & reconciliation

Daily payouts and automated reconciliation across every property, currency and acquirer.

Take control of your money.

See how Juno unifies your payment stack across the guest lifecycle.

In summary

Juno Hospitality Suite — the essentials

Quick facts

Purpose
A suite within Juno, 934's hospitality payments platform, that provides payment orchestration for hotels — connecting the PMS, payment processors, terminals and ERP across the guest payment lifecycle.
Target customers
Hotels and hotel groups, from independents to enterprise estates.
Supported PMS
Including Oracle OPERA Cloud and OPERA v5 (via OPI, with OHIP for OPERA Cloud data where applicable), SIHOT, Shiji, HotelKey, Clock, Infor and RMS Cloud.
Supported POS
Oracle Simphony. Juno Pay@Table connects with Simphony through the Simphony Transaction Services (STS) Gen 2 cloud API.
Payment channels
Configured channels including card-present (terminals), card-not-present (online, MOTO, Pay-by-Link) and in-PMS / in-POS charges.
Deployment model
Cloud platform that connects to systems a property already runs; existing terminals connect through Juno Nexus.
Typical use cases
Pre-authorisations and deposits at booking, a unified transaction record across outlets, automatic PMS posting, and handover to settlement and reconciliation.

Related on 934

Continue exploring

Adjacent products

Markets and solutions

Integrations & experts

Knowledge

Juno Hospitality Suite — questions answered

Reservation PMS Juno Hospitality Suitepayment orchestration Payment processor / acquirer Settlement Juno Financial Suite ERP
Reservation → PMS → Juno Hospitality Suite → Payment processor/acquirer → Settlement → Juno Financial Suite → ERP.
What is the Juno Hospitality Suite?

The Juno Hospitality Suite is part of Juno, 934's hospitality payments platform. It provides payment orchestration for hotels: it connects the property's PMS, payment processors and terminals, and carries payment data through to the financial back office. Rather than replacing existing systems, it connects them, so payments taken at the front desk, in F&B outlets or online are captured and recorded against the reservation. The Suite manages the payment lifecycle across three stages of the guest journey — before arrival, during the stay, and at checkout and beyond — and creates a unified transaction record that downstream settlement, reconciliation and accounting can work from. Acceptance and PMS posting are handled by the Hospitality Suite; settlement, reconciliation and ERP posting are handled by the Juno Financial Suite.

Related: Juno Financial Suite, Payment orchestration

Which property management systems does the Juno Hospitality Suite support?

Juno provides native, supported integrations with major hospitality PMS and POS platforms. On the Oracle side it supports OPERA Cloud and OPERA v5 (on-premises) through OPI (Oracle Payment Interface), with OHIP (Oracle Hospitality Integration Platform) providing OPERA Cloud data and context where applicable, and Oracle Simphony for F&B point of sale, where Juno Pay@Table connects through the Simphony Transaction Services (STS) Gen 2 cloud API. Beyond Oracle, supported platforms include SIHOT, Shiji, HotelKey, Clock, Infor and RMS Cloud, with a growing ecosystem of further connections. 934 is an OPI validated Oracle Partner, for both OPI On-Premise and OPI Cloud, with extensive OHIP integration for OPERA Cloud. Because the integrations connect at the PMS level, payment activity can be associated with the reservation and folio rather than tracked separately.

Related: Integrations, Pay-by-Link for OPERA Cloud

How does Juno post payments back to Oracle OPERA?

Juno integrates with Oracle OPERA through Oracle's supported interfaces — OPI for payment processing, and OHIP for OPERA Cloud data integration where applicable — with the supported interface for OPERA v5 on-premises. When a payment is authorised and captured, Juno records the transaction and posts it back against the corresponding reservation or folio, so the PMS reflects the payment activity. This reduces the manual entry and night-audit matching that occur when payment and PMS records are kept separately. Because the posting is tied to the folio, the downstream stages — settlement, reconciliation and ERP posting — work from a consistent record. The detail of settlement and reconciliation is covered by the Juno Financial Suite.

Related: Juno Financial Suite, Payment integration

How does Juno handle pre-authorisations, deposits and refunds during a stay?

Juno supports the authorisation lifecycle across the guest journey. Before arrival, it can read booking data from the PMS and handle pre-authorisations and deposits, including deposits collected through Pay-by-Link. During the stay, incidentals and additional charges can be authorised and captured, and refunds processed, with an audit trail. Card data is tokenised, so a reusable token rather than the raw card number can be used for follow-on actions such as a balance charge or a no-show fee, which helps keep card details out of staff workflows and the PMS. Authorisations, captures and refunds are recorded against the folio, giving finance an auditable view of the payments attached to a stay. Tokenisation is explained under payment orchestration.

Related: Pay-by-Link, Payment orchestration, Juno Financial Suite

Does Juno replace our existing payment terminals or PMS?

No. The Juno Hospitality Suite connects the systems a property already runs rather than replacing them. Existing payment terminals connect through Juno Nexus — a component that links a hotel's existing terminal hardware to the Juno platform, so the property can retain its terminals while bringing them into Juno. The PMS and POS — such as Oracle OPERA, SIHOT and Simphony — remain in place, with Juno acting as the orchestration layer between them and the payment rails. Front-desk and finance teams continue working in the systems they know, while gaining unified payment capture, posting and reconciliation across the estate.

Related: Juno payment terminals, Payment integration