Skip to main content
OnArrival

Collect payments, settle suppliers and track refunds.

Connect customer payments, supplier settlement and refunds to the same booking. Manage currencies, virtual cards and reconciliation without losing the history of each transaction.

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
Per market
payout rails — VCC, BSP/ARC, ACH/SEPA, wire
5+
ledger linked to each booking
1
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.

Collect customer payments and pay each supplier through its supported settlement method.

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.

Booking-level reconciliation
In depth

Where travel money actually goes.

A trip can involve several suppliers and currencies. Keep charges, payouts, refunds and disputes linked to the same booking.

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

Where a quote includes an FX lock, its rate and validity window are explicit. Show any revised quote before confirmation and keep the accepted FX terms with the booking.

FX
03

Chargebacks & disputes

Bring booking evidence, usage records and accepted cancellation terms together for a dispute. The payment provider and card-network process determine the outcome.

Protect
04

Reduce payment-data exposure

Tokenised payment capture keeps raw card data in the payment provider’s environment. Your PCI obligations depend on the integration; confirm the appropriate assessment with your acquirer or QSA.

Compliance
05

Liability & fund segregation

Agree on the merchant of record, fund flow, settlement schedule and dispute responsibilities for each market. Those roles are defined in your commercial agreement, rather than assumed from the API integration.

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

Payments API capabilities

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
  • Tokenised capture; confirm PCI scope
  • SOC 2 Type II report on file
  • Contracted payment responsibilities
  • PSD2 + SCA, AML + sanctions screening
  • GDPR + CCPA, DSAR tooling
The reconciliation tax

Your finance team should be able to follow a charge through supplier payment, cancellation and refund, using the same booking reference.

Capture currenciesPer market
Payout rails5+
Booking-linked ledger1
Who it's for

Who uses Payments?

OTA

Travel sellers

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

EXAMPLE WORKFLOWFollow a charge through settlement and refund.
Marketplace

Multi-supplier platforms

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

EXAMPLE WORKFLOWLink several supplier payouts to one trip.
Enterprise

Airlines & operators

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

EXAMPLE WORKFLOWReconcile bookings by distribution channel.
Questions

Payments: common questions

Something we haven’t covered? Talk to the team. We can help you work through your integration.

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?

The merchant of record is agreed for each market and payment flow. OnArrival is not the merchant of record in most jurisdictions. Confirm the available setup and each party’s tax, payment and dispute responsibilities before launch.

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?

Where an FX lock is offered, the quote shows the rate, spread and validity conditions. Your agreement sets the pricing, and the booking record retains the terms you accepted.

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

Build the rest of the trip.

Related reading

All field notes →
Technical · 12 min

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.

Manan VaghasiyaTechnical architecture · 11 min

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.

Manan VaghasiyaProduct engineering · 11 min

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.

Manan Vaghasiya
Start building
Try Payments with sandbox access.