Hospitality estates
Active payment locations are hotel receptions, restaurants, spas, retail and onboard outlets — the departments hospitality operators actually run.
We work in one industry. Reservations, folios, deposits, incidentals and multi-outlet estates are the design brief, not an adaptation of a generic acceptance layer.
Hotels & Resorts →Payments are posted against the right reservation, folio and ledger entry inside the systems your teams already work in.
Payment integration →Acquiring is a component of the platform, not the platform itself, so commercial terms and market coverage can change without re-integrating.
Acquiring →Acceptance, routing, tokenisation and posting are operated together as one flow rather than stitched together across vendors.
Products →Reception, restaurant, spa, retail and onboard outlets run on the same platform instead of a different payment stack per department.
Juno Hospitality Suite →Responsibility does not stop at authorisation — settlement, reconciliation and the path into the ledger are part of the same platform.
Juno Financial Suite →934 is a focused, accountable, learning execution organisation. We take end-to-end responsibility for customer outcomes, prioritise relentlessly, share knowledge actively, and turn every solved customer requirement into scalable platform capability.
Much of that work happens alongside others — acquirers, PMS and POS vendors, system integrators and hospitality technology partners. See how we work with partners →
We own the customer outcome from end to end, including the parts delivered alongside our partners.
We name the risks, the bad numbers and the operational bottlenecks plainly.
We make decisions based on what delivers the greatest value for the customer, recognising the important contribution our partners make.
We finish what we start before we begin something new.
Every solution is documented, shared and made reusable.
By the numbers
Every figure here comes from the canonical statistics registry — the same numbers used everywhere else on the site.
Active payment locations are hotel receptions, restaurants, spas, retail and onboard outlets — the departments hospitality operators actually run.
Supported PMS, POS and ERP integrations, including the Oracle Hospitality ecosystem.
The platform is operated to PCI DSS Level 1, the standard hospitality groups are audited against.
In summary
Where to go next
Knowledge
Because payments in hospitality fail at the seams rather than at the terminal: a charge taken at the table that never reaches the folio, a deposit that cannot be matched at month end, an estate where every property reconciles differently. 934 is chosen when an operator wants those seams closed by a partner that understands reservations, folios, pre-authorisations and multi-outlet estates, rather than a generic acceptance layer configured to fit.
Related: Native PMS payment integration, Reconciliation
A traditional provider bundles the platform and the acquiring together, so changing acquirer means changing infrastructure. 934 separates the two: Juno is the platform, and acquiring sits behind it as a commercial relationship that can be chosen, changed and optimised without re-integrating the estate. That separation is the reason a group can renegotiate or add acquiring capability without another integration project.
Yes. Juno is the platform layer, so an operator can adopt the integration, orchestration and reconciliation capability first and keep the existing acquiring relationship in place. Acquiring can then be reviewed on its own timetable, as a commercial decision rather than a technical one.
Related: Hospitality acquiring
Juno integrates with the PMS, POS and ERP platforms hospitality operators already run, including Oracle OPERA Cloud and OPERA v5, Oracle Simphony, SIHOT and Shiji. Each supported integration is documented on the integrations hub, including what is posted back to the folio and the ledger.
Related: Supported PMS & POS integrations, Oracle Hospitality
Juno sits between the operational systems and the payment rails. Property teams keep working in the PMS and POS they already use; Juno captures the payment, posts it against the correct reservation, folio or outlet, and carries the same record through to settlement and reconciliation in the finance system. Nothing in the operational estate is replaced.
Related: Juno Hospitality Suite, Juno Financial Suite
Start with a conversation about the estate: which systems are in place, which markets are in scope and where payments currently break down. The contact route puts that in front of the right regional and functional team, and scoping follows from there. Technology vendors and implementation partners have their own route through the partner programme.
Related: Contact 934, Partner with 934
Ready when you are
Whether you run hotels, build hospitality software or implement it, 934 connects the systems that move your money — securely, transparently, end to end.