Skip to content
934 logo
Aerial top-down view of a cruise ship bow moving through open water.

Cruise payment orchestration

The payment orchestration layer for Oracle Hospitality Cruise.

Connect Oracle Hospitality Cruise to secure, resilient payment infrastructure and supported acquiring services through Juno — with acquiring configurable by ship across a global fleet.

Explore the Oracle integration

Why cruise operators run their payment architecture on Juno.

Built for Oracle Hospitality Cruise

Juno plugs into the Oracle Cruise environment through the standard Oracle Payment Interface (OPI).

Resilient at sea

Designed for the connectivity realities of a ship, with controlled recovery when the link returns.

Secure payment tokenisation

Guest payment credentials are tokenised on PCI DSS Level 1 infrastructure.

Global payment orchestration

One payment architecture, with acquiring configured by ship across Juno's global footprint.

Why orchestration

One payment architecture. Acquiring configured by ship.

Juno provides the payment layer between Oracle Hospitality Cruise and the acquiring ecosystem. Oracle manages the guest folio; Juno manages the payment lifecycle and connects each ship to the supported acquiring service that fits its needs.

One Juno architecture can support different acquiring strategies across the fleet — without changing how Oracle connects to payments.

Architecture

Where Juno sits in the cruise payment architecture.

Cruise payment architecture
  1. Layer 1
    Oracle Shipboard Property Management System (SPMS)

    Guest, reservation and folio management

  2. Layer 2
    Oracle Payment Interface (OPI)

    Standard payment interface

  3. Layer 3
    Juno

    Payment orchestration, tokenisation and transaction lifecycle

  4. Layer 4
    Supported acquiring services

    Payment processing, configured by ship

Each layer keeps its own responsibility. Oracle manages the guest, reservation and folio environment, OPI provides the standard payment interface, Juno provides the payment orchestration layer, and supported acquiring services process the payments beneath it.

Oracle validated

Juno integrates with Oracle Shipboard Property Management System (SPMS) through Oracle Payment Interface (OPI), supporting the cruise payment lifecycle.

The payment lifecycle

The onboard guest payment lifecycle, end to end.

A cruise account is not a single transaction. It opens against a tokenised credential, grows through the voyage as authorised spend increases, and closes into completion and settlement at voyage end — with refunds and voids handled after the fact. Juno supports each of those steps as part of one lifecycle rather than as unrelated messages.

01 · Credential

Guest, reservation and tokenised credential

The guest and reservation record stays in Oracle. A tokenised payment credential is captured for the account.

02 · Authorisation

Pre-authorisation and top-ups

The account is pre-authorised, then incrementally authorised as authorised spend grows through the voyage.

03 · Onboard

Spend across the ship

Onboard activity accumulates against one account rather than being paid for at each point of service.

04 · Close

Completion, settlement and exceptions

The account completes into settlement at voyage close, with refunds and voids handled inside the same lifecycle.

Resilience

Built for intermittent connectivity at sea.

Connectivity at sea is variable by route and by hour. Juno works with the Oracle Hospitality Cruise environment so payment operations are designed to handle degraded or unavailable shore connectivity, with controlled recovery when connectivity returns and a payment record that reconciles cleanly once the ship is connected again.

Resilience here is a property of the combined Oracle and 934 architecture, covering host-unavailable and offline scenarios, declines and payment exceptions.

Designed for degraded connectivity

Payment operations are architected around variable ship-to-shore links rather than assuming a constant connection.

Controlled recovery

When connectivity returns, recovery is managed rather than improvised.

A payment record that reconciles

Onboard payment activity lines up with the operating record once the ship is connected again.

Security

Secure payment tokenisation across the voyage

Juno protects payment credentials through tokenisation across the cruise payment lifecycle, supporting secure payment experiences from embarkation through onboard spend and settlement.

Juno Universal Tokenisation

A consistent token layer across the payment lifecycle, designed to keep payment credentials secure as payment routes change.

Protected payment credentials

Sensitive card data is replaced with secure payment tokens, reducing exposure of cardholder information throughout the payment lifecycle.

PCI DSS Level 1

Juno operates within PCI DSS Level 1 payment infrastructure.

Oracle Payment Interface

Payment interactions with Oracle Hospitality Cruise use the standard Oracle Payment Interface (OPI).

Token lifecycle and reuse can be configured around the cruise operator's requirements.

Global payment orchestration

One payment layer. Acquiring flexibility across the fleet.

Juno connects Oracle Hospitality Cruise to supported acquiring services through a single payment orchestration layer. Acquiring can be configured by ship, giving cruise operators the flexibility to support different markets, entities and payment requirements across their fleet.

With payment coverage across 75+ markets and relationships with Worldline, Global Payments and other supported acquirers, Juno provides the flexibility to build the acquiring model around the needs of the cruise operation.

Acquiring by ship

Configure supported acquiring services by vessel while Juno provides a consistent payment layer.

Multiple acquiring relationships

Connect to Worldline, Global Payments and other supported acquirers through Juno.

Global payment coverage

Support international cruise operations through Juno's payment footprint across 75+ markets.

Capability and outcome

What this means for a cruise operator.

Tokenised guest credentials

Supports secure credential reuse across the payment lifecycle, configured around the cruise operator's requirements.

Pre-authorisation and incremental authorisation

Supports the onboard account as authorised spend grows through the voyage.

Completion and settlement

The voyage closes into a settled, traceable payment record.

Refunds and voids

