Skip to content
Bartender serving a guest at the bar, representing the hotel and food and beverage outlets that Shiji Daylight PMS and Shiji Infrasys POS run, connected to payments through Juno.

Juno Integration Ecosystem · Shiji

One payment layer across Shiji PMS and POS

Juno connects Shiji Daylight PMS and Shiji Infrasys POS to the payment ecosystem, so hotels, restaurants and hospitality groups can manage property and outlet payments through one integration layer.

Explore Juno Hospitality

Hospitality groups running Shiji rarely run only one Shiji system. The property runs on Shiji Daylight PMS while the restaurants, bars and other outlets run on Shiji Infrasys POS — and payment is too often designed twice, once per environment, then again per provider and per market.

Juno is the payment integration and orchestration layer between those Shiji environments and the payments ecosystem, so payment behaves consistently across property and outlet without replacing the systems the operation already runs on.

The integration challenge

Two hospitality environments. One payment problem.

The difficulty is rarely a single connection. It is the number of separate payment integrations an estate accumulates across property systems, outlet systems, providers and markets.

PMS and POS payment are designed separately

Property payment and outlet payment are usually procured, integrated and supported as two projects, even when the same group, the same finance team and often the same guest journey sit behind both.

Juno sits behind both Shiji Daylight PMS and Shiji Infrasys POS, so property and outlet payment are designed, supported and changed once rather than twice.

Every new provider or market becomes another integration

Connecting hospitality systems directly to each payment provider means repeating integration and testing work each time an acquiring relationship, provider or market changes.

Juno reduces the need to rework the Shiji connection when payment relationships change, keeping more of that change within the payment layer.

Payment information is moved by hand

Where payment activity is not integrated with the operational record, teams re-key payment and transaction information between the terminal, the PMS and the POS — slow at the desk, error-prone at night audit.

Supported payment outcomes can be returned to the Shiji environment that initiated the transaction, reducing manual movement of payment information between systems.

Finance sees the estate in fragments

A group operating multiple properties and outlets can end up reconciling property payments and outlet payments through different routes, different providers and different reports.

Routing both environments through Juno gives finance a single place to trace supported transaction, settlement and reconciliation context across the estate.

Explore Juno Financial Suite

Integration overview

One Juno integration layer across the Shiji ecosystem.

Juno connects the Shiji environments a hospitality group already runs to supported payment services, without a separate payment project per system. Each system keeps its operational role; Juno provides the payment layer between the Shiji environments and the wider payments ecosystem.

Shiji Daylight PMS

Hotel property management system

Shiji Daylight PMS runs the property: reservations, stays, charges and the guest folio. Juno provides the payment layer around it — deposits and balances before arrival, payment at the desk, and supported posting of payment outcomes back to the folio — so hotel payment workflows stay inside the system the front office already uses.

Explore Juno Hospitality Suite

Shiji Infrasys POS

Restaurant, bar and F&B point of sale

Shiji Infrasys POS runs the outlets: the check, the counter and the table. Juno connects outlet payment acceptance to the same payment layer as the property, so restaurant and F&B payment activity is part of the group's payment environment rather than a separate island of terminals and reports.

Explore Juno F&B Suite

Juno

Hospitality payment integration and orchestration layer

Juno sits between the Shiji environments and supported payment services, covering payment acceptance, tokenisation and orchestration where those capabilities are supported for the deployment. The architecture reduces the need to rebuild the Shiji connection when payment relationships change.

See how payment integration works

Acquiring & payment ecosystem

Acquiring, processing and payment methods by market

Juno connects to supported acquiring and payment services across the markets it operates in. Supported providers, payment methods and channels vary by market and are confirmed per deployment.

See payment coverage

Integration interfaces

Where the connection is made.

Shiji Daylight PMS integration

Juno integrates with Shiji Daylight, the hotel property management system, for property payment workflows. Supported flows are confirmed against the property's Shiji Daylight deployment and operating model during solution design.

Shiji Infrasys POS integration

Juno integrates with Shiji Infrasys, the hospitality point-of-sale system, for restaurant, bar and F&B payment workflows across outlets. Supported flows are confirmed against the outlet estate and its service models during solution design.

A shared payments architecture

Both integrations resolve to the same Juno payment layer, so acceptance, tokenisation, orchestration and downstream financial context are engineered once for the estate rather than once per system.

Reference architecture

Shiji, Juno and the payment ecosystem.

Both Shiji environments connect to Juno, which in turn connects to the acquiring and payment ecosystem and on to settlement and reconciliation context for finance.

