Airline Extension Overview
The Universal Airline API extends the Universal Fraud API shared transaction model with flight itinerary, segment, and passenger context.
Airline-specific information is supplied through the flightInformation structure while all core transaction data remains consistent with other Universal Fraud APIs.
Airline Extension Model
The Universal Airline API adds the following to the shared transaction structure:
- Flight Information
- Flight Segments
- Passenger Information
Note: See Airline Complete Request Structuremm for the full path.
Makes Airline Different
Air risk assessment often depends on data that is specific to airline transactions, such as:
- PNR / itinerary characteristics (ticket type, third‑party booking indicators)
- Segment-level context (route info, departure/arrival airports and timestamps, award ticket indicators)
- Passenger-level context (names, DOB, loyalty, passport where applicable)
These structures help the platform evaluate the event with the appropriate domain signals.
Hashing Requirements
The Air Fraud API follows the platform hashing rules. Fields designated as hash-required must be hashed before submission, including:
- giftCardNumber
- hashedPassword
See: Hashing RequirementsHashing Requirements (Constraint) and Accertify Hash AlgorithmAccertify Hash Algorithm (Reference).