Firstly, a TPP should contact the ASPSP and report the concerns. If no way out could be found, bilaterally, there is the possibility to contact the National Competent Authority.
An ASPSP is free to use a proprietary interface. He is obligated to provide the corresponding information and documents to TPPs. This includes in particular a specification of the implemented interface and a testing facility. In case of reasonable doubts that the used interfaces is compliant to the XS2A specification, a TPP can contact the National Competent Authority.
The testing procedure is ASPSP-specific and may require testing certificates and keys. Whether an ASPSP does require a registration etc. can be found under the given entry in the Test Directory.
All ASPSP are treated equally by the PSD2. However, there exist some country-specific requirements in the specification of PSD2-services. TPPs need a ‘passporting’ registration for the right to act as a TPP in the respective role and country.
In case of an error, the TPP should contact the ASPSP and report the issue.
It is in the common responsibility of the TPP and the ASPSP to fix it and should be solved bilaterally. However, in case of escalation, the National Competent Authority can be informed.
C.p. Question 8. There is no legal obligation on TPPs to test at all. However, NISP strongly recommends to test every supported service with every ASPSP a TPP wants to cooperate with.
The document constitutes the definition of functional requirements for a test environment-called sandbox -that supports the XS2A interface to be used for integration testing by TPPs. The document is available to both NISP members and TPPs.
It provides a definition of best practices for a PSD2 compliant dedicated interface within the NextGenPSD2 API context. It covers functional compliance criteria of dedicated interfaces and how to fulfill these criteria by the NextGenPSD2 API and related backend implementations. The document is available to NISP members.
The Test Directory provides information on the testsandboxes of ASPSPs: ASPSP Name, Country, BIC (6-8 digits), URL of the Sandbox for testing, Information whether a registration is needed with a URL for registration, Version of the implemented NextGenPSD2 interface.
The document constitutes the test concept for the Berlin Group specification of the XS2A interface and describes abstract test scenarios and the infrastructure of tests conducted by the ASPSP.
The document is not available to TPPs.
The document can be found here.