What is the PSU-ID-type?

/in , ,

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.

Which errata are added or respected by the specifications and NISP documents?

/in , ,

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.

What is the purpose of “Test Concept for the PSD2 Compliant XS2A Interface”?

/in , ,

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.

What is the purpose of “Test Specification for the PSD2 Compliant XS2A Interface”?

/in ,

This specification is an Excel Sheet that provides an overview of the underlying data sturcture and parameters of tests for PSD2 Services . In particular, it reveals implications a given set of Implementor Options has on the set of relevant test cases. The document is not available to TPPs.

What is the purpose of “ASPSP Test Directory”?

/in ,

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.

What is the purpose of “Compliance Best Practice for the PSD2 Compliant XS2A Interface”?

/in ,

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.

What is the purpose of “TPP Sandbox for the PSD2 Compliant XS2A Interface”?

/in ,

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.