Travel Agency Merchant Account: Own It or Use a Merchant of Record

For OTAs, superapps, and membership ecosystems that need to accept travel payments fast, without spending two months in high-risk underwriting.

A travel agency merchant account is the bank relationship that lets you collect card payments for the trips you sell and have that money settle into your account. It sounds like plumbing, and it is, but for anyone launching travel inside an existing platform, a travel agency merchant account is often the slowest, riskiest piece of the build. Travel is classified as high-risk by nearly every acquiring bank, which means opening a travel agency merchant account brings longer underwriting, rolling reserves, and real exposure to chargebacks and supplier failure. This guide explains what a travel agency merchant account means for a travel seller, why processors treat travel the way they do, and the real decision in front of you: get your own travel agency merchant account, or launch on a platform's Merchant of Record (MoR) and move to your own account once volume justifies it.

A merchant account is not the same thing as a payment gateway. The gateway (Stripe, Adyen, Braintree, and the like) is the software that captures the card. The merchant account is the underwritten bank relationship that lets an acquirer accept the risk of your transactions and settle the funds to you. To open one, an acquiring bank underwrites your business: it reviews your financials, projected volume, average ticket size, refund and cancellation policy, and, critically for travel, how far in advance you collect money before the customer travels.

That last point is what separates travel from most e-commerce. When someone buys a sweater, the card is charged and the product ships in days. When someone books a flight in March for an August trip, you are holding the customer's money for five months against a service you have not yet delivered. Acquirers call this future delivery risk, and it changes the whole underwriting conversation. You are not just processing a sale; you are holding a liability.

Three structural realities push travel into the high-risk bucket, and understanding them is the key to picking the right payment path:

Travel has one of the higher dispute rates of any category. Trips get cancelled, itineraries change, a hotel is not what the photos promised, or a customer simply does not recognize a supplier's name on their statement. Card networks watch dispute ratios closely: Visa places merchants that exceed roughly a 0.9% dispute-to-transaction ratio (with a minimum count of disputes) into its Visa Dispute Monitoring Program, which carries fines and remediation requirements (Visa). Mastercard runs a comparable Excessive Chargeback Program. For an acquirer, a travel merchant is a merchant more likely to trip those thresholds, so they price and reserve accordingly.

Because you collect long before you deliver, an acquirer's worst case is not a single refund; it is your business failing while holding a book of paid-but-not-yet-traveled bookings, leaving the acquirer to refund cardholders. The collapse of large travel sellers over the years, from airlines to tour operators, is exactly the scenario acquiring banks underwrite against. Their defense is the rolling reserve: they hold back a percentage of your settlements (commonly 5% to 10%) for months as a buffer, which ties up working capital you would rather deploy.

If you sell air, you inherit another layer. Airline content is settled through IATA's Billing and Settlement Plan (BSP), and accredited agencies carry financial guarantees and bonding against the tickets they issue (IATA). An acquirer underwriting an air seller knows a chargeback on a flown ticket, or a BSP default, is money the agency may already have remitted to the airline. That is high-risk by definition, and it is why generic payment providers so often decline or restrict travel merchants.

None of this makes a merchant account a bad idea. It makes it a slow, capital-intensive one, which is precisely the gap a Merchant of Record is built to close. If you want the broader picture of how travel money moves, our guide to travel agency payment processing covers the full stack.

Two paths: your own merchant account vs a platform MoR

There are two ways to accept travel payments, and the right one depends entirely on your stage:

Which one fits also depends on the rest of your stack. A team already comparing online travel agency software and a booking engine for travel agents will usually want payments to arrive in the same platform, not as a separate integration.

Path one: your own merchant account. You apply to a high-risk acquirer, pass underwriting, accept the reserve, and take on the compliance burden (PCI DSS scope, chargeback handling, refund logistics, tax) yourself. In exchange you own the relationship, keep the processing economics at scale, and control every downstream contract. Underwriting for a high-risk travel merchant is not instant. Where a low-risk retailer can be approved in a day, a travel seller commonly moves through documentation, review, and back-and-forth that stretches across several weeks before the account goes live, and reserves can persist well beyond that.

