Skip to main content

IATA_PaymentClearanceNotif

Notification · Payment Clearance · Implemented

Implemented

This airline sends IATA_PaymentClearanceNotif to your notification endpoint — see Notifications. Delivers: STTCAP Payment clearance — capture · STTCAN Payment clearance — cancellation.

Limits today:

  • STTCAP — The platform is the ORA and a simulated Clearance Manager (no real Settlement Manager is connected): a captured settlement-plan payment is requested for clearance at capture, and PaymentClearanceRQ clears one that is not yet — one clearance per payment, of exactly its amount.

Rests on simulated supply (settlement) — flagged on every response; see Simulated supply.

Notification of a payment-clearance event.

When to use​

Push channel — reports clearance status.

Transport​

PropertyValue
Method & pathPOST /24.4/PaymentClearanceNotif
Content-Typeapplication/xml
AuthAuthorization: Bearer <token> (or X-API-Key: <key>)
Routing headerIATA-Message-Name: IATA_PaymentClearanceNotif

See Authentication & connection for the full handshake.

Request example​

note

✅ The example below validates against the original XSD.

<?xml version="1.0" encoding="UTF-8"?>
<IATA_PaymentClearanceNotif xmlns="http://www.iata.org/IATA/2015/00/2022.1/IATA_PaymentClearanceNotif">
  <Clearance>
    <ClearanceID xmlns="http://www.iata.org/IATA/2015/00/2022.1/IATA_PaymentClearanceCommonTypes">0000000AAAAAAAA</ClearanceID>
    <ClearancePayeeData xmlns="http://www.iata.org/IATA/2015/00/2022.1/IATA_PaymentClearanceCommonTypes">
      <ClearancePayee>
        <Carrier>
          <AirlineAccountingCode>X</AirlineAccountingCode>
          <AirlineDesigCode>AA</AirlineDesigCode>
        </Carrier>
      </ClearancePayee>
    </ClearancePayeeData>
    <ClearancePayerData xmlns="http://www.iata.org/IATA/2015/00/2022.1/IATA_PaymentClearanceCommonTypes">
      <ClearancePayer>
        <Carrier>
          <AirlineAccountingCode>X</AirlineAccountingCode>
          <AirlineDesigCode>AA</AirlineDesigCode>
        </Carrier>
      </ClearancePayer>
    </ClearancePayerData>
    <NetClearanceAmount xmlns="http://www.iata.org/IATA/2015/00/2022.1/IATA_PaymentClearanceCommonTypes" CurCode="X">1</NetClearanceAmount>
    <PaymentBrandCode xmlns="http://www.iata.org/IATA/2015/00/2022.1/IATA_PaymentClearanceCommonTypes">1</PaymentBrandCode>
    <PaymentCommitmentDateTime xmlns="http://www.iata.org/IATA/2015/00/2022.1/IATA_PaymentClearanceCommonTypes">2024-06-01T09:00:00Z</PaymentCommitmentDateTime>
    <ProcessRuleCode xmlns="http://www.iata.org/IATA/2015/00/2022.1/IATA_PaymentClearanceCommonTypes">IATACAA</ProcessRuleCode>
    <RemittanceDate xmlns="http://www.iata.org/IATA/2015/00/2022.1/IATA_PaymentClearanceCommonTypes">2024-06-01</RemittanceDate>
    <SettlementDate xmlns="http://www.iata.org/IATA/2015/00/2022.1/IATA_PaymentClearanceCommonTypes">2024-06-01</SettlementDate>
    <StatusCode xmlns="http://www.iata.org/IATA/2015/00/2022.1/IATA_PaymentClearanceCommonTypes">AAAAA</StatusCode>
  </Clearance>
  <ClearanceCount>1</ClearanceCount>
</IATA_PaymentClearanceNotif>

Key fields​

Top-level content model of IATA_PaymentClearanceNotif (one level deep, including inherited content):

FieldTypeRequiredRepeatableNotes
ClearanceClearanceNotifType✓✓
ClearanceCountCountType✓—
PayloadStandardAttributesPC_IATA_PayloadStandardAttributesType——

Build it with the SDK​

The @oms/ndc-24-4 package is a reference SDK — build, serialize, parse, and validate this message in code:

import { IATA_PaymentClearanceNotif } from '@oms/ndc-24-4';

const xml = IATA_PaymentClearanceNotif.toXML(payload, { pretty: true });
const obj = IATA_PaymentClearanceNotif.parseXML(xml);    // round-trips
IATA_PaymentClearanceNotif.schema.parse(obj);            // strict Zod validation