Skip to main content
OnArrival

Embed travel booking inside your product.

Bring travel into the app your customers already use: a neobank, a property marketplace, an HR suite. White-label or co-branded, and you stay the brand of record.

At a glance

Who it’s for

Product teams at neobanks, marketplaces and HR suites who want travel in their app.

The problem today

Travel usually means a redirect, or a frame that looks and behaves like someone else’s product.

With OnArrival

Booking screens run inside your app, in your design system, with one backend behind every platform.

Next step: Design the embedded flow

Key facts

  • 6+ platforms from one backend
  • No iframes: components use your design tokens
  • WCAG 2.2 AA contrast and keyboard support

Terms in plain English

SDK
A code package your developers add to the app.
Iframe
A web page shown inside another page, with its own look and rules.
Headless
Use our APIs with screens you build yourself.
How it shows up

Native to the product. Owned by your brand.

01
Sandbox inventory
Show test inventory first. Use the integration phase for styling, checks and production readiness.
02
Web or native, one backend
React, React Native, Vue, web components, iOS and Android: six targets, one backend, one offer format.
03
Brand of record, headless if you need it
Take the full UI, or use just the APIs and build your own screens.
Implementation path

From sandbox to production.

Start with test inventory, then check styling, analytics, payments and after-booking support before going live.

  1. Install

    Add the SDK

    One package, one API key. Test inventory is live the moment you sign in.

  2. Theme

    Match your brand

    Your colours, fonts, corner radius and spacing apply to every component automatically.

  3. Compose

    Pick your products

    Flights, stays, experiences, insurance: show only what your app needs.

  4. Measure

    Stream the data

    Every search and booking event flows to your data warehouse from day one.

In your UI

Your checkout, your design system.

The flow your customers already trust, now booking a flight, a stay or a full bundle without leaving your app.

Match your design system

Set colour, type and spacing to fit your app, then test the full checkout and payment hand-offs.

Building blocks

Use the full flow, or just the pieces you need.

Accessible by default

Keyboard, screen-reader and WCAG 2.2 AA contrast built in.
Why no iframes

Your interface. A connected booking flow.

The travel components run inside your app, not in a frame from another site. Styling, navigation and keyboard focus stay consistent with the rest of your product.

Your design, not ours

Components build against your design system, so fonts and colours match exactly.

One focus order

Keyboard and screen-reader flow run through the whole page, not two competing loops.

No cookie breakage

Safari and cookie blockers don’t break checkout halfway, because booking state is not trapped in a cross-site frame.

Load only what you need

Each screen loads its own components. Speed depends on your modules, app, device and network.
Capabilities

What the travel SDK includes.

Embed

Works wherever your app runs.

  • React, React Native, Vue
  • Web components
  • iOS and Android
  • Server-driven UI

Theme

Looks like your product.

  • Design tokens
  • Light and dark
  • Locale and currency
  • Right-to-left support

Compose

Show only what you sell.

  • Any product
  • Bundle builder
  • Upsell slots
  • Headless mode

Operate

Run it with confidence.

  • Event webhooks
  • Warehouse sync
  • A/B test hooks
  • Versioned releases
Surfaces

Every step, on brand.

Search, offers, checkout and after-booking screens all take on your brand.

Search

Origin, dates, travellers. Your styling.

Offers

Fares and rooms with branded fare rules.

Checkout

Payment, traveller details, insurance.

Manage

Changes, refunds and disruption rebooks.
What teams ship

Fast, native, accessible.

Get started
Make travel feel native before production is in scope.
Related

Pairs well with

Most of our customers use two or three of these together.

Related reading

All field notes →
Product · 10 min

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.

Ankit SawantStrategy · 9 min

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.

Ankit Sawant