This capability allows an Airline to accept payment for an existing Order or Order Items
This capability allows the Seller to provide payment information for an existing Order or Order Items. Payment may be for some or all Order Items.
Capability: Pay for an Existing Unpaid Order or Order Items: https://guides.developer.iata.org/v213/docs/cappay02-pay-for-an-existing-order
Concepts: Payment: https://guides.developer.iata.org/v213/docs/payment-concepts
Capabilities: Payment: https://guides.developer.iata.org/v213/docs/payment-capabilities
Worked Examples: Payment: https://guides.developer.iata.org/v213/docs/payment-use-cases
Paying for an existing Order, often referred to as “deferred payment”, allows the Seller to request the creation of an Order without having to commit payment instructions. When an Airline supports deferred payments, payment can be collected by the Seller/customer via a subsequent OrderChangeRQ message.
While an Order is being presented (in OrderViewRS) with unpaid OrderItems, the Airline would normally still disclose what are the supported forms of payment possible to the Seller. This can be done globally for the entire Order, or on a per-OrderItem-level.
The payment functions possible through OrderChangeRQ are the same as for OrderCreateRQ, except for the payment redirection mechanism, which is only supported as part of deferred payments flows.
Deferred payments can also take place following a reshopping flow, whereby certain new services or changes to existing OrderItems are committed into the Order by the airline, but paid for subsequently via another OrderChangeRQ. Again, the principles around allocating payments to existing OrderItems applies in the same way as for “instant payments” for Offers/OfferItems at the time of Order creation.
The Airline is expected to define payment time limits for any unpaid or partly-paid OrderItems: