# OnArrival: full page summaries > OnArrival is a travel order platform: search, booking, servicing and settlement connected in one API across flights, hotels, buses, experiences, payments and protection. This file carries a one-paragraph summary of every public page. The shorter index lives at https://www.onarrival.com/llms.txt Operated by OnArrival Travel Technology Private Limited. Registered office: WeWork Salarpuria Symbiosis, Bannerghatta Road, Arekere, Bengaluru 560076, Karnataka, India. CIN U63030KA2022PTC158524, incorporated 2022. Investors include 8i Ventures, Antler, Good Capital and Ratio Ventures. ## Home https://www.onarrival.com/ The travel order platform. OnArrival keeps search, booking, servicing and settlement connected in one order history across flights, stays, ground transport, experiences and protection, so a trip remains one inspectable order rather than scattered supplier records. ## Platform https://www.onarrival.com/platform The platform overview walks the travel order lifecycle in five stages: intent (a structured trip request fanned out across connected supply), offer (different inventory normalised into a fair comparison), order (payment and supplier confirmations mapped to one durable order), service (schedule changes, cancellations, exchanges and refunds continuing on the same order), and settlement (customer payment, supplier settlement, refunds and fees reconciled against the same trip). ## Products https://www.onarrival.com/flights Integrate flight search, booking, bags, seats, changes and refunds across NDC, GDS and direct airline content with OnArrival. https://www.onarrival.com/hotels Search and book hotel rates from multiple suppliers with property and room mapping, clear rate conditions and booking management. https://www.onarrival.com/buses Buses: bus distribution infrastructure covering 2,800+ operators across 90+ countries, unified under one offer and booking API with seat-level inventory and live GPS tracking. https://www.onarrival.com/experiences Experiences: 90,000+ curated tours, tickets and transfers with live time-slot inventory, instant confirmation and mobile QR redemption, composable into any trip. https://www.onarrival.com/insurance Add travel insurance quotes and policy issuance to your booking flow. Review available cover, exclusions and claims handling for your markets. https://www.onarrival.com/payments Connect customer payments, supplier settlement and refunds to each booking, with currencies, virtual cards and transaction history in one integration. https://www.onarrival.com/bundles Combine flights, hotels and activities in one trip, with connected booking records, payments and recovery when only part of the trip confirms. ## Standalone data services https://www.onarrival.com/mapping Match hotel and room records across suppliers using shared identifiers, confidence scores and human review. Use mapping with your own booking system. https://www.onarrival.com/places Search hotels, cities and landmarks with autocomplete and location matching. Use the standalone places API with your existing booking system. https://www.onarrival.com/flight-status Receive flight schedule changes, delays, cancellations and airport updates through webhooks, including for flights booked outside OnArrival. ## Solutions https://www.onarrival.com/solutions/ai MCP for travel: OnArrival is a native MCP server, so AI agents can search, price, book and refund eligible flights, hotels, buses and experiences inside the guardrails you set, with typed tools and hard policy boundaries around side effects. https://www.onarrival.com/solutions/corporate Corporate travel: policy enforced at booking time, approvals routed through Slack, Teams or email, and cost-centre-tagged receipts that reconcile straight to your ERP. https://www.onarrival.com/solutions/embedded Embedded travel: ship a full travel stack of flights, stays, experiences and insurance inside your own product. White-label or co-branded, themed to your design system, with booking events streamed to your warehouse. https://www.onarrival.com/solutions/enterprises Enterprises: embed the full travel stack with policy-as-code, SSO/SCIM and one commercial contract covering every product. https://www.onarrival.com/solutions/fintech Fintechs and neobanks: add embedded travel rewards to a card program or neobank. Flights, hotels, forex and insurance through one SDK, without hiring travel-domain engineers. https://www.onarrival.com/solutions/loyalty Loyalty redemption: points-to-travel infrastructure that lets members spend points on eligible flights, hotels, buses and experiences at a redemption rate you control, with breakage and retention reporting. https://www.onarrival.com/solutions/suppliers Travel suppliers: reach modern channels such as fintech apps, super-apps, OTAs and AI agents through one connection. Push inventory once; OnArrival maps it to every partner schema and settles per booking. https://www.onarrival.com/solutions/travel-sellers Travel sellers: OTAs and agencies run search, book, ticket and refund through one modern platform and migrate off the legacy GDS and mid-office without losing supplier relationships. ## Developers and pricing https://www.onarrival.com/docs Explore OnArrival SDK examples, booking workflows, error handling and API documentation. Request sandbox access to test your integration. https://www.onarrival.com/pricing Pricing: usage-based, with no per-seat licensing, no per-transaction platform fee and no six-figure platform fees up front. Commercial terms are scoped to volume and product mix in the order form. ## Field Notes (blog) https://www.onarrival.com/blog Field Notes from the people building OnArrival: booking systems, hotel mapping, payments, refunds and the decisions behind them. https://www.onarrival.com/blog/a-price-used-to-be-data Dynamic airline pricing: when the cached fare is wrong: When an airline calculates an offer for each search, a cached fare may no longer explain the price. Booking systems need to retain the quote, its conditions and when it expires. https://www.onarrival.com/blog/build-vs-buy-travel-infrastructure Build vs. buy travel infrastructure: plan beyond launch: A search-and-book estimate leaves out supplier maintenance, booking changes, refunds and support. The build-versus-buy decision needs to include who runs those operations after launch. https://www.onarrival.com/blog/embedded-travel-for-fintechs Embedded travel for fintechs: connect booking to the rest of the app: A travel feature is more useful when it works with the customer identity, payment method and rewards already in the app. That connection also needs to survive a change or refund. https://www.onarrival.com/blog/agentic-travel-mcp-guardrails AI travel agents need booking permissions and spending limits: An AI agent can find a trip without having permission to buy it. Booking needs separate checks for the approved price, traveller, budget and any repeated request. https://www.onarrival.com/blog/ndc-gds-lcc-comparison NDC, GDS and LCC direct: choosing the right mix: The right mix depends on the routes, fares and servicing your customers need. Compare airline content sources without forcing each supplier workflow into your checkout. https://www.onarrival.com/blog/travel-api-architecture-control-plane Travel API architecture needs orders, state and recovery: 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. https://www.onarrival.com/blog/travel-order-lifecycle The travel order lifecycle: from search to refund settlement: A travel order records the offer, confirmation, booking changes and related payments. Keeping that history together makes partial cancellations and delayed refunds easier to handle. https://www.onarrival.com/blog/how-we-solved-room-mapping How we built our hotel and room mapping pipeline: Our mapping pipeline compares supplier records, checks room attributes and sends uncertain matches for review. The key is keeping the evidence behind each decision. https://www.onarrival.com/blog/unified-payments-refunds-reconciliation Travel payments: keep bookings, refunds and settlement connected: A successful payment does not mean every part of a trip is confirmed or settled. Track customer charges, supplier payments and refunds against the booking they belong to. https://www.onarrival.com/blog/hotel-mapping-deduplication Hotel mapping: why one property appears five times: Different suppliers can list the same hotel under different names. Hotel mapping joins those records while keeping room types, rate conditions and booking references distinct. https://www.onarrival.com/blog/post-booking-is-the-trust-product Post-booking service: who handles changes and refunds?: A confirmed booking still needs support when a flight changes, a traveller cancels or a refund is delayed. Customers need a clear status, a next step and someone responsible for the outcome. https://www.onarrival.com/blog/the-travel-cart-problem Why a travel cart needs more than one checkout call: Flights, 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. https://www.onarrival.com/blog/when-to-add-travel-as-a-product When should you add travel to your app?: Travel makes sense when it improves a job your customers already do in your app. Before launching, decide who owns booking changes, customer support and refunds. https://www.onarrival.com/blog/why-ndc-wont-solve-your-immediate-problems What NDC does not fix in your booking product: NDC can improve the airline offers you sell. Your product still needs to handle different carrier capabilities, booking changes, refunds and incomplete responses. https://www.onarrival.com/blog/one-core-five-hosts One travel SDK. Five platforms. The same booking rules.: We moved shared booking rules into a Kotlin Multiplatform core for web, iOS, Android, Flutter and React Native. Each host runs the same checks so prices, dates and decisions agree. https://www.onarrival.com/blog/stripe-analogy-breaks-after-checkout Why travel infrastructure has to work after checkout: The comparison with payment infrastructure is useful until a confirmed trip changes. Travel infrastructure also has to manage supplier updates, booking changes, refunds and settlement. https://www.onarrival.com/blog/ndc-capability-matrix The NDC capability matrix: what to check before integrating: An NDC label does not tell you which bookings a connection can service. Check shopping, booking, changes, refunds and disruption support for the markets you plan to sell. https://www.onarrival.com/blog/observability-stops-at-checkout What to monitor after a travel booking is confirmed: Search latency cannot tell you whether a flight changed or a refund arrived. Post-booking monitoring needs to detect supplier changes, missing updates and delays in telling the traveller. https://www.onarrival.com/blog/points-are-a-liability-not-a-currency Travel loyalty points: what redemption really costs: The cost of issuing points is only part of loyalty economics. Travel redemption also depends on supplier prices, the value promised to members and what happens when a booking is cancelled. ## Company and trust https://www.onarrival.com/company About OnArrival: the company builds booking infrastructure so banks, fintechs and consumer platforms can launch travel inside their own products. Incorporated 2022 in Bengaluru, India. https://www.onarrival.com/trust Trust: every security, privacy and reliability claim resolves to a control, an owner and evidence, with entry points into security, privacy, reliability and data-processing detail. https://www.onarrival.com/security Security: how OnArrival secures travel data across identity, infrastructure, software delivery and incident response. https://www.onarrival.com/status Status: an illustrative preview of how service health, supplier dependencies, incident history and notification channels will be presented. Sample data only; not connected to production monitoring. https://www.onarrival.com/privacy Privacy policy: data roles, collection, processing, retention, rights, transfers, security and contact information. https://www.onarrival.com/terms Terms and conditions: platform access, accounts, travel services, booking, pricing, payments and communication consent. https://www.onarrival.com/dpa Data Processing Addendum: roles, scope, sub-processors, cross-border transfers, data-subject rights and audit rights for traveller data. ## Getting started https://www.onarrival.com/demo Book a demo: walk through search, booking and settlement with an engineer. Bring your target markets, supplier mix and integration questions. https://www.onarrival.com/signup Request sandbox access: request OnArrival sandbox keys and MCP access. https://www.onarrival.com/atlas Atlas: a scroll-driven film through the OnArrival network, one traveller and one integration carrying all of it.