Pay: Payment Recovery [PAYRCV]

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

Ability to return details of failed payment attempts (error handling)

Seller

Ability to interpret errors appropriately and take necessary action.

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

Links to EASD Implementation Guidance

Concept: Payment Errors: https://standards.atlassian.net/wiki/spaces/EASD/pages/574587020

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 details about an unsuccessful payment transaction:

/IATA_OrderViewRS/PaymentFunctions/PaymentProcessingSummary

This is to be used in combination with the Error structure, which should contain further explanations on the reasons for the payment processing failure (e.g. “AVS verification failed”, “Incorrect CVV number”…). For a list of available errors and respective codes, see the official Payment Errors documentation.

/IATA_OrderViewRS/Error

The Airline may choose to persist failed payment attempts in Order’s history for traceability (OrderHistoryRQ/RS).

Any one of the following message pairs	Optional Messages
OrderCreateRQ/OrderViewRS	OrderHistoryRQ/RS
OrderChangeRQ/OrderViewRS

Seller

Any one of the following message pairs	Optional Messages
User Interface Screenshots	OrderHistoryRQ/RS
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.