01
Perishable, high-value, dynamic
An airline seat has the highest perishability of any travel product and the value of a single PNR can range from £40 to £40,000. The payment system has to handle both ends cleanly.
Knowledge Base
Airline payment solutions.
A practical guide to airline payment solutions — what makes airline payment distinct, the IATA BSP and direct-distribution picture, ancillary and unbundled revenue handling, refund mechanics during irregular operations, chargeback patterns specific to airlines, and the multi-currency picture.
Distributiondirect and BSP supported
IROPSrefunds tracked per PNR
Multi-currencyready for global routes
Why airline payment is distinctive.
Airline payment carries shape that no other travel category quite shares. The merchandise is perishable (an empty seat at departure has zero value), the delivery window can be a year or more, ticket prices are highly dynamic, ancillaries account for a significant slice of revenue, and irregular operations can flip a healthy book into a refund queue within hours. The payment system has to handle all of that while sitting alongside the IATA Billing and Settlement Plan, distribution across multiple channels, and a chargeback profile that the card schemes monitor closely.
02
Multi-channel distribution
Direct (website, app, call centre), indirect (GDS through travel agents), OTAs, code-share partners and aggregators all feed into the same revenue picture. The payment trail has to stay honest across all of them.
03
Long tail of post-purchase events
Change fees, ancillary add-ons, upgrades, refunds, IROPS rebookings and post-flight ancillary spend all hit the booking after the initial sale. The system has to absorb each one against the right PNR.
Section 01
How IATA BSP and direct distribution fit together.
For most airlines, the payment picture splits into two big streams - direct distribution where the airline takes payment itself, and indirect distribution settled through IATA's Billing and Settlement Plan (BSP).
01
Direct distribution - airline takes the money
The airline website, app and call centre all take customer payment directly. Card, A2A and wallet rails apply the same as any e-commerce business, with the airline taking the merchant relationship and bearing the cost and risk.
02
BSP - IATA settles through travel agents
Tickets sold through travel agents settle through BSP - the agent collects from the customer, the BSP settles to the airline on a periodic cycle (usually monthly), and the agent's commission and credit card service charge are netted in the same flow.
03
Reconciling both into one revenue picture
Finance has to reconcile direct settlement and BSP settlement into one revenue picture per PNR. Doing this badly produces a finance team that does not actually know what each booking is worth.
Ancillary revenue and unbundling.
For most airlines, ancillary revenue - bags, seats, food, change fees, lounge access, fast-track, insurance - is a material slice of the business. Each ancillary attaches to a PNR but settles on its own rules, and the payment picture has to track the whole arc.
01
Add-ons at booking time
The initial booking can carry the base fare plus ancillaries selected at point of sale. The payment captures everything in one authorisation and the PNR record carries each line item. The discipline is that each ancillary attaches to the PNR, not as a separate floating transaction.
Capture At booking
Authorisation Single
PNR Itemised
02
Post-booking add-ons
Post-booking ancillaries arrive through the website, app or customer service and each one needs its own payment authorisation. Modern airline systems handle this through stored card tokens or new payment requests via payment link, with each ancillary attaching to the original PNR.
Channel Multi
Auth Per ancillary
Link To original PNR
03
Onboard and post-flight
Some airlines extend the payment surface beyond the flight itself - in-flight wifi, food, duty-free, post-flight ancillaries. These attach to the PNR through onboard systems or post-flight messaging and the booking-level evidence has to handle the late-arriving transactions cleanly.
Onboard Per PNR
Post-flight Captured
Late capture Reconciled
Section 03
How refunds work when irregular operations hit.
IROPS - irregular operations - are the airline-specific stress test for any payment system. A cancelled flight, a delayed route, a strike or a weather event can move thousands of refunds from theoretical to required within hours. The payment system has to handle the wave or the customer-service team takes the cost in chargebacks instead.
01
Refund by PNR, not by transaction
An IROPS refund applies to the affected PNR, not to a specific transaction. Where a PNR has multiple transactions (original ticket, ancillaries, post-booking upgrades), the refund has to handle all of them in the right proportion.
02
Voucher, credit, refund - customer choice
Many airlines offer customers a choice between a refund, a voucher or a credit for future travel. Each choice routes differently through the payment system and the booking record has to capture the customer's selection.
03
Speed is the chargeback prevention
Customers who get a refund within 48 hours of IROPS notification rarely chargeback. Customers who wait three weeks frequently do. Speed of resolution is the single biggest lever on the IROPS-related chargeback profile.
Chargeback patterns specific to airlines.
Airlines sit in a particular category for card-scheme chargeback monitoring. The combination of high values, long delivery windows and IROPS exposure puts airlines under particularly close scheme oversight.
01
Scheme monitoring is tight
The card schemes track airline-segment chargeback ratios closely because of the historical risk profile. Operators close to scheme thresholds face MDR increases, reserve hikes and sometimes scheme-mandated monitoring programmes. Staying comfortably below the thresholds is part of the operating discipline.
Visa VAMP threshold
Mastercard ExSP threshold
Target Below 0.5%
02
IROPS clusters become chargeback waves
When weather, strikes or technical issues cancel a wave of flights, the chargeback exposure is not the cancelled flights themselves - it is the customers who could not get a refund or rebooking quickly enough. The payment-system response speed determines the chargeback wave size.
Trigger IROPS event
Window 72 hours
Lever Refund speed
03
Representment leans on authentication
For airline disputes, the booking confirmation, ticket, traveller details, IROPS evidence and customer correspondence all matter - but the single most powerful piece of evidence is the 3DS authentication outcome. Routing transactions through authentication is the foundation, not an optional add-on.
3DS Foundation
Liability Shifted
Representment Defensible
Section 05
How multi-currency and FX fit airline payments.
International airlines sell in many currencies, settle in fewer and report in one. The currency picture has to capture rate context at every step to keep the revenue picture honest.
01
Sell in customer currency
Customers booking in their home currency convert better and pay less in cross-border interchange. Selling in the customer's currency is usually a revenue win.
02
Settle through the right MID
Different currencies settle through different MIDs and acquirer relationships. The reconciliation picture has to handle multi-MID economics per booking and per route.
03
DCC where it makes sense
Dynamic Currency Conversion at point of sale gives the customer the chance to pay in their home currency at the airline's rate. The economics work for some routes and not for others; the data picture has to evidence the decision.
04
Report in operating currency
Revenue reporting in the operating currency (usually GBP, USD or EUR) means each booking's FX context has to be captured at the moment of payment, not at the moment of reporting.
Section 06
PCI DSS for airline IT.
Airline IT stacks are large, complex and often span on-premise, cloud and partner-hosted components. PCI DSS scope grows quickly without active scope reduction.
01
Tokenisation across the stack
Replacing card data with tokens at every point in the stack - reservation system, customer service, mobile app, kiosks - keeps systems out of PCI scope and reduces operational risk.
02
Embedded and hosted payment journeys
An embedded checkout or hosted payment page lets the payment provider handle card capture, so the airline's web, app and customer-service systems stay outside PCI scope for those flows.
03
Network segmentation
For systems that genuinely need to hold card data, network segmentation keeps the rest of the estate out of scope. The segmentation has to be evidenced and tested.
04
PCI scope review per change
Every system change is a chance for PCI scope to creep. Building scope review into change management is the operational discipline that keeps the picture defensible at audit.
What airline payment handling looks like in felloh.
felloh treats airline payment as multi-channel, multi-currency and post-booking-event-heavy from the start. Each PNR, ancillary, refund and chargeback attaches to the booking-level ledger - so direct and indirect distribution share one picture rather than four.
01
One ledger across distribution
Direct website, BSP, GDS and OTA flows all sit against the PNR in one booking-level picture - so finance reads one source of truth across channels.
See booking-level visibility02
IROPS-ready refund handling
Refunds against affected PNRs run automatically with the booking-level evidence to defend representment if a chargeback follows.
See refund management for travel03
Multi-MID reconciliation
Different currencies and acquirer relationships reconcile into the same picture - per PNR, per route, per acquirer.
See multi-acquirer setupsSee this guide running on your booking data.
Bring the workflow or rail you want to improve and we will show how felloh keeps the booking-level evidence connected end to end.