No, NISP won’t provide an ASPSP Directory of the ASPSPs’ productive systems.
In case a PSU-ID allows more than one kind of data item – e.g. IBAN, Name, email address – to identify a PSU, the PSU-ID-Type specifies the type of used data item, hence, whether it’s a name, an IBAN or an email address.
The ASPSP can mandate the usage of a PSU-ID Type. Compare also, IO16.
Note: Also in the case where the ASPSP supports different types of PSU-Ids he might not support the PSU-Id-Type in the requests, since he is able to distinguish between the different typs whithout this explicit information, e.g. he might recognize whether an IBAN or an email adress is entered.
The Sandboxes of the ASPSPs support the same method and format as the productive system of the ASPSP supports.
There is no restriction and the Sandboxes deliver actual data in the correct format so that TPPs can test their functionality with genuine data.
However, these data are static.
In particular, we adapt the specification with respect to errata that refer to errors.
Thus, errata that result from issues that concern the functionality of the interface will be respected in the specification.
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.
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.