Overview
  • 30 Nov 2021
  • 1 Minute to read
  • Contributors
  • Dark
    Light
  • PDF

Overview

  • Dark
    Light
  • PDF

1. Cancellation Request / ClearanceCancellationRQ

request to cancel Clearances that have already been accepted by the Clearance Manager. Clearance can only be cancelled by ORA since ORA is the only party that can initiate a Clearance Request with the ClearanceRQ message. If ORA decides to cancel a Clearance, then ORA must send a ClearanceCancellationRQ message to the Clearance Manager.

Please see IATA_PaymentClearanceCancellationRQ.xml.

2. Cancellation Response / ClearanceCancellationRS

this is the response sent by the Clearance Manager back to ORA as an acknowledgement of the Cancellation Request. It delivers either the errors that prevented message processing and response to be generated, or a response. The response provides information if the cancellation request was successful or not and why given cancelation request could not be fulfilled. Clearances that have been successfully cancelled will be identified with their Clearance ID and will have status “Cancelled”. Clearances that could not be cancelled will be identified with their Clearance ID and will show their current status code and the reason why the cancellation request could not be fulfilled. “Clearance Failure Reason Code” provides the reason why a Clearance could not be cancelled and can be one of the codes listed in Annex B under code list identifier “CFRC – Clearance Failure Reason Code”

The Clearance Manager establishes and communicates the rule on how a Clearance can be cancelled. After changing the Clearance Status Code to “Cancelled” the Clearance Manager must send ClearanceNotif message for the same Clearance, identified with its ClearanceID, to the Seller where the Clearance Status Code is “Cancelled” too. Thus, the Clearance Manager informs the Seller about the change of status of the Clearance, which in this case is cancellation.

Please see IATA_PaymentClearanceCancellationRS.xml.


What's Next