Pay: Payment Recovery [PAYRCV]

Guidance for Schema Version:

21.3

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

Related Concepts, Capabilities and Worked Examples:

• 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

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

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).

Seller

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.