PSD2 Obstacles

Public registry of PSD2 obstacles

The table below contains identified PSD2 obstacles arising out of ASPSP implementation of PSD2 account access requirements. These obstacles existed at the time of compilation of this list over 2021-2022.

What is the problem we are trying to solve?

With more than 3 years of PSD2 API implementation we still aren't seeing a successful and coherent implementation of PSD2 that Fintechs can succeed on. This public registry shall help lead to the fruition and successful implementation of PSD2 by disclosing obstacles, and thus putting additional pressure for the much needed removal of these obstacles.

This public disclosure of obstacles has the following benefits:

  • ASPSPs can consult the registry, acknowledge and address obstacles.

  • NCAs can consult the registry and request evidence of non-compliance that can form the basis for investigating a bank's dedicated interface. Thus enabling NCAs to put further pressure on ASPSPs on resolving non-compliance.

  • The EBA can consult the registry to see where NCAs fail to achieve compliance. Thus putting further pressure on NCAs to address non-compliance in their market.

  • This is a multi-level effect that can accelerate a successful PSD2 implementation.

Disclaimer: ETPPA does not accept any liability from any inaccuracies or improper listing of obstacles. All obstacles listed were unresolved at the time of entry into the registry. ETPPA welcomes any contact regarding a particular obstacle in case of proof of obstacle resolution. In case you wish to request more information on any of the listed obstacles or in case an ASPSP wishes to inform ETPPA of any inaccuracies due to identified obstacles being resolved, please send a mail to info@etppa.org with the obstacle ID number, member state and bank alias in the email subject. Please also include your name and organisation.