a. This Service enables to pay and issue an order for the selected flight offer and seat[1..*] (Issue EMDs on successful seat purchase in the same transaction)>
b. This Service enables to create a Hold booking without payment for the selected flight offers (Seat not allowed for Hold booking)
c. Both booking (PNR) and document (ETicket and EMDs) details are returned in the OrderViewRS. Only PNR details are returned for Hold booking
NDC Schema: IATA OrderCreateRQ and OrderViewRS v21.3.
Form of Payment - Credit Card - Secured (3D Secure 2.0).
This is a complete replica of production and a test environment where developers can build against our NDC APIs and validate their code for build of new features, ahead of certification and go-live. This environment should also be used for debugging
This environment will have the same capability features as Sandbox but in addition we may deploy breaking changes or new features in advance of release to Sandbox and Production in order to give developers early visibility.
Supports only from 1 to 9 passengers. Request needs at least 1 x ADT Pax. Number of Infants cannot be greater than Adult passengers. Groups are out of scope.
Supported Passenger Type Codes (PTC) are following:
Service accepts the following field length and characters, else it returns an error
ID <-> RefID attribute request/response formats are shown as follows:
The requested OfferID in OrderCreate request must be from be from the previous OfferPrice response (else it returns an error).
OfferPrice response OfferID and Upsell-OfferID(s) are valid for 20 minutes, within the time-limit OrderCreate request must be triggered, otherwise, the OfferID will be invalid and will return an error on request).
E-Ticketing Issuance has failed but Payment has been successful. In this case, Service will return an error with payment rollback and cancellation of the created OrderID and Booking.
Supported Payment Card Types.
The service returns an error, when the OrderCreateRQ request contains no Contact [email, phone] details.
The service sends an eTicket Confirmation email after successful payment, booking creation and issued eTicket(s)
The service checks if the agent calling the service has the rights. If the agent does not have such authority, then the service will not process and will return an error.
Supported Program Code – ENUM values. Invalid Program Code will return an error.
For Program Code VS, DL (Virgin Atlantic/Flying Club, Delta Airline/Sky Miles) the entered Loyalty/Frequent Flyer Number is validated with the Passenger Given + Surname. Mismatch in Frequent Flyer Number and Name will return an Warning in the response
For Partner Codes – KL, AF, CA, NZ, NH, HA, 9W, SK, MH, SQ, SA, VX, VA Only the entered Loyalty/ Frequent Flyer Number - Syntax/ Algorithm is validated (Passenger name validation/ check is not done)
For US & CA countries – Address information is validated (Street, City, Zip-code, State) If given Address is Invalid – Error code: 317 & 708 is returned.
Before Seat Payment, we will revalidate the seat price & its availability with or without Frequent Flyer.
If Availability for the requested seat is Occupied or taken over. We will not continue with the seat payment for other passenger(s) in the same segment:
If Seat price is discounted due to frequent flyer in the request. We will continue Payment with the seat discounted price:
For any Seat related issues, warning message will be returned in the OrderViewRS.
Before proceeding for payment authorization, we will be validating received ECI values and authentication status.
An Order without ticket is created when OrderCreateRQ is called without the payment section. These type of orders will have a payment time limit, within which the Order must be ticketed. In the case of time limit expiration, the inventory will be released and the seller must start over again.
Goods and Service Tax (GST) will be accepted for agents based out of India, and will be added to the PAX details in the PNR. Applicable only if at least one segment originates from an Indian city.