Hotels & resorts
Juno brings guest payments, property systems, acquiring and reconciliation together for hotels and resort groups.
A hotel does not take one payment. It takes a deposit weeks before arrival, a pre-authorisation at check-in, incremental charges across reception, restaurant, bar and spa, and a final settlement at checkout — often against a folio that has been split between a guest, a company and a travel intermediary. Each of those moments touches a different system, and each one has to end up posted correctly against the same reservation. Juno sits underneath that journey as a single payment and financial operations layer, connected to the property-management system the hotel already runs.
The operating challenge
The recurring problems in hotel payments are rarely about acceptance. They are about what happens to the transaction afterwards, and how much manual work it takes to make the numbers agree.
Terminals, online journeys and remote payment links often live outside the property-management system, so front-office teams re-key references or reconcile by hand at shift close.
Juno integrates at the gateway layer and returns the payment result to the PMS, so the folio reflects what actually happened at the point of interaction.
Pre-arrival collection is frequently improvised across email, phone and third-party links, which creates card-data exposure and unclear audit trails.
Pay-by-Link gives reservations and revenue teams one secure remote payment journey tied to the booking, with the outcome visible to the property.
Payouts arrive net of fees, batched across outlets and sometimes across acquirers, which makes property-level and group-level attribution slow.
Juno carries transaction, settlement and reconciliation context together so finance can trace a payout back to the property, outlet and folio it came from.
Primary value proposition
Start with the operating context, then move into the products, solutions and integrations that make the proposition real.
Business outcomes
Collect deposits and pre-authorisations through secure, connected payment journeys tied to the reservation.
Keep reception, F&B, spa and online charges moving through one controlled payment layer across the estate.
Post accurately, see settlement clearly and reduce the manual reconciliation work that lands on finance.
Deployment patterns
One property, one acquiring relationship and a direct PMS integration — the shortest path to a controlled payment layer.
A shared operating model across properties, with per-property configuration for outlets, terminals and posting rules.
Owned, managed and franchised properties running different PMS versions, connected through the same gateway and reporting pipeline.
Platform proof
Hotel groups adopt Juno because the property layer is already integrated: the payment result returns to the folio, and the settlement record stays traceable back to the stay. Values are held in the canonical platform statistics registry and are not restated per page.
Juno connects to the property-management systems hotels already run, rather than sitting beside them as a separate payment island.
Deposits, pre-authorisations, in-stay charges and final settlement move through one payment layer tied to the reservation.
Payment, settlement and reconciliation context travels beyond the property so group finance can trace payouts to their source.
Relevant integrations
Knowledge
Juno integrates with the property-management systems hotels already run, including Oracle OPERA Cloud and OPERA 5, alongside other leading PMS platforms. The applicable integration path depends on the PMS product, its version and the deployment scope, which the 934 team confirms during solution design.
Related: Oracle integration hub, All integrations
Through a secure remote payment journey tied to the reservation rather than an ad-hoc email or phone process. The guest completes payment on a hosted page, the property sees the outcome, and card data stays out of the property's own systems and inboxes.
Related: Juno Pay-by-Link
No. Juno is the payment and financial operations layer that connects to the PMS. Reservations, folios and property operations stay in the PMS; Juno handles acceptance, orchestration, acquiring, settlement and reconciliation around it.
Groups typically standardise the operating model once and then configure per property — outlets, terminal footprint, posting rules and acquiring arrangements. Reporting rolls up to the group while remaining traceable to the property and outlet the activity came from.
Tell us which property-management system you run and how your estate is structured. We will walk through the integration path, the acquiring model and what reconciliation looks like day to day.
Still researching? Visit the Learning Centre
Related on 934
How virtual card credentials from agents and intermediaries are held and charged against the stay.
A practical guide to how hotel payment gateways connect the PMS, payment infrastructure and acquirer, and why those boundaries matter for hotel operations.
A practical framework for hotel payment SOPs — how payments should be posted, authorised, refunded, checked at night audit and reconciled to settlement, with 12 controls and a reusable template.
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.
What has to match before finance can close.
Oracle Hospitality integration context from the team.
