This document is to help participants including ASPSPs, TPPs and consumer experts of which errors are required / recommended to be shared in specific scenarios. The attempt is to put some common scenarios to start with. There could be other scenarios that are not listed here but a similar approach has to be taken by the ASPSPs to provide an appropriate ISO 20022 reason of failure as a first preference. If an appropriate reason is not available then OBL proprietary reason codes can be provided. ASPSPs can provide a customised reason code in exceptional circumstances when an appropriate reason is not available or in instances where a bespoke reason is provided by the PSU in specific scenarios.
Other pages in this section Themes Identified from Consumer & SME Research CX Guidelines Consultation – Research Data Deep Linking for App-to-App Redirection Payment Initiation Services (PIS) Parameters & Considerations Card-Specific Permissions & Data Clusters for AIS Journeys TPP Permissions & CASS Considerations Contingent Reimbursement Model Refund Payment Fulfillment Information flow – Payment Status Information flow Payment Status – SO Transaction Risk Indicators (TRI) definitions and guidance Common Terminology – Preferred Terms and Language Common Error Scenarios – Preferred Status and Reasons 90-Days Re-authentication (delegated SCA) Examples of VRP use cases Read/Write API Specification – Standard Error Codes
Common Terminology – Preferred Terms and Language Previous 90-Days Re-authentication (delegated SCA) Next