Juno Integration Ecosystem · Clock PMS
Juno connects Clock PMS to Worldline and a global payment ecosystem spanning more than 75 markets, so hotels and hotel groups reach payment services without a new PMS project per market.
Hotels running Clock PMS need payments to work wherever they operate — not only where a single acquiring relationship reaches. Juno provides the payment integration and orchestration layer between Clock PMS and the wider payments ecosystem, so the property reaches supported payment connectivity across more than 75 markets.
The integration challenge
The integration effort rarely stops at the first acquirer. Every new market, provider or acquiring relationship risks another project against the same property management system.
Connecting a property management system directly to each acquirer means repeating integration, testing and certification work every time the payment relationship changes.
Juno absorbs that change in the payment layer, so it happens away from the Clock PMS connection.
Groups expanding across borders meet different acquiring relationships, payment providers and local requirements, none of which the PMS was designed to arbitrate.
Juno sits between Clock PMS and the payments ecosystem, providing a consistent connection while the underlying payment relationships vary by market.
A group operating multiple properties can end up with a different payment architecture per hotel, each with its own integration history.
Connecting every property through the same Juno layer gives the group a consistent payment architecture rather than a per-property arrangement.
Payment activity may post correctly in the property while finance still reconciles settlement across acquirers and properties by hand.
Juno carries supported transaction and settlement context beyond the property, so finance can trace activity back to its source.
Integration overview
Hotels using Clock PMS can connect through Juno to supported payment services without creating and maintaining a separate PMS integration for every acquiring relationship or market. Each layer has a distinct role.
Hotel property management system
Clock PMS runs the property: reservations, stays, charges and the guest folio. Juno does not replace it. The integration is with Clock PMS specifically.
Hospitality payment integration and orchestration layer
Juno provides the integration and orchestration layer between Clock PMS and supported payment services, so the payment relationship can change without rebuilding the PMS connection.
Explore Juno Hospitality SuiteAcquiring and payment connectivity, including Worldline
Worldline is one supported acquiring route through Juno. Juno's payment connectivity reaches beyond any single acquirer, extending to supported services across more than 75 markets.
Explore acquiringIntegration interfaces
Juno integrates with Clock PMS, the property management system. Supported payment flows are confirmed against the property's Clock PMS deployment and operating model during solution design.
Juno provides the middleware enabling Clock PMS connectivity with Worldline acquiring for supported deployments. Worldline is a supported route through Juno rather than the boundary of Juno's payment reach.
Reference architecture
One flow: Clock PMS connects to the Juno payment layer, and Juno connects to the acquiring and payment ecosystem — Worldline among the supported acquiring routes — providing payment connectivity across more than 75 markets.
Relevant Juno products
Business outcomes
Connect Clock PMS to supported payment infrastructure without building and maintaining a bespoke integration.
Use a consistent PMS-to-payments integration architecture across multiple properties and markets rather than a per-property arrangement.
Extend Clock PMS payment connectivity into markets requiring different acquiring or payment relationships, without rebuilding the PMS connection market by market.
Platform proof
Clock PMS properties connect through the same Juno platform, gateway and acquiring relationships as every other deployment. Values below come from the canonical platform statistics registry.
934 works in hotel systems and hotel payment workflows, not generic middleware. The value is in understanding how a property operates and how payments have to behave around it.
One connection from Clock PMS to Juno provides a route to payment connectivity across more than 75 markets, including markets outside a single acquirer's footprint.
Supported flows are confirmed against the property's Clock PMS deployment, markets and operating model during solution design rather than assumed.
Knowledge
Yes. Juno provides the middleware connecting Clock PMS with Worldline acquiring for supported deployments. The applicable scope is confirmed with 934 during solution design.
Juno sits between Clock PMS and the payment ecosystem, providing the integration and orchestration layer required to connect hotel payment workflows with supported payment services. Clock PMS continues to run the property, reservations and guest folio.
Related: Juno Hospitality Suite
Juno provides payment connectivity across more than 75 markets, enabling a broader international payment strategy than a single acquiring relationship. Supported providers, payment methods and flows are not identical in every market and are confirmed per deployment.
No. The current Juno integration is specifically with Clock PMS, the property management system.
Yes. The architecture is particularly relevant for groups that want a consistent connection between Clock PMS and payments while operating across multiple properties or markets.
No. Juno acts as the payment integration layer alongside Clock PMS. The property management system stays in place.
Talk to 934 about connecting your Clock PMS estate to Worldline and Juno's wider payment ecosystem.
Still researching? Read the hospitality proposition
Related on 934
See the wider Juno integration ecosystem.
See the market proposition around hotels and groups.
Explore the product layer behind the integration.
Move from integration context into implementation.
How PMS, gateway, terminals and ERP are actually wired together.
Which flows are supported, and what determines the integration path.
The pre-arrival collection journey tied to the reservation.
