You can easily adapt to the evolving data requirements of various industries.

While the current focus is on airline-specific data, future expansions are planned for car rental, hospitality, and insurance.

Airline payments

Airline industry payments include additional data to be captured and passed through the payment Guide
An order is a customer’s request to purchase goods or services, progressing through various states based on payment status. lifecycle. This enriched data, including details such as passenger names, ticket numbers, and flight information, ensures the proper verification and categorization of transactions.

Merchants operating under airline-related MCCs 3000–3350 or travel agencies MCC 4722 may choose to provide these details. Supplying this enhanced data can help reduce fees, improve Guide
Fraud strategies and protocols for merchants to protect their businesses. fraud detection and Guide
Manage chargebacks effectively to minimize losses and protect your business. dispute handling, increase customer trust, and support industry compliance.

Airline data requirements

Airline-related information can be included in the Charge API request body under industry_data, where the type is airline with the following key data:

• airline - carrier codes, ticket types, passenger information, and flight dates
• ticket - unique ticket identifier, issue date, restriction status, and the address where the ticket was issued
• passenger - passenger’s first and last name, date of birth, phone number, and traveler type, along with an optional code for identifying the traveler
• flight_legs - details about each leg of the flight, such as flight number, carrier code, class of travel, departure and arrival airports, travel dates, and additional details like departure tax and stopover eligibility
  For each transaction, the flight legs data should be saved, and up to four legs can be included per transfer.

It is crucial that the data is validated according to industry standards. For example, airport codes must follow the IATA codes, and flight dates must be in the correct format.

To transfer this data, you must ensure that the connector supports these fields, which can currently only be checked through your account manager. Additionally, not all card brands may be supported by the connector.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53

{
  "industry_data": {
    "type": "airline",
    "airline": [
      {
        "airline_code": "PS",
        "airline_designator_code": "PS",
        "airline_name": "Ukraine International Airlines",
        "boarding_fee": "500",
        "computerized_reservation_system": "AMAD",
        "customer_reference_number": "A123456789",
        "document_type": "01",
        "flight_date": "2025-09-01 14:30",
        "agency_plan_name": "1B",
        "travel_agency_name": "AeroTravel",
        "travel_agency_code": "12345678",
        "agency_invoice_number": "INV12345",
        "ticket": {
          "number": "5661234567890",
          "issue_date": "2025-08-19",
          "restricted": false,
          "issue_address": {
            "line1": "12 Khreshchatyk St",
            "city": "Kyiv",
            "country": "UA",
            "postal": "01001"
          }
        },
        "passenger": {
         "first_name": "Ivan",
         "last_name": "Petrenko",
         "date_of_birth": "1985-03-21",
         "phone_number": "+380931234567",
         "traveller_type": "ADT",
         "code": "123"
        },
        "flight_legs": [
          {
            "flight_number": "PS101",
            "carrier_code": "PS",
            "class_of_travel": "Y",
            "departure_date": "2025-09-01 15:30",
            "departure_airport": "KBP",
            "departure_tax": "100",
            "arrival_airport": "JFK",
            "fare_base_code": "Y123",
            "stop_over_code": "X"
          }
        ]
      }
    ]
  }
}