Live demo

For airlines and airline partners

Airline passenger service system integration for web and agent sales

Put a booking and servicing layer in front of your PSS: live availability, passenger reservations, PSS ticketing and supported changes, sold on your own website and B2B agent portal through airline APIs, NDC or GDS.

  • PNR and passenger records
  • PSS ticketing workflows
  • Airline API, NDC and GDS
  • B2C and B2B channels

What a PSS is

Reservations, inventory and departure control, connected to your sales channels

An airline passenger service system (PSS) is the set of airline systems behind every passenger journey: the reservation system that holds bookings and PNRs, the inventory that controls flights, booking classes and seats, and departure control for check-in and boarding. PHPTRAVELS is the digital booking and integration layer on top: passenger-facing and agent-facing booking flows that exchange reservation data with the PSS through the APIs it exposes.

  1. Confirm which PSS, airline API, NDC or GDS sources will be connected
  2. Define the reservation, ticketing and servicing functions in scope
  3. Map passenger, itinerary, fare and reservation fields between systems
  4. Test search, booking, ticketing and servicing scenarios in the sandbox
  5. Switch to production after provider testing and approval
Try the flights demoSee pricing
Connected source
Airline PSS API
Environment
Sandbox · certification
Sales channels
B2C website and B2B agent portal
Ticketing rule
Issue after payment
Servicing
Changes and cancellations

PSS ticketing

From search to ticket to servicing

The typical passenger ticketing flow, with each step handled by the connected airline or distribution source.

  1. Search

    Available flights and fares retrieved from the connected source.

  2. Reserve

    Traveller details collected and the booking record created.

  3. Pay and validate

    Payment taken and booking conditions validated.

  4. Ticket

    Ticket issued or confirmed through the airline or provider.

  5. Service

    Supported changes, cancellations and extra services managed.

Distribution

How a PSS reaches your booking channels

Airlines expose availability and booking through several interfaces. PHPTRAVELS connects to the ones your project uses.

  • Direct airline APIs

    Selected search, booking and servicing functions opened by the airline to approved applications.

  • NDC distribution

    Richer offers and order data exchanged with the airline through modern NDC interfaces.

  • GDS distribution

    Airline content delivered through global distribution systems to agencies and other sellers.

Flight suppliers you can connect:

  • Seeru
  • Amadeus
  • Duffel
  • Google Flights
  • Kayak
  • Kiwi
  • Mystifly
  • PKfare
  • Sabre
  • TBO Holidays
  • Travelport
See every flight integration

Back office

Run airline sales from one admin

The commercial side of the booking layer, managed by your team without touching the PSS itself.

  • Booking records

    Search passenger bookings by PNR, name, route or channel and see their current status.

  • Ticketing queue

    Bookings waiting for payment or ticketing, with the result returned by the source.

  • Fees and markups

    Service fees and markups per route, channel or agent group, as amounts or percentages.

  • B2B agents and wallets

    Agent accounts with their own commissions, credit and wallet balance.

  • Roles and access

    Separate permissions for sales, servicing, finance and administrators.

  • Reports

    Bookings, revenue and agent sales from every channel, ready to export.

Compare

Disconnected sales tools vs a connected booking layer

Without an integration layer, web, agent and call-centre sales each work around the PSS on their own.

AreaDisconnected toolsPHPTRAVELS
AvailabilityDisconnected toolsChecked by phone or copied between systemsPHPTRAVELSLive availability from the connected source in every search
ReservationsDisconnected toolsWeb, agent and phone bookings kept apartPHPTRAVELSOne booking flow that writes to the PSS record
TicketingDisconnected toolsIssued by staff after manual payment checksPHPTRAVELSIssued after payment where the source supports it
ServicingDisconnected toolsChanges and refunds handled by emailPHPTRAVELSSupported changes and cancellations from the booking record
AgentsDisconnected toolsFares requested by email or phonePHPTRAVELSB2B portal with agent markups, credit and wallet
ReportingDisconnected toolsTotals rebuilt from each channelPHPTRAVELSBookings from every channel in one report

Use cases

Who connects a PSS to PHPTRAVELS

  • Airlines

    A direct website and agent portal on top of the airline's own PSS and inventory.

  • Agencies and OTAs

    Airline content through APIs, NDC or GDS, without running a full PSS.

  • Technology teams

    A source-code booking front end to extend for a specific airline project.

Why PHPTRAVELS

A booking layer you own and can extend

  • Source code included

    Self-hosted under a commercial licence, so your developers can build each PSS connector.

  • Flight booking built in

    Search, fares, passengers, payment and tickets already in the flights module.

  • 24 languages

    Sell in your passengers' languages and currencies, including right-to-left.

  • B2C and B2B

    One installation for the public website and the agent portal.

FAQ

Airline passenger service system questions

What airlines and agencies ask before connecting a PSS to their booking channels.

Talk to sales

An airline passenger service system, or PSS, is a group of airline systems that support passenger operations. A traditional PSS includes a reservation system, an inventory system and a departure control system for check-in and boarding.

No. An airline reservation system manages bookings, passenger records and PNRs. It is one component of the wider PSS, which also covers inventory and departure control.

PSS ticketing links a confirmed reservation to the airline's ticketing process: validating the booking, issuing the ticket and handling permitted changes under the airline or provider's rules.

No. PHPTRAVELS is the booking and integration layer. Inventory control, departure control, check-in and boarding stay with the airline's PSS and DCS provider and are connected only where supported APIs exist.

Yes. Availability, booking and servicing data can be exchanged with GDS, NDC and direct airline APIs, depending on the provider's capabilities and your commercial agreements.

Usually not. A travel agency or OTA needs access to airline content and a flight booking website, not the airline's own passenger-service infrastructure, which is primarily airline technology.

Keep exploring

More from the platform