Post-booking servicing API

Airline bookings, serviced where they were sold.

One API that lets OTAs and travel partners change, cancel, refund and rebook flights, using each airline's own rules.

Illustration: a cancelled flight is rebooked onto a later flight in the OTA's app, under the airline's waiver rules, without a call to the airline.

Paxstream at a glance

  • Airline rules applyPartners can only make the changes the airline allows.
  • Works next to your PSSYour booking flow and distribution setup stay as they are.
  • One integration per sideAn airline connects once for all its OTAs, and an OTA once for all its airlines.
  • Airline-side backgroundWe've worked on airline distribution, PSS and DCS systems, including at Lufthansa Systems and fastjet.

The problem

Why do OTA-booked passengers end up in the airline's phone queue?

Most OTAs and travel partners can sell an airline seat but can't change, cancel or refund it after the sale. When a storm closes an airport or a schedule changes, their passengers can't fix the booking where they bought it, so they call the airline while its contact centre and airport teams are at their busiest.

Booked direct

  1. Gets a rebooking offer in the airline app
  2. Picks a new flight in a few taps
  3. Is on the way again within minutes

Booked through an OTA

  1. The OTA can't change the ticket
  2. The passenger is told to call the airline
  3. Waits in a phone queue through no fault of their own

$100.4bn

in airline tickets were sold by US travel agencies, including OTAs, in 2025. Each of those bookings can need a change, cancellation or refund after the sale.

Source: ARC, reported by Travel Weekly

What Paxstream does

What is Paxstream?

Paxstream is a post-booking servicing API for airline distribution. The airline sets its servicing rules once. Every partner it authorises can then change, cancel, refund and rebook its own customers' bookings under those rules, the same way the airline's app does.

  • Re-accommodation

    Move disrupted passengers to another flight from the options the airline allows.

  • Changes

    Change the date, time or route, priced under the fare's change rules.

  • Cancellations

    Cancel a booking with the correct fee or waiver.

  • Refunds and credit

    Refund to the original payment or issue travel credit, whichever the airline allows.

  • Seats and bags

    Carry over or change ancillaries when the itinerary changes.

  • Airline rules on every request

    Paxstream checks each request against the airline's waivers, change windows and fees.

How it works

How does Paxstream work?

  1. 01

    The airline sets its rules

    It decides which changes are allowed, which waivers apply during a disruption, and whether refunds go back as money or credit.

  2. 02

    Partners connect once

    OTAs, travel agencies and aggregators use the same API calls for every connected airline.

  3. 03

    Passengers fix it where they booked

    When a flight is disrupted, the partner offers rebooking or a refund under the airline's rules, and the passenger doesn't have to call the airline.

Airlines

  • Airline A
  • Airline B
  • Airline C
Paxstream

Servicing layer

  • Airline rules
  • Rebook
  • Change
  • Cancel
  • Refund
  • Seats and bags

Travel partners

  • Travel agencies
  • OTAs
  • TMCs and aggregators
One integration to reach many OTAs. For each OTA, one integration to service many airlines.

Behind Paxstream

Why we're building this

We come from the airline side of distribution, where we've worked on the reservation and departure control systems and the data that runs through them. From there, the same thing happens every time a flight is cancelled. Passengers who booked direct rebook in the app. Passengers who booked through an OTA call the airline and wait.

We're building Paxstream so the OTA can sort out that booking itself, under the airline's rules. It's early. If your team deals with this, we'd like to show you what we've built and hear how you handle servicing today.

Product
Post-booking servicing and disruption API
For
Airlines, OTAs, travel agencies, TMCs and aggregators
Covers
Re-accommodation, changes, cancellations, refunds, seats and bags

FAQ

Frequently asked questions

What is post-booking servicing?

Post-booking servicing is the work done on a flight booking after it's paid for: date or route changes, cancellations, refunds, re-accommodation after a disruption, and seat or bag changes. Many OTAs can shop and book flights well but can't do this for the airlines they sell.

What does Paxstream do?

Paxstream is a servicing API that sits between airlines and the partners that sell their seats. It lets OTAs and other travel partners change, cancel, refund and rebook airline bookings under each airline's rules, so passengers can fix problems where they booked.

Who is Paxstream for?

Airlines that sell through OTAs and other B2B partners, especially low-cost and hybrid carriers, and the OTAs, travel agencies, TMCs and aggregators that sell their flights.

Does the airline stay in control?

Yes. The airline decides what's allowed: change windows, disruption waivers, fees, re-accommodation options, and whether refunds go back to the original payment or as travel credit. Paxstream applies those rules to every partner request.

Does Paxstream replace a PSS, booking engine or distribution connection?

No. Paxstream runs alongside the systems and connections you already have and doesn't change how flights are shopped or booked.

How do we get started?

Book a short call. We'll show you a live demo of what we've built and look at how servicing works for you today.

Post-booking servicing explained

Next step

See it working on a real disruption scenario

On a short call we'll show you a live demo and look at whether Paxstream fits your setup.