From request to reconciled, in four steps.
Integrated where your team already works.
Juno Pay-by-Link works alongside your existing payment setup and integrates directly with Oracle Opera Cloud. Links relate to the reservation, payments post back and reconcile against the folio, and tokenisation keeps card data out of the PMS — reducing your PCI scope rather than adding to it.
- PMS-integratedFits the Opera Cloud workflow your front desk and finance teams already use.
- Automatic reconciliationPayments match back in Juno, no spreadsheet chasing.
- Tokenisation, reduced PCI scopeCard data is tokenised and kept out of staff hands and the PMS.
- Works with your existing setupRuns alongside terminals and other payment methods, not instead of them.
- No hardwareNothing to install or maintain; it's a capability, not a device.
Requires existing — or transition to — Worldline or Getnet acquiring.
One link, many moments.
- Deposits & pre-arrivalSecure a booking before the guest arrives.
- No-show & cancellation chargesCollect what's owed without a card on file.
- Balance settlementClose out a folio remotely after checkout.
- Phone & email bookingsReplace insecure card-over-phone with a link.
- Group & event depositsRequest larger or split payments cleanly.
- Virtual & remote payersLet a third party (company, travel agent) pay for the stay.
See it in a real hotel workflow — in two minutes.
Watch how hotel teams use Juno Pay-by-Link to request payments, get paid instantly, and eliminate card details from email and phone calls — from front desk to finance.
- Creating a one-time payment link
- Guest payment on mobile or desktop
- Instant payment confirmation
- Automatic reconciliation in Juno
Knowledge
Juno Pay-by-Link (for Oracle Opera Cloud) — questions answered
Quick facts
- Purpose
- A capability within Juno for secure remote card capture — a one-time payment link that replaces card details taken by phone or email.
- Target customers
- Hotels running Oracle OPERA Cloud.
- Integration
- Oracle OPERA Cloud — links relate to the reservation; payments post back and reconcile against the folio.
- Delivery channels
- Email, SMS or WhatsApp; no app or hardware required for the guest.
- Security
- PCI-compliant; cards are tokenised and kept out of the PMS, which reduces PCI scope.
- Pricing
- Contact 934 for current Pay-by-Link pricing.
- Requirement
- Existing — or transition to — Worldline or Getnet acquiring.
- Activation
- A few days, guided by the 934 team.
- Typical use cases
- Deposits and pre-arrival, no-show and cancellation charges, balance settlement, phone and email bookings, group and event deposits, third-party payers.
Frequently asked questions
What is Juno Pay-by-Link?
Juno Pay-by-Link is a capability within Juno for taking secure payments without handling card details by phone or email. A staff member generates a one-time payment link tied to a guest's reservation or folio and sends it by email, SMS or WhatsApp; the guest pays from their own device, and the payment is confirmed and reconciled. Because the link handles capture, staff do not enter the card number, and the card is tokenised rather than exposed. It is PCI-compliant and integrated with Oracle OPERA Cloud, so payments post back and reconcile against the folio. Pay-by-Link runs alongside a property's existing terminals and methods, and requires Worldline or Getnet acquiring.
Related: Juno Hospitality Suite, Payment orchestration
How does Pay-by-Link work end to end?
Pay-by-Link follows four steps. A staff member creates a one-time payment link tied to the guest's reservation or folio; the link is delivered by email, SMS or WhatsApp, with no app or hardware needed on the guest's side; the guest pays from their device and the card is tokenised; and the payment is confirmed and reconciled in Juno, with the result reflected against the OPERA Cloud folio. Because the payment record is tied to the reservation from the moment the link is created, it can be matched back automatically rather than reconciled by hand.
Related: How Juno posts to OPERA Cloud, Reconciliation
How does Pay-by-Link reduce PCI scope?
Pay-by-Link reduces PCI scope by keeping card data out of the places it is hardest to protect — phone calls, emails and staff workflows. The guest enters their details directly into a secure payment page reached through the link, rather than reading a card number to a staff member. The card is then tokenised, so a reusable token replaces the raw card data for any later action. Because the card number is not handled by staff and is kept out of the PMS, those systems and people fall outside parts of the PCI DSS obligation that applies wherever card data is stored, processed or transmitted. Tokenisation is described in more detail under payment orchestration.
Related: Payment orchestration, Juno Hospitality Suite
How does Pay-by-Link integrate with Oracle Opera Cloud?
Pay-by-Link is built for Oracle OPERA Cloud. Each link relates to a specific reservation, so the payment is associated with the right guest and folio. When the guest pays, the payment posts back and reconciles against the OPERA Cloud folio, and tokenisation keeps the card data out of the PMS. It runs alongside the property's existing payment setup — terminals and other methods continue to work — so it is an added capability within the OPERA Cloud workflow rather than a replacement for it. To use Pay-by-Link, a property needs Worldline or Getnet acquiring — an existing relationship or a transition to one — because the acquirer settles the payments the links capture. Activation typically takes a few days, guided by the 934 team; contact 934 for current pricing.
Related: Acquiring, Juno Hospitality Suite, Contact 934
When would a hotel use Pay-by-Link?
Pay-by-Link covers the moments when a guest needs to pay but is not at a terminal. Common uses include securing deposits and pre-arrival payments, collecting no-show and cancellation charges without a card on file, settling a folio balance remotely after checkout, and replacing card-over-phone for telephone and email bookings. It also supports group and event deposits, where larger or split payments are requested, and third-party payers — for example a company or travel agent paying for a guest's stay. In each case the link removes manual card handling and ties the payment to the reservation, so it can reconcile automatically.
Related: Juno Hospitality Suite, Reconciliation