# Travel Payments API: Settlement and Refunds | OnArrival > Connect customer payments, supplier settlement and refunds to each booking, with currencies, virtual cards and transaction history in one integration. Source: https://www.onarrival.com/payments --- # Collect payments, settle suppliers and track refunds. Customer payments, supplier payouts and refunds, all tied to the same booking. Currencies, virtual cards and reconciliation stay traceable, so finance never has to guess where the money went. [Request a key](https://www.onarrival.com/signup) [Read the docs](https://docs.onarrival.com/) payment currencies, automatic provider failover Per market payout rails — VCC, BSP/ARC, ACH/SEPA, wire 5+ ledger linked to each booking 1 In short ## Payments, in four steps. The traveller pays once. Behind that payment, several suppliers get paid in their own way, and every amount traces back to the booking. 1. Collect The traveller pays once, at checkout. 2. Split The ledger splits that payment across every supplier in the trip. 3. Pay out Each supplier is paid its way: virtual card, airline settlement, bank transfer or wire. 4. Reconcile Refunds, disputes and payouts trace back to the same booking. How it works ## One charge, many settlements. A $1,820 trip can become four supplier payouts in three currencies. Collect once. When the booking confirms, the ledger pays each supplier by virtual card, airline settlement (BSP/ARC), ACH or SEPA. Amounts stay locked to the quoted exchange rate, and each one traces back through its leg and segment to the booking and offer. [Read the reference](https://docs.onarrival.com/) One charge, many settlements Customer charge $1,820 1 booking · USD Carrier BSP · settles GBP £742 ≈ $940 Bedbank Virtual card · settles EUR €572 ≈ $620 Activity ACH · settles USD $180 Insurer Internal book · settles USD $80 Reconciled$1,820 · 0 unattributed Inventory ## Capture here, pay anywhere. Collect customer payments, then pay each supplier through the method it supports. CAPTURE ### Many payment providers in Stripe, Adyen, Razorpay and regional payment providers (PSPs) behind one tokenised API. Payments route by cost and approval rate, with automatic failover. 38 capture currencies SETTLE ### Five payout rails Single-use virtual cards, airline industry settlement (BSP/ARC), bank transfers (ACH, SEPA and local rails) and scheduled wires. Chosen per supplier, reconciled per booking. VCC · BSP · ACH · SEPA · wire RECONCILE ### One travel ledger Every cent traced from offer to booking, segment, leg and extra. Refunds are netted against future supplier payments. 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 A single-use virtual card (VCC) is issued per booking to pay bedbanks and operators. Each card is locked to one amount and one merchant, and reconciled automatically against its booking. Settle 02 ### Exchange rate, locked at quote Where a quote includes a locked exchange rate (FX lock), the rate and how long it holds are explicit. Show any revised quote before confirmation, and keep the accepted terms with the booking. FX 03 ### Chargebacks & disputes When a customer disputes a charge, bring booking evidence, usage records and the accepted cancellation terms together. The payment provider and card network process decide the outcome. Protect 04 ### Reduce payment-data exposure Tokenised payment capture keeps raw card data with the payment provider. Your PCI obligations (the card industry’s security rules) depend on the integration; confirm the right assessment with your acquirer or QSA. Compliance 05 ### Liability & fund segregation For each market, choose the merchant of record (the business legally selling to the customer): your business, or OnArrival where that setup is offered. Then agree the fund flow, the settlement schedule and dispute responsibilities. Your commercial agreement defines those roles; they are not assumed from the API integration. Compliance @media (prefers-reduced-motion: no-preference){ .pdp-link{stroke-dasharray:60; stroke-dashoffset:60;} .oa-illo-in .pdp-link{animation:pdpDraw .55s ease-out forwards;} .pdp-node{opacity:0;} .oa-illo-in .pdp-node{animation:pdpRise .5s ease-out forwards;} .oa-illo-in .pdp-leaf-glow{transform-box:fill-box; transform-origin:center; animation:pdpGlow 1.25s 1.8s ease-in-out 2;} .pdp-stamp{opacity:0;} .oa-illo-in .pdp-stamp{transform-box:fill-box; transform-origin:center; animation:pdpStamp .55s 1.7s cubic-bezier(.2,1.5,.4,1) forwards;} } @keyframes pdpDraw{to{stroke-dashoffset:0}} /* opacity-only: pdp-node / pdp-stamp are positioned by transform attrs. */ @keyframes pdpRise{from{opacity:0} to{opacity:1}} @keyframes pdpStamp{from{opacity:0} to{opacity:1}} @keyframes pdpGlow{0%,100%{opacity:.35}50%{opacity:.85}} 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 payouts 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 Collect once, pay every supplier. Supplier payments, exchange rates and refund netting stop being engineering projects. EXAMPLE WORKFLOWFollow a charge through settlement and refund. Marketplace ### Multi-supplier platforms Split one customer payment across any number of suppliers, with locked exchange rates and a statement for each supplier. EXAMPLE WORKFLOWLink several supplier payouts to one trip. Enterprise ### Airlines & operators Accept bookings from hundreds of sales channels, with settlement, netting and dispute handling already running. EXAMPLE WORKFLOWReconcile bookings by distribution channel. Questions ## Payments: common questions Something we haven’t covered? [Talk to the team](https://www.onarrival.com/company#contact). We can help you work through your integration. **Do I have to use your payment providers, or can I keep mine?** Keep yours. Connect existing Stripe or Adyen accounts to the routing layer, or collect through OnArrival as merchant of record in markets where that setup is offered. Either way, settlement and the ledger work the same. **Who is the merchant of record?** Your business or OnArrival. As a platform, we support both setups: you can be the merchant of record (the business legally selling to the traveller) and use our payment rails, or OnArrival can act as merchant of record in markets where that setup is offered. Your agreement sets which applies to each market and payment flow, along with each party’s tax, payment and dispute responsibilities. **How does refund netting actually work?** Refunds are offset against pending supplier payments instead of moving new money. The ledger nets balances per supplier and per currency, which cuts wire fees and double currency 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 keeps the terms you accepted. **Can I pay suppliers that only take bank transfers?** Yes. Settlement supports virtual cards, BSP/ARC, ACH/SEPA/local rails and scheduled wires. The ledger reconciles them all back to the original bookings. Pairs well with ## Build the rest of the trip. [Product Flights Search, book and manage flights through one API.](https://www.onarrival.com/flights) [Product Hotels Hotel booking with property and room mapping built in.](https://www.onarrival.com/hotels) [Product Bundles Book flights, hotels and activities as one trip.](https://www.onarrival.com/bundles) ## Related reading [All field notes →](https://www.onarrival.com/blog) [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 Vaghasiya**](https://www.onarrival.com/blog/unified-payments-refunds-reconciliation) [Technical 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 Vaghasiya**](https://www.onarrival.com/blog/the-travel-cart-problem) [Product 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**](https://www.onarrival.com/blog/travel-order-lifecycle) Start building Try Payments with sandbox access. [Request a key](https://www.onarrival.com/signup) [Read the docs](https://docs.onarrival.com/)