Find travel from many suppliers, book it, handle changes and refunds, and match every payment. Each trip lives in one order, from the first search to the final refund.
Every booking becomes an order: a single record that follows the trip through five steps.
Pick a step to see it in detail below
Pick a step. See what changes, what the traveller sees and what your team can do.
The payment, each supplier's confirmation and the traveller details join one order. Each supplier's own reference is kept underneath.
Whichever way you connect, the same four layers do the work. They share the same offer, order, traveller, event, servicing and payment records.
Highlighted: the layers used at the Book step
Use ready-made booking screens, build your own on our APIs, or let an AI agent book through MCP.
MCP (Model Context Protocol) is an open standard that lets AI agents use outside tools. Here, the tools are travel search and booking.
Drop a complete travel booking flow into your product, styled as yours.
Build your own screens. The same booking records and operations run underneath.
Let an AI agent search and book through travel tools with clear limits.
You decide the look, the rules, the order of results and who approves what. OnArrival handles the suppliers, changes, refunds and payment updates.
Start with one product, like flights. Add hotels later without rebuilding your rules or your booking updates.
Bundles, payments and MCP share the same order and event history as every bookable product.
Before you plan a launch, try price changes, supplier failures, cancellations and refunds on a real trip.
Pick a real trip and agree who owns each part.
Connect one way in (screens, APIs or MCP) to the shared offers and orders.
Try price changes, supplier failures and changes to the booking.
Write down what launch needs, who owns it and the rollout steps.
Supplier adapters handle API calls. A travel platform also needs a shared booking record, permission checks and recovery when a supplier response is late or unclear.
Pawan Shetty→Product engineering · 11 minA travel order records the offer, confirmation, booking changes and related payments. Keeping that history together makes partial cancellations and delayed refunds easier to handle.
Manan Vaghasiya→Technical architecture · 11 minFlights, hotels and activities can expire or fail independently during checkout. A travel cart needs price checks, booking recovery and a payment plan for partial success.
Manan Vaghasiya→