Built for Hospitality Software
Hospitality payment processing
from booking to checkout
CSIPay is the embedded payments platform for hotel and hospitality software within the Constellation ecosystem. Reservations, deposits, folios, and card on file, all running inside your product.
A hotel stay is one guest, one folio, and a dozen transactions.
Hospitality money follows the folio. A booking deposit secures the reservation weeks out, a card is held at check in, and then the stay accumulates: room nights, the restaurant, the spa, the minibar. At checkout, the hold converts to the final folio charge, and every outlet's revenue has to land in the right bucket. Booking deposits and folio settlement are where property software earns its keep, and where bolted on processors fall apart.
Multi outlet properties raise the stakes: the restaurant and the front desk are different profit centers that settle separately even when the guest charges everything to the room. CSIPay embeds hotel folio payments and multi outlet settlement inside your platform, so the guest sees one bill and the property books each outlet correctly.
Everything property software needs around the folio.
Booking deposits
Collect a deposit at reservation that secures the booking and applies to the final folio.
Check in card holds
Hold the guest's card at check in and convert the hold to the folio charge at checkout.
Hotel folio payments
Room, dining, and incidental charges accumulate on the folio and settle as one payment at departure.
Multi outlet settlement
Restaurant, spa, and front desk revenue settles to the right outlet even when charged to the room.
Security built in
Guest cards, holds, and folio charges are protected to PCI DSS Level 1.
Revenue for your platform
Property payment volume becomes platform revenue through our partnership and PayFac as a Service models.
Payments that understand the property.
CSIPay is the embedded payments platform for Constellation Software and Jonas Group companies, including hospitality and property software. That means the payment layer is shaped around reservations, folios, and outlets rather than generic retail, and the processing relationship stays inside the ecosystem.
Guests check in every day of the year, and the platform is built accordingly: more than 4,000 merchants, PCI DSS Level 1 security, a 99.9% uptime SLA, and US and Canada coverage, including card not present payments in Canada, which is how a deposit taken at reservation actually processes.
What that means for you
- Built for hospitality software inside Constellation and Jonas Group
- One partner from the booking deposit to folio settlement
- PCI DSS Level 1 protection on guest cards and holds
- US and Canada coverage, card not present at booking and card present at the desk
Three steps from integration to first check in.
Embed the folio layer
Integrate CSIPay once and deposits, holds, and folio settlement become native to your property software.
Onboard your properties
Hotels and operators get underwritten and processing quickly, with CSIPay carrying compliance.
Grow stay after stay
Every folio settled through your platform builds your processing share. When you grow, we grow.
Hospitality payment questions.
How does a card hold at check in become the final payment?
The guest's card is authorized for an amount at check in, charges accumulate on the folio during the stay, and at checkout the hold converts to the final folio charge for the actual total. The guest pays once, and the property is covered throughout the stay.
What happens to a booking deposit?
The deposit is collected when the reservation is made and applied against the folio at checkout, so the guest's final payment reflects what they have already paid. If the guest cancels, the property applies its cancellation policy to the deposit.
How do charges from the restaurant or spa reach the guest's bill?
Outlet charges post to the guest folio during the stay, and at settlement each outlet's revenue is booked to that outlet, even though the guest paid one combined amount at checkout.
Why does hospitality software need embedded payments?
Because the folio is a living record that spans days and departments. A standalone processor sees disconnected charges, while the property needs deposits, holds, and outlet revenue unified on one guest bill. Embedding CSIPay keeps that whole lifecycle inside your software.
Run the folio end to end.
Bring hospitality payment processing into the property software your operators run on. When you grow, we grow.
Request DemoLet's build hospitality payments together
Bring embedded payments to the hospitality software your customers rely on. When you grow, we grow.