Pay: Payment Transaction Summary [PAYSUM]

Guidance for Schema Version:

21.3 - Please consult the ARM index Schema version 21.3 regarding validation of capabilities within the ARM index program.

Definition of Capability

Airline

The airline has the capability to send confirmation and transactional details summarizing a successful payment transaction.

Seller

The seller has the capability to display the details of a successful payment transaction.

NOTE: System Providers will use the above definition that pertains to their customers for Capabilities Verification.

Links to EASD Implementation Guidance

Related Concepts, Capabilities and Worked Examples:

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

NOTE: Retailing Capabilities Verification Guidance will align to the published EASD Implementation Guidance at all times. From time to time when new guidance is published this will be updated and supersede any Retailing Capabilities Verification Guidance listed below.

Retailing Capabilities Verification Guidance

For all capabilities, please also consult the list of general guidelines for adherence to best practices that span across several capabilities and messages: https://standards.atlassian.net/wiki/spaces/ARMI/pages/584318980

Airline

Demonstrate ability to return detailed transaction summaries following a successfully captured payment from the Seller or customer. Refunds may also be returned in the form of payment summaries:

/IATA_OrderViewRS/PaymentFunctions/PaymentProcessingSummary

Payment statuses need to be included in payment summaries (reference to ATSB Codeset “PAYS“): /IATA_OrderViewRS/PaymentFunctions/PaymentProcessingSummary/PaymentStatusCode

Seller

Demonstrate ability to present transaction details from a successful payment transaction to the Seller’s front-end.

Airline

Any one of the following message pairs
OrderCreateRQ/OrderViewRS
OrderChangeRQ/OrderViewRS

Seller

Screenshots + any one of the following message pairs
User Interface Screenshots
OrderCreateRQ/OrderViewRS
OrderChangeRQ/OrderViewRS

NOTE: For all versions prior to that listed above (generally the most recent), the verification will be based on the guidance available for that version. In the case that no guidance is available, verification will be at IATA’s discretion.