Path two: a Merchant of Record. With an MoR, a platform is the legal seller on record for the transaction. The MoR's merchant account processes the payment, the MoR absorbs the underwriting, holds the reserve, and carries the chargeback and compliance liability. You plug into the MoR's rails and start selling, often in days, because you are not the one being underwritten. This is the model that lets a superapp with millions of users switch on travel without a two-month payments project blocking the launch.

The trade-off is the classic build-versus-buy curve, and it shows up most clearly in time-to-live.

Approximate time to go live accepting card payments. High-risk travel underwriting and reserve setup stretch an own-account launch across weeks; an MoR removes underwriting because the platform is the party approved. Sources: card-network and acquirer underwriting norms; Xeni onboarding (2026).

The value of an MoR is not only speed; it is where the risk sits. When Xeni is the Merchant of Record, three burdens move off your balance sheet and onto the platform.

First, underwriting. You do not submit financials to a high-risk acquirer or wait out their review, because the platform's account is already live and already approved for travel. Your launch timeline stops depending on a bank's risk committee.

Second, liability and reserves. Chargeback exposure, the rolling reserve, and the future-delivery risk that acquirers price so heavily are carried by the MoR. That protects your working capital and means a spike in disputes during, say, a weather event does not put your own acquiring relationship into a monitoring program.

Third, compliance overhead. PCI DSS scope, payment-side fraud screening, and the operational machinery of refunds and dispute responses are handled at the platform layer. Xeni's built-in fraud protection screens transactions before they settle, which matters more in travel than almost anywhere else given the category's dispute profile.

An MoR also unlocks payment features that are hard to assemble alone:

For a membership ecosystem or superapp, those are conversion levers, not just convenience. This is also why an MoR pairs naturally with a white-label travel booking engine: the payment rails and the booking flow ship together instead of being stitched from separate vendors. If you are launching under your own brand, the same logic runs through a white-label travel portal, where checkout, inventory, and settlement are one product rather than three contracts.

An MoR is not a permanent ceiling, and the best platforms do not lock you into one. The economics are simple: at low and medium volume, the MoR's bundled rate beats the fixed cost and capital drag of running your own high-risk account. As monthly processing grows into the millions, the calculus flips. Owning the merchant account lets a high-volume seller negotiate interchange-plus pricing directly, capture the margin the MoR would otherwise keep, and go direct on supplier and BSP contracts.

The smart sequence, and the one Xeni is built around, runs in three steps:

A superapp like Rafeeq embeds travel this way to move quickly, with the option to shift payment economics in-house as its travel line matures. Teams evaluating the deeper build should read our guide to B2B travel portal development alongside this one.

Xeni is an API-first, white-label travel platform, and payments are a first-class part of it rather than a bolt-on. You can launch as Xeni's Merchant of Record and be live without your own high-risk underwriting, or bring your own payments and merchant account when you want to own the economics. Either way you get BNPL in the US and Canada, multi-currency acceptance, and built-in fraud protection tuned for travel's dispute profile, all under the same booking engine, multi-agency org management, and inventory of 1M+ hotels, 900+ airlines, cars, and activities (or your own negotiated contracts).

For an OTA, superapp, or membership ecosystem, that combination is the difference between a launch measured in days and one measured in quarters. See how the payment layer fits the wider stack on the Xeni B2B travel platform overview, and compare the Xeni plans when you are ready to price a launch.

Getting your own travel merchant account is the right long-term move for a high-volume seller, but it should not gate your launch. Xeni's flexible Merchant of Record lets you accept travel payments in days, with BNPL, multi-currency, and built-in fraud protection included, and hand you a clean path to your own merchant account when you scale.