Connect Cloudbeds with SOTpay for a clearer, more controlled payment process. Guests complete payment securely through SOTpay, and each stage of the transaction is logged as a note in Cloudbeds, so your team has a full record of what happened and when.
Less uncertainty, cleaner handovers between shifts, and payment activity that is easy to track without anyone having to ask.
Your team keeps working in Cloudbeds. The payment happens outside it, and the record of that payment lands back inside it.
That last point is the one that matters day to day. The reason payment questions eat time in a small property is that the answer usually lives in somebody's head, or in a message thread, rather than on the reservation.
Properties running Cloudbeds tend to run lean. Shifts change, a duty manager covers three roles at once, and the person who took the booking is rarely the person who checks the guest in.
A time-stamped note against the reservation means the payment position is never a matter of recall. Whoever opens the booking next can see that a link was sent, whether it was opened, and whether it was paid, without chasing a colleague who is off until Thursday.
Small properties handle card details in the least controlled way of anyone in hospitality. Numbers taken over the phone, details on a booking form in a drawer, a card written into a reservation note so the night manager can charge it later.
SOTpay removes the need for all of it. The guest enters their card details on SOTpay's secure page, never to a member of your team and never into Cloudbeds. Your PMS holds the record of the payment, not the card number, which takes the property out of PCI DSS scope and removes a risk that is very difficult to manage through training alone when the team is small and busy.
A secure payment request is raised against the reservation and the guest pays through a branded link on their own device. Each stage of that transaction is logged as a note in Cloudbeds, so the reservation carries a full record of what happened and when.
The payment stages are recorded in Cloudbeds as time-stamped notes against the reservation, which gives your team a complete audit trail of the payment journey. If you need payments posting automatically to a folio rather than recorded as notes, our team can talk you through what is possible for your setup.
No. Guests enter their card details on SOTpay's secure hosted page, not to your reception team and not into Cloudbeds. Your PMS receives the record of the payment, never the card number, which keeps the property out of PCI DSS scope.
Yes. Deposits at the point of booking and balances before arrival are among the most common uses, and both mean check-in stops being a payment conversation.
Because every stage is written to the reservation as a note, whoever picks the booking up next can see whether a link was sent and whether it was paid. Nobody has to remember, and nobody has to ask a colleague who is not on shift.
Payments are authenticated with 3-D Secure and completed by the guest personally, so fraud liability shifts to the card issuer. That is materially different from a card number taken over the phone, where the property carries the risk if the charge is later disputed.
No. The connection is configured rather than built. Our team sets it up with you and confirms what is needed for your property.
Yes. SOTpay also integrates with Oracle OPERA Cloud, and connects to other booking engines and property systems through APIs and middleware. If your estate runs more than one PMS, tell us what is in it and we will tell you what is possible.
More on how SOTpay works across hotels and hospitality. For the other systems SOTpay connects to, see the integrations page.
Our payment specialists will show you how a payment request behaves against a live Cloudbeds reservation, and what setting it up would involve for your property. No obligation.