SHIJI HOSPITALITY ENVIRONMENTS Shiji Daylight PMShotels — property, reservations,stays and the guest folioroom, deposit and balance payment Shiji Infrasys POSrestaurants, bars and F&B outlets —the check and the outletcounter and table payment PAYMENT LAYER Juno payment layeracceptance · tokenisation · orchestrationone integration layer for both environments ACQUIRING & PAYMENT ECOSYSTEM Acquiring & payment ecosystemsupported acquiring, processing and payment methods by market Financial operationstransaction visibility · settlement · reconciliation
Reference model. Supported flows, providers and payment methods vary by deployment and market; not every capability is available identically everywhere.

Business outcomes

Payments that fit the operating model.

Hotels running Shiji Daylight

Connect property payment workflows to supported payment services without building and maintaining a bespoke integration, and without moving payment information between systems by hand.

Restaurant and F&B operators on Shiji Infrasys

Bring outlet payment into the same payment environment as the rest of the business, so counter and table payment are engineered and supported the same way everywhere.

Hospitality groups running both

Use a common payments architecture across properties, outlets, providers and markets instead of a different arrangement per system and per site.

Platform proof

One platform behind every integration.

Shiji Daylight and Shiji Infrasys deployments connect through the same Juno platform, gateway and acquiring relationships as every other integration.

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

Payment infrastructure built for hospitality

934 specialises in hotel, restaurant and hospitality payment environments. Juno is designed around how properties and outlets operate, and how payment needs to work across them.

One layer across PMS and POS

Property and outlet payment are served by the same architecture, so a group does not have to run and maintain two of everything to cover hotels and outlets.

Scoped against the real deployment

Supported flows, providers and payment methods are confirmed against the estate's Shiji environments, markets and operating model during solution design rather than assumed.

Knowledge

Juno and Shiji — questions answered

Quick facts

Shiji systems in scope
Shiji Daylight property management system for hotels, and Shiji Infrasys point of sale for restaurants, bars and other food and beverage outlets.
What Juno provides
The payment integration and orchestration layer between Shiji environments and supported payment services — acceptance, tokenisation, orchestration and downstream financial context.
Relationship
Juno complements Shiji. 934 does not own, resell or form part of Shiji, and Juno does not replace Shiji's property-management or point-of-sale products.
Scope confirmation
Supported flows, payment providers, payment methods and markets vary by deployment and are confirmed with 934 during solution design.

Frequently asked questions

Does Juno integrate with Shiji Daylight PMS?

Yes. Juno, the hospitality payment platform from 934, integrates with Shiji Daylight PMS. Juno provides the payment layer around the property management system — deposits and balances, payment at the desk, tokenisation and orchestration — and connects that activity to the payment services Juno supports. Supported flows are confirmed against the property's Shiji Daylight deployment during solution design.

Related: Juno Hospitality Suite, Payment integration

Does Juno integrate with Shiji Infrasys POS?

Yes. Juno integrates with Shiji Infrasys POS and connects outlet payment — acceptance at the point of sale, tokenisation and orchestration — to the payment services Juno supports in the relevant market. Supported flows are confirmed against the group's Shiji Infrasys deployment during solution design.

Related: Juno F&B Suite, Payment coverage

Can Juno be used across both Shiji Daylight PMS and Shiji Infrasys POS?

Yes. Juno integrates with both Shiji Daylight PMS and Shiji Infrasys POS, so a hotel group running property systems and outlet systems can use one payment layer across both rather than a separate payment architecture per system. The Shiji systems stay in place; the supported integration path still differs per environment and per deployment, but acceptance, orchestration and financial context run on the same Juno platform.

Related: Juno integration ecosystem

How does Shiji payment integration reduce manual payment operations?

Where payment is not integrated, teams move payment information between the terminal and the hospitality system by hand, then reconcile the difference later. With Juno connected to Shiji Daylight PMS or Shiji Infrasys POS, supported payment outcomes are captured and posted back to the system that initiated them, so the operational record and the payment record are created once. That removes re-keying at the desk and in the outlet, and gives finance a single traceable path into settlement and reconciliation.

Related: Reconciliation, Settlement

Does this work for hotel groups running Shiji across several properties and outlets?

That is the case the architecture is built for. A group operating Shiji Daylight in its properties and Shiji Infrasys in its outlets can route both through the same Juno payment layer across sites, providers and markets, instead of maintaining a different payment arrangement per system and per location. Coverage varies by market and is confirmed per deployment.

Related: Hospitality

Is 934 part of Shiji?

No. 934 is an independent hospitality payment company and Juno is its payment platform. Shiji Daylight and Shiji Infrasys are Shiji products. 934 provides payment integration and orchestration alongside them, and makes no claim of ownership, resale, certification or partnership status with Shiji.

Connect Shiji to Juno.

Talk to 934 about connecting your Shiji Daylight PMS and Shiji Infrasys POS environments through a common integration layer.

Explore Juno F&B Suite

Still researching? Read the hospitality proposition

Related on 934

Explore the cluster

Validate the thinking