An authorization request is carried out in full accordance with the section "Payment request". After a notification from IPS Assist about the successful authorization of the payment means, a separate request should be made for the transmission of flight data.
To transfer flight data send a request to the IPS Assist server via HTTP POST method (n UTF-8 coding).
Request URL for transfer the flight data:
https://<SERVER_NAME>/ addaviafields/addaviafields.cfm
List of request parameters for transfer the fligh flight data:
Parameter | Mandatory field | Adopted values | Description |
merchant_Id | Yes | Number | The merchant identifier in IPS Assist |
login | Yes | 8-20 character string | Login (Latin letters, digits and symbol _) |
password | Yes | 8-20 character string | Password (Latin letters and digits) |
billNumber | Yes | 15 or 16 digits | Unique number of payment corresponding to the order number in IPS Assist |
plan_Mounth | No | 2 digits “00”,“01”, …,“12” | AIRLINE PLAN NUMBER - Months over which deferred payments can be made. Zero if unused. |
invoice_Number | No | 6 digits | AIRLINE INVOICE NUMBER - allocated by the airline for tracing payments. |
charge_Type | Yes | 2 digits | AIRLINE CHARGE TYPE - to determine if journey details are included. “01” - ticket “02” - non-ticket |
airline_Name | Yes | 20 characters | AIRLINE NAME - as it will appear on the cardmember’s bill. |
number_Passendgers | Yes | Number | Number of passengers |
passendger_Name | Yes 1 | 26 characters | PASSENGER NAME – will be displayed on CardMember Statement. Format at SE’s discretion. |
ticket_Number | Yes 2 | 14 digits | TICKET NUMBER - unique reference number from the ticket issued. |
ticket_Issuer | No | 20 characters | TICKET ISSUER - as it will appear on cardmember’s bill. |
ticket_Issuer_Address | No | 40 characters | TICKET ISSUER ADDRESS - the first 13 characters only will appear on the cardmember’s bill. |
departure_Airport | Yes 1 | 20 characters | DEPARTURE AIRPORT - the place of departure, first 3 characters should be Airport Code. |
arrival_Airport_1 | No 1 | 20 characters | ARRIVAL AIRPORT - the place of destination, first 3 characters should be Airport Code. |
carrier_Code_1 | No 1 | 2 characters | CARRIER CODE - the IATA carrier code. |
airline_Class_1 | No 1 | 2 characters | AIRLINE CLASS - the IATA class code. |
stopover_Code_1 | No 1 | 1 character | Stopover Code |
flightNumber_1 | No | String | Flight number |
arrival_Airport_2 | No 1 | 20 characters | ARRIVAL AIRPORT - the place of destination, first 3 characters should be Airport Code. |
carrier_Code_2 | No 1 | 2 characters | CARRIER CODE - the IATA carrier code. |
airline_Class_2 | No 1 | 2 characters | AIRLINE CLASS - the IATA class code. |
stopover_Code_2 | No 1 | 1 character | Stopover Code |
flightNumber_2 | No | String | Flight number |
arrival_Airport_3 | No 1 | 20 characters | ARRIVAL AIRPORT - the place of destination, first 3 characters should be Airport Code. |
carrier_Code_3 | No 1 | 2 characters | CARRIER CODE - the IATA carrier code. |
airline_Class_3 | No 1 | 2 characters | AIRLINE CLASS - the IATA class code. |
stopover_Code_3 | No 1 | 1 character | Stopover Code |
flightNumber_3 | No | String | Flight number |
arrival_Airport_4 | No 1 | 20 characters | ARRIVAL AIRPORT - the place of destination, first 3 characters should be Airport Code. |
carrier_Code_4 | No 1 | 2 characters | CARRIER CODE - the IATA carrier code. |
airline_Class_4 | No 1 | 2 characters | AIRLINE CLASS - the IATA class code. |
stopover_Code_4 | No 1 | 1 character | Stopover Code |
flightNumber_4 | No | String | Flight number |
charge_Details | No | 20 characters | CHARGE DETAILS - description of Charge (other than a ticket). Will appear on CardMember (Excess baggage) |
agent_Code | Yes | 20 characters | Agency Code |
restricted_Ticket_Ind | No 1 | 1 or 0 | Restricted Ticket Indicator |
pnr | Yes | 16 characters | PNR Number |
departure_Date | Yes | YYYYMMDD | Departure date. Format: YYYYMMDD |
1 it is recommended to send this parameters to produce the fully filled extended record for bank.
2 it should be passed within the payment confirmation.
Web-service description for SOAP format can be found on page:
https://<SERVER-NAME>/addaviafields/addaviafields.wsdl
List of response parameters:
Parameter | Value |
addaviafields | 1 – success; 0 – error. |
Data is transferred successfully only once. Resending (after successful sending) returns an error.