Skip to main content
OnArrival

A travel-aware money layer.

Multi-currency capture, FX with rate-lock, virtual cards for supplier settlement, and a ledger that reconciles every leg of every booking. Built for the way travel actually moves money.

Illustration: a person launching a small paper boat carrying a single coin across a calm stream toward another figure waiting on the far bank.
capture currencies, automatic PSP failover
38
payout rails — VCC, BSP/ARC, ACH/SEPA, wire
5+
of bookings reconciled to the cent
100%
How it works

One charge, many settlements.

A $1,820 trip can become four supplier payouts in three currencies. Capture once; on confirmation, the ledger routes each settlement by VCC, BSP/ARC, ACH or SEPA. Amounts stay locked to the quoted FX rate and trace back from ancillary to leg, segment, booking and offer.

Read the reference
Inventory

Capture here, pay anywhere.

Travel money moves on rails most payment stacks have never heard of. We speak all of them.

CAPTURE

Multi-PSP in

Stripe, Adyen, Razorpay and regional PSPs behind one tokenised API, routed by cost and auth-rate with automatic failover.

38 capture currencies
SETTLE

Five payout rails

Single-use virtual cards, BSP/ARC, ACH/SEPA/local rails and scheduled wires, picked per supplier, reconciled per booking.

VCC · BSP · ACH · SEPA · wire
RECONCILE

One travel ledger

Every cent traced offer → booking → segment → leg → ancillary, with refund netting against future settlements.

100% reconciled, to the cent
In depth

Where travel money actually goes.

Travel is the hardest vertical in payments: one charge, many suppliers, many currencies, refunds that net against future settlements. We built for it specifically.

01

Virtual cards for suppliers

Single-use VCCs issued per booking for bedbank and operator settlement: amount-locked, merchant-locked, auto-reconciled against the booking they paid for.

Settle
02

FX, locked at quote

Travel margins die on FX slippage. The rate shown at quote is the rate the trip settles at. We carry the intraday risk, not you.

FX
03

Chargebacks & disputes

Travel-specific representment: booking evidence, usage proof and cancellation-policy acceptance compiled automatically per dispute.

Protect
04

PCI scope-out

Raw card data stays inside our PCI DSS Level 1 boundary, keeping your integration SAQ-A eligible. Our SOC 2 Type II report is renewed annually; the Security page carries the AOC, certification posture and residency map.

Compliance
05

Liability & fund segregation

Where you use OnArrival as merchant of record, card-network and chargeback liability shifts to us. Customer funds follow a safeguarding model: held in segregated client-money accounts, never commingled with our operating cash, reconciled per booking and released to suppliers and to you on a scheduled basis.

Compliance
LEDGER WATERFALL · RECONCILEDCustomer charge$1,820.00Offer · OA-9F3K$1,820.00Booking · carrier$1,540.00Segment · LIS-JFK$1,402.00Leg · ancillary$14.00SEAT 11A · PAID FORWARD TO CARRIERRECONCILED TO THE CENT0 UNATTRIBUTED · WHERE DID THE $14 GO? · HERE
Capabilities

The Payments surface

Capture
  • 38 currencies
  • Multi-PSP routing (Stripe, Adyen, Razorpay + regional)
  • 3DS + Strong Customer Auth
  • Tokenisation + vault
  • BNPL, wallet, UPI, PIX
Settle
  • Virtual cards for supplier pay
  • BSP / ARC / IATA flows
  • FX with quoted rate-lock
  • Multi-PSP failover
  • Refund netting against settle
Reconcile
  • Travel-aware ledger (offer → segment → leg)
  • Per-supplier statements
  • Chargeback representment
  • Dispute workflow
  • Auto-tax reporting
Compliance
  • PCI DSS Level 1 (you stay SAQ-A)
  • SOC 2 Type II report on file
  • MoR liability shift + segregated funds
  • PSD2 + SCA, AML + sanctions screening
  • GDPR + CCPA, DSAR tooling
The reconciliation tax

Every travel company eventually hires a team whose whole job is finding out where the money went. The ledger exists so you never do.

Capture currencies38
Payout rails5+
Bookings reconciled100%
Who it's for

Where Payments earns its keep.

OTA

Travel sellers

Capture once, settle everywhere. Supplier payments, FX and refund netting stop being engineering projects.

"Finance closes the month in a day, not a week."
Marketplace

Multi-supplier platforms

Split a single customer charge across any number of suppliers with locked FX and per-supplier statements.

"Four payouts, three currencies, one charge, automatically."
Enterprise

Airlines & operators

Accept distribution from hundreds of channels with settlement, netting and dispute handling already operationalised.

"Every channel settles the same way: ours."
Questions

Before you integrate Payments.

Something we haven’t covered? Talk to the team. A real engineer answers, never a bot.

Illustration: a traveller taps a card and one fine line fans into tidy settlement streams
Do I have to use your PSPs, or can I keep mine?

Keep yours. Plug existing Stripe or Adyen accounts into the routing layer, or capture on our merchant-of-record rails. Either way, settlement and the ledger work the same.

Who is the merchant of record?

Your choice per market. Act as MoR yourself with our routing underneath, or use OnArrival as MoR where you lack entities, useful for selling in currencies you can’t legally capture.

How does refund netting actually work?

Refunds offset against pending supplier settlements rather than triggering new money movement. The ledger nets positions per supplier per currency, cutting wire fees and FX double-conversion.

What does the FX rate-lock cost?

The locked rate includes a transparent, contracted spread you see on every quote. There is no slippage between the quote and settlement. Treasury-grade reporting shows exactly what you paid.

Can I pay suppliers that only take bank transfers?

Yes. Settlement supports VCC, BSP/ARC, ACH/SEPA/local rails and scheduled wires. The ledger reconciles them all back to the originating bookings.

Pairs well with

One product is rarely enough. Compose them.

Related reading

All field notes →
Technical · 12 min

Money has to inherit the shape of the trip

Checkout is the front door, not the building. One button creates collections, supplier settlements, FX snapshots, refunds and ledger entries, and they only stay coherent if every movement carries the order's own identifiers.

Manan VaghasiyaTechnical architecture · 11 min

The cart is the hardest problem in travel

A flight, a hotel and a transfer in one cart looks like ecommerce. It is actually a distributed transaction across suppliers that never agreed to coordinate, with inventory that expires while the customer types a card number.

Manan VaghasiyaProduct engineering · 11 min

Checkout is the midpoint: designing the travel order lifecycle

A booking is not a receipt. It is a living order that must survive rechecks, confirmations, schedule changes, cancellations and money moving on different clocks.

Manan Vaghasiya
Start building
Wire Payments into your stack with a sandbox key.