OrderChange 17.2
Â
Functional Description
Â
OrderChange allows payment and servicing of an existing Order.
The Order can be:
Unpaid (booked and on hold)
Paid for (issued but no services used)
Partially used (some of the services used some not)
Whenever servicing an existing Order, an OrderRetrieve should always be done before using this service. This ensures you have the latest version of the Order, which could have changed.
The Order Change API currently supports the following types of changes:
Action/Function | Use |
---|---|
Payment | Pay for services in a previously created Order that is held with a PaymentTimeLimit. Orders on Hold with ancillaries have to be paid for in full (all OrderItems) with this service. The following payment methods can be used depending on the type of Seller (IATA or Non IATA) and the Market
|
Add | This action is intended to perform the following changes:
|
Delete |
|
Cancel |
|
Voluntary Change |
 ***WARNING*** Associated ancillaries that cannot be changed/moved with the flights are lost, and a warning is shown in both the OrderReshopRS and OrderViewRS. |
If there is a cancellation or a passenger is deleted from an order, and it is necessary to refund money to the client, the money is always refunded back to the original form of payment used for the tickets.
Partial refund should not be used if all of the ticket coupons are open for use, in that case OrderReshop and OrderCancel should be used for total refund.
NDC Servicing operations for corporate will only validate that travel agency indicated in the request is the same as generated the order. If corporateID is present in the request, it will only be checked when the order has been generated with corporateID.
Â
Â
Â