Rihuum AI Hospitality Intelligence Suite
A controlled hospitality core from reservation to accountable settlement.
RAHIS v8.2 connects protected SaaS administration, room and stay operations, folios, finance, procurement, stock and provider-readiness controls.
Paystack is configured for sandbox commissioning only. No live payment provider, OTA or property hardware connection is represented as active.
Readiness record →- Release
- RAHIS v8.2
- Access
- Authorised workspace
- Payments
- Paystack sandbox only
- Live providers
- Inactive
01 / Release evidence
Implemented operational records with explicit limits.
Internal workflow, external provider evidence and live settlement are separate states. A recorded payment attempt is never treated as proof of a bank settlement.
- Tenant and property administration
- Membership, plan, entitlement, seat and period-based usage records inside the protected workspace.
- Reservations and stays
- Server-priced reservations, guarded inventory, physical rooms, assignment, check-in, folios and zero-balance checkout.
- Finance
- Chart-of-account masters and append-only balanced journals with independently confirmed payment evidence.
- Procurement and stock
- Supplier and stock masters, controlled purchase orders, goods receipt, supplier bills and payments.
- Provider configuration
- Encrypted immutable configuration revisions, credential rotation and maker-checker approval.
- Paystack commissioning
- Test-mode hosted checkout, signed webhook handling and server-side transaction verification bound to a RAHIS folio.
02 / Product architecture
Module families governed as one hospitality system.
The catalogue describes the wider architecture. The v8.2 release evidence above—not the number of named modules—defines current implementation.
| 01 | Central Reservation SystemMulti-property CRS · Room and rate master · Daily availability and restrictions · Reservation lifecycle · Groups, corporate and travel-agent business · Guest profiles and loyalty · Direct booking engine · Channel mapping and reconciliation |
|---|---|
| 02 | Hospitality operationsFront office and PMS · Housekeeping and laundry · F&B POS and kitchen operations · Events, venues and banqueting · Guest service and concierge · Facilities and maintenance · Security, incidents and lost property · Revenue and experience intelligence |
| 03 | Hospitality ERPChart of accounts and general ledger · Accounts receivable and payable · Cash, bank and settlement reconciliation · Budgets, departments and cost centres · Procurement and supplier management · Stores, recipes, stock and cost control · Fixed assets and maintenance · HR, roster, attendance and payroll inputs |
| 04 | RAHIS SaaS controlTenant and property provisioning · Plans, trials and subscriptions · Feature entitlements and limits · Licensing and activation · Usage metering and quotas · Customer administration and support · Audit, export and offboarding · Versioned upgrades and migrations |
| 05 | Integration and intelligenceOTA and channel-manager adapters · Payment and settlement adapters · Property hardware bridge · Messaging and guest communications · Accounting and tax adapters · Analytics and business intelligence · Governed RIA insight and exception detection · Health, retry, reconciliation and incidents |
03 / Provider readiness
Configuration records are not live connections.
Provider records, mappings and credentials are controlled server-side. Only Paystack has a sandbox transaction adapter in this release; every production connection requires commissioning.
| Code | Provider | Category | Current boundary |
|---|---|---|---|
| booking-connectivity | Booking.com Connectivityroom rate mapping · availability rates restrictions · reservations · modifications | ota | Requires Booking.com connectivity-partner onboarding, property permission and provider certification. |
| expedia-connectivity | Expedia Group Connectivityroom rate mapping · availability rates restrictions · reservations · modifications | ota | Requires Expedia Group lodging connectivity onboarding, certification and production credentials. |
| agoda-connectivity | Agoda Connectivityroom rate mapping · availability rates restrictions · reservations · modifications | ota | Requires Agoda connectivity approval, property identifiers, test access and certification. |
| airbnb-software-partner | Airbnb Software Partnerlisting mapping · availability · rates · reservations | ota | Available only through Airbnb-approved software-partner access and applicable host/property permissions. |
| approved-channel-manager | Approved Channel Managerroom rate mapping · availability rates restrictions · reservations · modifications | ota | The selected channel manager must be added to the server-side endpoint allowlist before testing. |
| paystack | Paystackhosted checkout · transaction verification · signed webhooks · refunds | payment | Use server-side transaction initialisation and verification. RAHIS never stores card number, CVV, PIN or OTP. |
| flutterwave | Flutterwavehosted checkout · transaction verification · signed webhooks · refunds | payment | Requires merchant onboarding, API-version selection and verified webhook signatures. |
| squad | Squadhosted checkout · transaction verification · signed webhooks · refunds | payment | Requires an approved Squad merchant account, current integration specification and production credentials. |
| interswitch | Interswitchhosted checkout · transaction verification · signed webhooks · refunds | payment | Requires merchant onboarding and the approved Interswitch product/API profile. |
| zkteco-bridge | ZKTeco Property Bridgeattendance events · access events · device health · offline buffering | hardware | Private-LAN terminals require an outbound property bridge. A public cloud service cannot safely dial a hotel private IP. |
| property-device-bridge | RAHIS Property Device Bridgedoor locks · pos kds · receipt printers · smart room | hardware | Each supported device model and firmware requires an approved local adapter, outbound TLS and an operational fallback. |
| whatsapp-cloud | WhatsApp Business Platformapproved templates · guest messages · delivery events | messaging | Requires Meta business verification, approved templates and customer messaging consent. |
| smtp-provider | Transactional Email Providerbooking confirmations · invoices · service notices | messaging | Use a dedicated transactional mail account with SPF, DKIM and DMARC alignment. |
| google-maps | Google Maps Platformplaces · maps · geocoding | analytics | Restrict API keys by application, domain, API and quota before production use. |
| approved-accounting-api | Approved Accounting APIchart mapping · journals · settlement reconciliation | accounting | Requires a reviewed accounting mapping, fiscal controls and endpoint allowlisting. |
04 / Sandbox transaction integrity
A webhook starts verification; it does not finish it.
The commissioning path is deliberately bound to the exact RAHIS folio and expected value before any evidence can be recorded.
- Create
Create an idempotent attempt against the exact folio, amount and currency.
- Redirect
Use Paystack-hosted test checkout; never expose the server credential to the browser.
- Receive
Validate the signed webhook and reject duplicate or malformed events.
- Verify
Query the provider server-to-server and compare reference, amount, currency and status.
- Post
Record verified evidence; operational staff still control reconciliation and exception handling.
Release boundary
Operational depth without false activation claims.
Each hotel or group still requires tenant setup, data preparation, acceptance and provider commissioning.
- Live Paystack remains inactive until merchant activation and production acceptance.
- Other provider records do not make OTA, hardware, accounting or messaging integrations live.
- Tenant-facing self-service, automatic metering and subscription collection remain future releases.
- Operational acceptance and reconciliation remain accountable human responsibilities.
RAHIS access
Evaluate the current core against a real property workflow.
Discovery confirms property scope, operational data, roles, integrations, migration and acceptance before implementation.