Authorisation with airline data

When you send an authorisation request with a batch file submission, you can include airline data information.

To do so, you append the relevant airline data as sub-lines to the card payment, IBAN payment or recurring payment authorisation requests.

Below you can find an overview of the airline data sub-lines you can pass with the batch file requests.

Airline data sub-lines

Below you can find an overview of the airline data sub-lines you can pass with the batch file requests.

Airline

This sub-line holds information about airline data information you want to send along with batch file authorisation and capture requests.

Airline data fields may have specific format and/or character limitations: refer to the airline data overview for details.

Field #

Format

Required

Description

1

Fixed value: SL

(tick)

Record type identifier

2

Numeric [0-9]+

(tick)

SL sub-line record number reference within its parent line.

The counter starts at 1, and it increments sequentially by one unit.

3 Fixed value: Airline

(tick)

Transaction type.
Defines the required field types for the specific sub-line.

4

Alphabetic data [A-Z, a-z]

(error)

Customer reference identifier/number.

5

Alphabetic data [A-Z, a-z]

(error)

Airline code.
6
Alphabetic data [A-Z, a-z]
(error) Airline designator code.
7
Alphabetic data [A-Z, a-z]
(error) Ticket issue address.
8
Alphabetic data [A-Z, a-z]
(error) Ticket number.
9
Alphabetic data [A-Z, a-z]
(error) Travel agency code.
10
Alphabetic data [A-Z, a-z]
(error) Travel agency name.
11
Alphabetic data [A-Z, a-z]
(error) Agency plan name.
12
Alphabetic data [A-Z, a-z]
(error) Agency invoice number.

Example of isolated airline data batch file sub-line:

SL,3,Airline,BVQT04,KLM,DSG123,5th avenue 66,100020003034,12345678,,,,

Example of airline data batch file sub-line in a batch file context:

FH,1.0,DEVL,Company,TestCompany,Default,27,ws@Company.TestCompany,Modification,FileHeaderEchoData
BH,1,BlockHeaderEchoData
L,1,MerchantAccount,TestMerchant,CaptureWithExternalAuth,Test Product
3,123456
SL,1,PaymentDetails,10000,2,EUR
SL,2,Card,4111111111111111,6,2016,737,CardHolderName,,,
SL,3,Airline,BVQT04,074,KL,C1,ABCDEF123456,A1B2C3D4,Adyen-Air,AP,123456
SL,4,AirlineLeg,1,AMS,FL123,AA,1,B,A,LND,2025-01-01 10:00,,
SL,5,AirlinePassenger,1,Name,Miguel,Rodriguez,,,
SL,8,ShopperInteraction,Ecommerce
BT,1
FT,1

AirlineLeg

This sub-line holds information about airline leg information you want to send along with batch file authorisation and capture requests.

If you include airline data in your request, the batch file needs to contain at least one airline leg sub-line as well.

Airline data fields may have specific format and/or character limitations: refer to the airline data overview for details.

Field #

Format

Required

Description

1

Fixed value: SL

(tick)

Record type identifier

2

Numeric [0-9]+

(tick)

SL sub-line record number reference within its parent line.

The counter starts at 1, and it increments sequentially by one unit.

3 Fixed value: AirlineLeg

(tick)

Transaction type.
Defines the required field types for the specific sub-line.

4

Numeric [0-9]+
(tick)
Leg number identifier.
The counter starts at 1, and it increments sequentially by one unit.
5
Alphabetic data [A-Z, a-z]
(tick) Departure airport.
6
Alphabetic data [A-Z, a-z]
(tick) Flight number.
7
Alphabetic data [A-Z, a-z]
(tick) Carrier code.
8
Alphabetic data [A-Z, a-z]
(tick) Fare basis code.
9
Alphabetic data [A-Z, a-z]
(tick) Travel class identifier.
10
Alphabetic data [A-Z, a-z]
(error) Stopover code.
11
Alphabetic data [A-Z, a-z]
(tick) Destination code.
12
Alphabetic data [A-Z, a-z]
(tick) Travel date.
13
Alphabetic data [A-Z, a-z]
(error) Departure tax.

Example of isolated airline leg data batch file sub-line:

SL,4,AirlineLeg,1,AMS,12345,AA,Y123456,B,O,LON,2014-08-02T19:05:00.000,Y

Example of airline leg data batch file sub-line in a batch file context:

