This capability allows the Airline to accept payments using two or more forms of payment. (e.g. cash + voucher redemption)
This capability allows the Seller to execute payments using two or more forms of payment. (e.g. cash + voucher redemption)
Concepts: Payment: https://standards.atlassian.net/wiki/spaces/EASD/pages/574619671
Capabilities: Payment: https://standards.atlassian.net/wiki/spaces/EASD/pages/574717975
Worked Examples: Payment: https://standards.atlassian.net/wiki/spaces/EASD/pages/574488655
For all capabilities, please also consult the list of general guidelines for adherence to best practices that span across several capabilities and messages: |
The repetition of the payment processing function in OrderCreateRQ and OrderChangeRQ allow the Seller to submit more than one payment transaction request per message sent:
/IATA_OrderChangeRQ/Request/PaymentFunctions/PaymentProcessingDetails
For each occurrence of PaymentProcessingDetails, the Seller is free to choose a different payment method and assign a different amount to each transaction. Each of these transactions can be explicitly allocated to particular OfferItems or OrderItems through the payment association structures:
Any one of the following message pairs |
---|
OrderCreateRQ/OrderViewRS |
OrderChangeRQ/OrderViewRS |
Any one of the following message pairs |
---|
OrderCreateRQ/OrderViewRS |
OrderChangeRQ/OrderViewRS |