Cruise operators
Payments built for life at sea. See how Juno helps cruise operators manage secure payments, ship-level acquiring and global payment operations across the fleet.
A cruise is a closed economy that moves. Guests spend across restaurants, bars, retail, spa and excursions on a single onboard account, while connectivity to shore varies by route and by hour. The payment layer has to keep working when the link degrades, then reconcile cleanly once the ship is connected again — and it has to do so per voyage, per ship and across a fleet. Juno Cruise Suite is built around that operating reality rather than adapted from a land-based model.
The operating challenge
Every constraint in cruise payments comes back to two facts: the guest account is shared across many outlets, and connectivity cannot be assumed.
Satellite links vary by route and by conditions, so a payment architecture that assumes a live connection will fail at sea.
The combined Oracle and 934 payment architecture is designed for degraded or unavailable shore connectivity, with controlled recovery when the link returns.
Restaurants, bars, retail, spa and excursions all post to the same guest account, often with different operators and revenue-share arrangements behind them.
Oracle manages the guest folio across the onboard environment; Juno manages the payment lifecycle behind it, from tokenised credentials and authorisation through completion and settlement.
Settlement lands after the voyage ends, batched across ships and currencies, which makes per-voyage financial closure slow.
Payment, settlement and reconciliation context is carried per ship and per voyage, giving finance a traceable path from spend to payout.
Primary value proposition
Start with the operating context, then move into the products, solutions and integrations that make the proposition real.
Business outcomes
Support payment journeys across onboard locations and changing connectivity conditions.
Bring onboard activity and shoreside operations into a more coherent financial workflow.
Give finance teams the detail they need across payments, settlement and voyage operations.
Deployment patterns
Onboard acceptance and account posting across outlets, with shoreside reporting once connected.
A consistent payment configuration across ships, with per-vessel and per-voyage reporting.
Voyage settlement and reconciliation handled centrally through Juno Financial Suite.
Platform proof
Cruise operators test a payment layer against connectivity, not throughput: what happens at sea, and whether the voyage still closes cleanly ashore. Values below come from the canonical platform statistics registry.
Payments run through the standard Oracle Payment Interface with the Oracle Shipboard Property Management System (SPMS), covering tokenisation, pre-authorisation and incremental authorisation, completion and settlement, refunds and voids, and host-unavailable and offline scenarios.
Restaurants, bars, retail, spa and excursions post to the same onboard account so the voyage reads as one financial narrative.
Settlement and reconciliation context is carried per vessel and per voyage rather than flattened across the fleet.
Relevant integrations
Knowledge
Juno provides a consistent payment layer while supported acquiring services can be configured by ship, allowing operators to adapt their acquiring model to different vessels, entities and markets.
Juno provides payment coverage across 75+ markets, connecting cruise operators to supported acquiring services while maintaining a consistent payment architecture across the fleet.
Yes. Payment, settlement and reconciliation context is carried per ship and per voyage, which gives shoreside finance a traceable path from onboard spend through to the payout that covers it.
Related: Juno Financial Suite
Operators standardise the payment configuration once and apply it per vessel, with reporting broken down by ship and voyage. New vessels join the same operating model rather than being configured from scratch.
Share your fleet profile, onboard systems and connectivity constraints. We will map the acceptance, settlement and reconciliation path per voyage.
Still researching? Visit the Learning Centre
Related on 934
A practical guide to how hotel payment gateways connect the PMS, payment infrastructure and acquirer, and why those boundaries matter for hotel operations.
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.
How voyage spend is matched to settlement.
Integration context from the team.