FH,1.0,DEVL,Company,TestCompany,Default,27,ws@Company.TestCompany,Modification,FileHeaderEchoData
BH,1,BlockHeaderEchoData
L,1,MerchantAccount,TestMerchant,CaptureWithExternalAuth,Test Product
3,123456
SL,1,PaymentDetails,10000,2,EUR
SL,2,Card,4111111111111111,6,2016,737,CardHolderName,,,
SL,3,Airline,BVQT04,074,KL,C1,ABCDEF123456,A1B2C3D4,Adyen-Air,AP,123456
SL,4,AirlineLeg,1,AMS,FL123,AA,1,B,A,LND,2025-01-01 10:00,,
SL,5,AirlinePassenger,1,Name,Miguel,Rodriguez,,,
SL,8,ShopperInteraction,Ecommerce
BT,1
FT,1

AirlinePassenger

This sub-line holds information about airline passenger information you want to send along with batch file authorisation and capture requests.

If you include airline data in your request, besides at least one airline leg sub-line the batch file needs to contain at least one airline passenger sub-line as well.

Airline data fields may have specific format and/or character limitations: refer to the airline data overview for details.

Field #

Format

Required

Description

1

Fixed value: SL

(tick)

Record type identifier

2

Numeric [0-9]+

(tick)

SL sub-line record number reference within its parent line.

The counter starts at 1, and it increments sequentially by one unit.

3 Fixed value: AirlinePassenger

(tick)

Transaction type.
Defines the required field types for the specific sub-line.

4

Numeric [0-9]+
(tick)
Passenger number identifier.
The counter starts at 1, and it increments sequentially by one unit.
5 Fixed value: Name (tick) Passenger data type.
6
Alphabetic data [A-Z, a-z]
(tick) Passenger's first/given name.
7
Alphabetic data [A-Z, a-z]
(tick) Passenger's last/family name.
8
Alphabetic data [A-Z, a-z]
(error)

Passenger's birth date.

  • Format: yyyy-MM-dd
    For example: 1980-02-28

9
Alphabetic data [A-Z, a-z]
(error) Traveller type.
Passenger type code (PTC).

Example of isolated airline passenger data batch file sub-line:

SL,1,PaymentDetails,100,2,EUR,,,,,
SL,2,Card,4111111111111111,6,2016,737,CardHolderName,,,
SL,3,Airline,BVQT04,KLM,DSG123,5th avenue 66,100020003034,12345678,,,
SL,4,AirlineLeg,1,AMS,12345,AA,Y123456,B,O,LON,2014-08-02T19:05:00.000,Y
SL,5,AirlinePassenger,1,Name,John,Doe,1979-02-28,,

Example of airline passenger data batch file sub-line in a batch file context:

FH,1.0,DEVL,Company,TestCompany,Default,27,ws@Company.TestCompany,Modification,FileHeaderEchoData
BH,1,BlockHeaderEchoData
L,1,MerchantAccount,TestMerchant,CaptureWithExternalAuth,Test Product
3,123456
SL,1,PaymentDetails,10000,2,EUR
SL,2,Card,4111111111111111,6,2016,737,CardHolderName,,,
SL,3,Airline,BVQT04,074,KL,C1,ABCDEF123456,A1B2C3D4,Adyen-Air,AP,123456
SL,4,AirlineLeg,1,AMS,FL123,AA,1,B,A,LND,2025-01-01 10:00,,
SL,5,AirlinePassenger,1,Name,Miguel,Rodriguez,,,
SL,8,ShopperInteraction,Ecommerce
BT,1
FT,1

Optional sub-lines

The MerchantOrderReference sub-line described below can be optionally included in the payment request.

MerchantOrderReference

Field #

Format

Required

Description

1

Fixed value: SL

(tick)

Record type identifier

2

Numeric [0-9]+

(tick)
SL sub-line record number reference within its parent line.

The counter starts at 1, and it increments sequentially by one unit.
3

Fixed value: MerchantOrderReference

(tick)

Transaction type.
Defines the required field types for the specific sub-line.

4

Alphanumeric data

(tick)

Value of your order reference.

Example
FH,1.0,TEST,Company,TestCompany,Default,2,ws@Company.TestCompany,Authorisation,FileHeaderEchoData
BH,1,BlockHeaderEchoData
L,1,MerchantAccount,TestMerchant,Authorisation,Test Product 6,
SL,1,PaymentDetails,100,2,SEK,,,,,
SL,2,Card,4111111111111111,08,2018,737,CardHolderName,,,
SL,3,MerchantOrderReference,XY66AB
BT,1
FT,1