--- title: Legacy Airline API Overview slug: legacy-fraud-apis/legacy-airline-api-overview createdAt: 2026-03-10T12:35:18.974Z --- ::::ExpandableHeading ### **Topic type: Concept** :::hint{type="warning"} **Purpose**: Legacy Airline Fraud API overview, differences, and hashing requirements. **Audience**: API integrators and client developers. **Applies to**: Legacy Airline clients implementing via API. **Does not apply to**: Universal APIs, any other industry, or airline clients who opt for a non-API integration. ::: :::: :::hint{type="info"} ******Legacy API Notice**: This API is part of the Legacy Fraud API framework and is maintained for compatibility with existing implementations. New integrations should use the **Universal Fraud APIs** instead. The Universal Fraud APIs provide: - A shared core transaction model - Consistent request and response contracts - Industry-specific extensions - Unified documentation and onboarding - Ongoing feature investment Use this Legacy API documentation only if: - You are maintaining an existing Legacy Fraud API integration. - You have not yet completed migration to Universal Fraud APIs. - Accertify has specifically directed your implementation to remain on the Legacy API framework. For new implementations, start with **Universal Fraud APIs Overview**. ::: The Air Fraud API is designed for transactions where **flight itinerary context** materially affects fraud evaluation. In addition to the shared core fields (transaction, account, payment, device, addresses, and so forth), Air adds structures for **PNR/itinerary, segments, and passengers**. ## What 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 Requirements](docId\:yuGHwVL8eOn7vCgSwPcd3)** (Constraint) and **[Accertify Hash Algorithm](docId\:rKIK1Lb6EUUWsz3sxPCe-)** (Reference). ## Field Reference ::::LinkArray{contentSource="CUSTOM"} :::LinkArrayItem{headerType="IMAGE" headerImage="https://api.archbee.com/api/optimize/C_ua77kdJRrVi_Gd-0NCF/I1-du8EBa2R9r9DXRoqZ1-20260326-200545.png"} [US Airline Fields](docId\:mWidAxBRrJSPXvU16qrAZ) ::: ::::