Plugs into the stack your operation already runs.
Two PMS adapters production-ready, two more in sandbox validation. Stripe and Tap for payments. Twilio for guest comms. Public REST API for anything else.
AURI runs alongside your PMS — never instead of it. Your room nights stay where they are. AURI handles the spa side — bookings, scheduling, payments, comms — and posts charges back to the room folio. Every PMS adapter implements the same five-operation shape. We will not pretend to support what we have not built. If your PMS is not on the list, tell us — new adapters typically ship in two to three weeks.
AURI sits beside your stack, not instead of it.
The hotel stack already does what it does — reservations, room inventory, channel manager, the OTA pipeline. AURI plugs in at the spa lifecycle: booking, scheduling, payment, comms. Every guest-side action lands on the room folio through one of the five adapter calls.
Read surface is guest identity and folio target. Write surface is one charge line per spa service, plus a void path for refunds. The reservation itself is never touched.
Honest adapter status, not a logo wall.
Logo walls overpromise. This is the same surface broken into PMS, payments and comms — each row tagged with current build state. No vendor on the list that we have not actually built against.
PMS adapters
- Mews Live
Cloud PMS · folio post, guest lookup, void
- Oracle Opera Cloud Live
Enterprise PMS · OHIP folio post, guest lookup
- Cloudbeds In dev
Cloud PMS · adapter built, sandbox validated
- Previo In dev
CEE PMS · adapter built, sandbox validated
- RoomRaccoon Next
Cloud PMS · adapter scheduled next
Payments
- Stripe Live
EU + UK card acceptance, SCA, refunds, payout in 19 currencies
- Tap Payments Live
MENA acquirer — AED, SAR, BHD, KWD, OMR, QAR cards
Email · SMS · WhatsApp
- Twilio SMS Live
Reminders, magic links, 6-digit verification across 180 countries
- Twilio Email Live
Confirmations, reschedule notices, daily staff agenda
- WhatsApp Business In dev
Twilio adapter shipped — Gulf rollout pending production hookup
Status legend
Five operations. One envelope.
Every PMS adapter — current and future — implements the same five calls. Same input shape, same error codes, same audit trail. Adding a new PMS means filling in five functions; everything around them is shared infrastructure.
GETLookup guest
Find an in-house guest by name, email or booking reference. Returns folio target plus check-in window.
GETCheck status
Confirm the guest is in-house and the folio is open for charges. Returns checkout date and posting window.
POSTPost charge
Push a spa charge line to the room folio. Idempotency key per service; double-post on retry is impossible.
DELETEVoid charge
Reverse a posted line — refund path or operator correction. Audit log keeps the original and the reversal.
GETIdentify provider
Discover property and chain structure for multi-site groups. Used by the dashboard and by routing.
Idempotent · audited · retried
Every call signs a request ID, lands in a per-property audit log, retries with exponential backoff on transient PMS errors, and queues to the outbox if the PMS is unreachable.
When the PMS is unreachable, the booking still completes.
The PMS is the most fragile dependency in the stack — vendor maintenance windows, certificate rotations, network blips. AURI is built to absorb those without dragging the front desk into reconciliation work.
- Booking completes anyway. Guests book and pay through AURI in real time. The spa side does not need the PMS to be alive.
- Charge queues in the outbox. Folio posts hold in a per-property outbox with idempotency keys, ordered by service time.
- Queue flushes on recovery. First successful health-check drains the outbox in order, posts every line, reconciles. Zero manual replay.
How a new adapter gets shipped.
If your PMS or processor is not on the list, the build path is predictable. No bidding war, no quarterly committee — vendor name in, working adapter out, typically inside three weeks.
Custom adapters and middleware bridges available for hotel groups with proprietary stacks. Quoted per scope.
- 01
Scope · within a week
Share PMS vendor, version, and your property scale. We come back with a feasibility read, sandbox access needs, and a target window.
- 02
Build · two to three weeks
Adapter built against vendor sandbox. The five-operation surface lights up call by call; idempotency, audit log and outbox come for free.
- 03
Validate · joint sandbox
Walk through guest lookup, charge post and void with your test data. Recording for your IT team. Cutover to production on your timeline.
What IT directors usually ask.
Yes. Send the vendor name and your property type to the consultation form; we come back within the week with a feasibility read and a build window. Most cloud PMSes with a public API ship in two to three weeks.
Adapter code is complete, validated against the vendor's certification environment, and deployable today. It is a statement about the adapter's build state, not about how many hotels are running it. Early properties run on staged installations.
Bookings keep completing inside AURI. Each charge that would have posted is held in a per-property outbox with an idempotency key. The first successful health-check drains the outbox in order. The front desk sees no gap, no manual replay, no double-post.
Cards tokenize at the processor (Stripe in Europe, Tap in MENA). AURI never stores PAN data; the folio posts as a charge line, not a card record. Your PCI-DSS scope reduces to SAQ-A.
Reads: guest identity and folio target — only for guests who book the spa or whose folio receives a charge. Writes: spa charge lines to the folio, plus voids on the same lines. Reservation, rate plan, room inventory and OTA channel are never touched.
Yes — that is the consultation. We connect to your PMS sandbox (or the vendor's representative one if yours isn't ready), and walk guest lookup, charge post and void end to end. You keep the recording. No contract until you've seen it work.
See your PMS post a charge — before you sign anything.
Thirty-minute consultations walk through guest lookup, charge posting and the void path on a sandbox tied to your PMS. Founder-led, no SDR layer, no slide warm-up.
- Live sandbox against your PMS or a representative one
- Honest read on what the adapter does and does not do today
- Written proposal within three business days
30 minutes with Maciej
Founder, ex-banking principal engineer. The same person who wrote the adapter is the one who answers the questions.
No pressure to commit on the call. You get the proposal, you get the time.