Post-authorisation exceptions handled inside the same payment lifecycle.

Payment-state visibility

Transaction inquiry and online-status checking show payment state directly, rather than inferring it from the operating record.

Host-unavailable and offline handling

Payment operations designed for intermittent shore connectivity.

Acquiring configured by ship

Acquiring strategy can change without changing the Oracle integration.

Secure tokenisation within PCI DSS Level 1 infrastructure

Reduced exposure of sensitive cardholder information.

Across the Juno platform

From onboard payment to financial reconciliation.

Juno Cruise Suite orchestrates the payment lifecycle. Settlement and reconciliation are provided by Juno Financial Suite, which cruise operators can add to reconcile acquirer settlement against onboard activity and post into finance systems across a fleet. Two suites, one platform.

Explore Juno Financial Suite

Deployment

From architecture review to a working deployment.

Deployment is implementation work, sized per operator, acquirer and vessel.

  1. 01

    Architecture review

    Map the Oracle Cruise environment, onboard estate and existing payment arrangements.

  2. 02

    Payment and acquiring route

    Select the Juno payment route and acquiring services appropriate to the fleet and its itineraries.

  3. 03

    Customer and acquirer configuration

    Configure the deployment with the operator and the selected acquiring services.

  4. 04

    Ship and operator testing

    Test per operator, acquirer and vessel as part of implementation.

  5. 05

    Deployment

    Roll out by ship, on the same Juno payment architecture across the fleet.

Discuss your cruise payment architecture.

Tell us about your Oracle Cruise environment, your fleet and your acquiring position, and we will walk through how Juno would sit in it.

Explore the Oracle integration

In summary

Juno Cruise Suite — the essentials

Quick facts

Purpose
The payment orchestration layer between Oracle Hospitality Cruise and the payment layer, supporting the onboard payment lifecycle.
Oracle integration
Integrates with the Oracle Shipboard Property Management System (SPMS) through the Oracle Payment Interface (OPI).
Acquiring
Configurable by ship. Juno connects to Worldline, Global Payments and other supported acquirers through a single payment orchestration layer.
Security
Secure payment tokenisation across the payment lifecycle, within PCI DSS Level 1 payment infrastructure.

Related on 934

Continue exploring

Oracle integration

Across the Juno platform

Cruise in context

Problems it solves

Knowledge

Juno Cruise Suite — questions answered

What is the Juno Cruise Suite?

Juno Cruise Suite is the payment orchestration layer for Oracle Hospitality Cruise environments. It sits between the Oracle Shipboard Property Management System (SPMS) — through the Oracle Payment Interface — and the payment layer beneath it, supporting the onboard payment lifecycle from tokenised guest credentials and pre-authorisation, through incremental authorisation as authorised spend grows during the voyage, to completion, settlement, refunds and voids. Unlike a gateway, which terminates a transaction, the orchestration layer manages the lifecycle and the routes beneath it.

Related: Oracle integration hub

Which payment operations does Juno support in an Oracle Cruise environment?

Juno supports tokenisation and token exchange including bulk guest token operations, sale, pre-authorisation and incremental or top-up authorisation, authorisation release and reversal, completion and settlement, refunds and voids, transaction inquiry and online-status checking, host-unavailable and offline scenarios, declines and payment exceptions, and behaviour under multiple guest tokens and rapid pre-authorisation messaging through OPI Manager.

How does the onboard guest account work?

The guest and reservation record stays in Oracle Hospitality Cruise. A tokenised payment credential is captured against the onboard account and pre-authorised, then incrementally authorised as authorised spend grows through the voyage. Onboard activity accumulates against the account rather than being paid for at each point of service, and the account completes into settlement at voyage close, with refunds and voids handled inside the same payment lifecycle.

What happens when connectivity drops at sea?

The combined Oracle and 934 payment architecture is designed for the realities of intermittent ship-to-shore connectivity. Payment operations are designed to handle degraded or unavailable shore connectivity, with controlled recovery when connectivity returns and a payment record that reconciles once the ship is connected again.

Which acquirers can a cruise operator use?

Acquiring is configurable by ship, so a fleet operating across regions is not forced onto a single relationship. Juno connects Oracle Hospitality Cruise to supported acquiring services through a single payment orchestration layer, with payment coverage across 75+ markets and relationships with Worldline, Global Payments and other supported acquirers. This gives cruise operators the flexibility to build the acquiring model around the markets, entities and payment requirements of the operation.

How is cardholder data protected?

Juno protects payment credentials through tokenisation across the cruise payment lifecycle, with Juno Universal Tokenisation providing a consistent token layer as payment routes change. Sensitive card data is replaced with secure payment tokens, reducing exposure of cardholder information, and Juno operates within PCI DSS Level 1 payment infrastructure. Token lifecycle and reuse can be configured around the cruise operator's requirements.

Related: Juno Universal Tokenisation

Where do settlement and reconciliation sit?

Juno Cruise Suite orchestrates the payment lifecycle. Settlement reconciliation and posting into finance systems are provided by Juno Financial Suite, which cruise operators can add to reconcile acquirer settlement against onboard activity across a fleet. Two suites, one platform.

Related: Juno Financial Suite

What does a cruise deployment involve?

Deployment is implementation work rather than technical qualification. It runs through architecture review of the Oracle Cruise environment and onboard estate, selection of the Juno payment route and acquiring services, configuration with the operator and the selected acquiring services, testing per operator, acquirer and vessel, and rollout by ship on the same Oracle-facing payment architecture.