Card rail
Authorise on a folio at check-in, capture at check-out for the balance the folio shows, void or refund — with the processor's risk verdict recorded before any card is held.
Embedded payments
Payments
The money, on the same bill as everything else.
Aerandil Payments takes the money inside the system that knows the stay. A card is held at check-in and captured at check-out for what the folio says; a deposit lands on the booking when it is paid; a no-show fee is assessed by the night audit and collected off-session; a refund or a chargeback is a recorded leg on the payment it concerns. Each property settles to its own merchant account, with the platform's fee taken at capture. Nothing is keyed twice and nothing is reconciled by hand.
Capabilities05 / 05
Card on file
The card number never reaches Aerandil: a processor-hosted field tokenises it, the token is held against the guest, and forgetting a card detaches it at the processor first.
Deposits and payment requests
Deposit policy as data; the booking's own account; a pay-by-link page the house sends and the rail mints, so a guest pays a deposit without the desk taking a card over the phone.
No-show and cancellation money
The night audit assesses the fee; the rail collects it off-session against the card the guest left, and an issuer's demand for the cardholder is recorded as a state, not written off.
Refunds and disputes
A refund is its own leg against the payment it reverses. A chargeback arrives on the webhook, lands on the payment it contests with its deadline, and its evidence is assembled from the stay.
Merchant accounts
Each property its own account at the processor, verified on the processor's hosted form; its card payments settle to it as the merchant of record, with the platform's fee taken at capture.
Charge to key
The room key as the folio's payment token: a guest taps their key at any outlet and the charge posts straight to their folio — one gesture, one staff confirmation, governed end to end.
Watchtower
The fraud network, coming with the rail: every hotel on Aerandil Payments contributes confirmed outcomes as one-way fingerprints, and every hotel's risk read asks the network before a card is held — no names, no cards, no records cross a tenant, and no hotel learns which other hotel saw a signal. Built when two operators share signals.
On the kernel
Explore the platform Every movement of money is a governed action on the folio — authorised, captured, refunded and disputed through the same contract as a room charge, with the processor's verdicts recorded as events.
Forge
The hospitality ontology, action engine, connectors, conformed metrics, and public contracts — HTTP, MCP, and generated SDKs — plus Explorer, the operator console.
Proxima
The dedicated cloud: your own single-tenant Forge cell — its own Postgres, region, and jurisdiction — with governed agents and open-weights models served inside the boundary.
Labs
AI products on the same public contracts as every partner — Forge Agents, the first-party runtime, and Talos, its flagship operations agent.
Talos
The flagship operations agent: a versioned definition, evals that gate release, and trust measured as conformed metrics.
Agent Studio
The authoring plane for Forge Agents: compose an agent's tool and data boundary from the live ontology, test it in a no-write sandbox, publish an immutable version.
Ithaca Early access
The PMS: purpose-built screens for arrivals, folios, night audit, housekeeping, and groups & events — running on the governed ontology.
Meridian Soon
The golden record: entity resolution that recognises the same guest, company, or property across every source system in the portfolio.
Forward deployed
Put Payments to work.
Aerandil is in private development. The next milestone is working with design partners who operate complex, multi-system hospitality businesses.
Design partner channel coming soon.