You want to ship a travel agent, not become a travel agency. The moment "selling flights and hotels" enters the picture, most developers brace for the part where they register as a regulated seller, chase airline accreditation, and stand up a finance team before a single booking clears. You don't.

Do you need a license to sell travel through RouteStack?

No. Building a travel API for your AI agent on RouteStack does not make you the licensed seller of travel.

RouteStack is the merchant of record on every booking, backed by Custom Travel Solutions' 30+ years of direct-supplier-API operating history. That one fact does the heavy lifting, because the three things developers dread never land on you:

• Travel-industry licensing and state seller-of-travel registrations — RouteStack carries the regulated merchant relationship, not you.
• Airline accreditation — not required to sell flights through RouteStack; that's handled upstream through CTS's direct supplier APIs.
• Your own Stripe merchant account — checkout is Stripe-powered and runs through RouteStack, so there's no merchant account to open and no card data touching your code.

What you do is build the agent and set your markup. Picture a road-trip agent that books a $1,200 trip, a flight, three hotel nights, and a rental car - in one MCP call. You set commission per vertical (flat, algorithm-suggested, or wholesale-plus-retail), keep 100% of what you mark up, and get paid weekly via ACH. At no point in that flow are you the licensed seller. You're the developer who built the agent and earn on every leg.

What is a merchant of record, and why does it remove the license requirement?

The merchant of record is the legal seller on the transaction — the entity the customer pays, the name tied to the payment relationship, and the party responsible for the regulatory obligations that come with selling travel. When RouteStack is the merchant of record, those obligations are RouteStack's.

You operate one layer up: you build the agent, choose your markup, and collect commission. That separation is exactly what lets a solo developer or a small team launch a revenue-generating travel agent without first becoming a regulated travel business.

How it works

Walk the booking flow and the reason you don't need a license becomes obvious — it comes down to who is selling the travel at the moment money changes hands:

1. Your agent searches. One MCP endpoint returns live, bookable inventory across flights, hotels, and cars — 950+ airlines, 3M+ hotel properties, and 20,000+ car models — direct from supplier APIs.
2. The user checks out. Your agent returns a Stripe-powered deep link. The user pays through that checkout — you don't build a payments stack, and no card data passes through your application.
3. RouteStack is the merchant of record. The seller-of-record relationship — licensing, state registrations, PCI scope, supplier contracts — belongs to RouteStack and CTS.
4. You get paid. Commission settles to you weekly via ACH, across all three verticals, kept 100%.

In code, the part you own collapses to a single call:

// Search across all three verticals, then book — one endpoint
const trip = await rs.search({ flights, hotels, cars });
const booking = await rs.book(trip.id);   // RouteStack = merchant of record
// booking.checkoutUrl → Stripe deep link the user pays through

No accreditation handshake, no merchant-account onboarding, no PCI questionnaire in that snippet, because none of it is yours to carry.

Common concerns

Do state seller-of-travel laws apply to me if I'm outside the US?

Those laws regulate the entity acting as the seller of travel. Since RouteStack is the merchant of record for every booking, that responsibility falls to RouteStack rather than your project. Jurisdictions differ, so if you're running a larger business, it's worth confirming your own situation — but the regulated selling relationship is one you're not stepping into by building on RouteStack.

Do I need a Stripe merchant account or to handle card data?

No. Checkout is Stripe-powered and runs through RouteStack, so there's no merchant account to open and no PCI scope landing on your code. You return a link; the payment is handled.

What about refunds and chargebacks?

Because the checkout and the merchant relationship run through RouteStack, the payment-side handling sits there too, not in an account you have to manage or reconcile.

The honest edge cases.

On an Enterprise plan with white-label checkout, your brand appears on the credit card statement and invoice — the merchant-of-record protection still applies, but the customer-facing name is yours. And if you genuinely want to operate as your own licensed seller of travel, you can still build that way. Most developers don't, which is why the merchant-of-record model exists.

Start building

You can have a bookable, multi-vertical trip running before you decide anything about licensing, because there's nothing to decide. Start free with 100 API credits and an unlimited sandbox, and connect in 12 lines.

Fork the roadtrip-bot starter to see a working agent book flights, hotels, and cars in a single MCP call, then set your markup and ship.

*This article is general information, not legal advice; licensing rules vary by jurisdiction, so confirm your own obligations before launch.