Ability to return details of failed payment attempts (error handling)
Ability to interpret errors appropriately and take necessary action.
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
Demonstrate ability to return details about an unsuccessful payment transaction:
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.
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 |
Any one of the following message pairs | Optional Messages |
---|---|
User Interface Screenshots | OrderHistoryRQ/RS |
OrderCreateRQ/OrderViewRS | |
OrderChangeRQ/OrderViewRS |