Payment processor · reference
Cloudbeds Payments
Cloudbeds Payments is the bundled payment processor inside Cloudbeds PMS. Native integration with the folio means authorisation, capture and refund flow without third-party gateway integration.
Target segment
Properties already running or considering Cloudbeds PMS wanting native payment processing without third-party gateway setup.
Pricing
Pricing is bundled with Cloudbeds PMS subscription with per-transaction fees similar to standard merchant rates (around 2.5-3% for online, lower for in-person).
Source: Cloudbeds Payments
Strengths
Native PMS integration
Authorisation hold tied to the reservation; updates automatically on cancellation or modification.
Single-vendor support
Payment issues handled by the same support team as the PMS.
Pre-arrival auth automation
Two-stage auth (validation hold at booking, full hold 48h pre-arrival) automated natively.
Trade-offs
Only available with Cloudbeds PMS
Not a standalone processor; commits the property to Cloudbeds PMS.
Less competitive at very high volume
For properties over USD 1M monthly volume, Adyen Interchange++ typically becomes cheaper.
When to choose
Choose Cloudbeds Payments when the property is on Cloudbeds PMS and wants minimum vendor count plus native folio integration.
When to avoid
Avoid when the property is not on Cloudbeds PMS or wants payment processor flexibility independent of PMS choice.
Common integrations
Cloudbeds PMS, Cloudbeds Distribution, Cloudbeds Engagement (Whistle).
Editorial disclosure
This site is operated by Maciej Dudziak, founder of Guestivo. Guestivo is guest-journey software (not a payment processor) and is intentionally absent from /payment-processors/ recommendations.