Every spa charge posts straight to the guest's folio in your PMS and settles at checkout — nothing re-keyed at the front desk.
When a guest charges a treatment to their room, AURI posts it to their hotel folio through the PMS connector. It lands on the final bill next to the minibar and the late checkout. The front desk re-keys nothing.
The spa stops being a separate cash desk. It becomes a line on the folio.
Fully wired: guest lookup, check-in verification, charge posting to the room folio, and VIP profile read. Today, Mews is the only connector where AURI detects a VIP guest. A posted charge is reversed by your team in Mews directly; its API exposes no void method.
Guest lookup, check-in verification, and charge posting with your cashier ID, through Oracle's Hospitality Integration Platform over OAuth2. Voiding a charge is a front-desk step for now, not an automated call.
Fully wired: guest lookup, check-in verification, charge posting, and charge void. Of the connectors live today, Cloudbeds is the only one that voids a mis-posted charge from AURI directly.
Charge posting is live: the spa charge posts to the guest's folio under its own segment ID, so spa revenue lands in the right segment of your reports. A posted charge is reversed in Previo directly; its API exposes no void method.
The adapter is code-complete, charge void included, but not yet selectable in a live configuration. We'd rather give you a straight date on the call than imply it's ready today.
These are PMS systems we have built connectors for — not customers, not “integration partners,” not endorsements. Status, not affiliation.
AURI is built to add PMS connectors. A new one typically takes 4–6 weeks to build, wire, and validate against your environment.
The question on the intro call isn't “do you support my PMS?” — it's “how soon, and on what terms?”
How guests pay and how they're reminded is set per market and per property, not left for later.
Stripe runs embedded card payments for European properties: Apple Pay, Google Pay, SCA, 3DS2. Tap covers the Gulf with a redirect flow: KNET, Mada, and local cards. Charge-to-room posts to the folio through the PMS connector. A venue that settles at the desk runs cash mode, so the booking is tracked in full while payment happens at reception.
Every booking is confirmed, then reminded. Email goes 48 hours and 24 hours ahead (Resend, with SMTP fallback). SMS goes 2 hours ahead (SMSAPI in the EU, Twilio elsewhere), with regional sender IDs supported. WhatsApp is on the roadmap: built in the codebase, not yet wired into the production reminder flow.
Live today: Mews, Opera Cloud (OHIP), Cloudbeds, and Previo, with RoomRaccoon in final wiring. For any other PMS, a new connector typically takes 4–6 weeks to build, wire, and validate. We'll confirm your specific PMS on the intro call.
The spa charge posts to the guest's hotel folio through the PMS connector and appears on the room bill immediately. At checkout, the guest settles one bill with the spa line included. No card swipe at the spa, no chit walked to the front desk, no reconciliation later.
Real-time per transaction, not a nightly batch. A charge posts the moment it happens, and a guest is looked up the moment they book. The hotel bill matches the AURI screen in the same minute.
No. They are PMS systems we built connectors to, nothing more. We are not affiliated with Mews or Oracle, not endorsed by them, and not their customers.
Not sure where your setup fits? Book my intro call and ask it there.
Tell us what your hotel runs. You'll get a straight answer on how the spa charge reaches the folio, and on timing, with no obligation.