Simplify hotel payments with SOTpay for OPERA Cloud. Guests complete payment securely on their own device, and every stage of the process is recorded back in the PMS as clear, time-stamped notes.
Front desk and finance get a complete view of each payment journey, manual follow-up drops away, and card details stop passing through your property at all.
The workflow is closed-loop. It starts in OPERA and it finishes in OPERA, which is the part that matters to anyone who has spent a morning reconciling folios.
Because the request is raised against a specific folio, the payment arrives attached to the right reservation instead of landing as a receipt somebody has to match up later.
Hotels handle card details in more places than almost any other business. Reservations by phone, deposits by email, cards written on booking forms, and details left sitting in PMS notes long after the guest has gone.
SOTpay removes the need for any of it. The guest enters their card details on SOTpay's secure page, never to a receptionist and never into OPERA. The PMS receives the payment status and the posting, not the card number, which takes your property and your staff out of PCI DSS scope and removes a category of risk that is otherwise very hard to train away.
A payment request is raised from OPERA against the reservation or folio, and the guest receives a secure branded link they can pay from on their own device. Once paid, the transaction posts automatically to the folio and every stage is written back into the PMS as a time-stamped note.
Oracle is moving OPERA Cloud properties from the older Shared Security Domain model onto OPERA Cloud Identity Management, which handles user access and the authentication behind API connections. The SOTpay integration is designed to work with OPERA Cloud properties on either side of that migration, so moving to OCIM does not mean rebuilding your payment workflow. If you are mid-migration and want the specifics for your property, our team can confirm them directly.
Yes. The payment posts to the folio automatically once the guest completes it, and the status is visible in the PMS. Front desk and finance are looking at the same picture rather than one chasing the other for confirmation.
No. Guests enter their card details on SOTpay's secure hosted page, not to a member of your team and not into OPERA. The PMS receives the payment status and the posting, never the card number, which keeps the property out of PCI DSS scope.
Yes. Pre-arrival settlement is one of the most common uses. The guest pays before they travel, which shortens check-in, reduces queues at the desk, and means the balance is not being chased at the point the guest is trying to get to their room.
Yes. Deposits, staged payments in the run-up to an event, incidentals during the stay and balances after departure are all handled the same way, each raised against the relevant folio.
Because payments are authenticated with 3-D Secure and the guest completes them personally, fraud liability shifts to the card issuer. That is a material difference from a card number read out over the phone, where the property carries the risk if it is later disputed.
SOTpay also integrates with Cloudbeds, and connects to other booking engines and property systems through APIs and middleware. If you run a mixed estate, tell us what is in it and we will tell you what is possible.
More on how SOTpay works with Oracle OPERA PMS and across hotels and hospitality. For the other systems SOTpay connects to, see the integrations page.
Our payment specialists will walk you through the full guest payment journey, from the request raised in OPERA to the posting landing back on the folio, and what setting it up would involve for your property. No obligation.
