Description

The Open Banking Directory is the key Architectural Component that enables Third Party Providers (TPPs)to enroll in the Open Banking Directory and initiate interactions through APIs with Account Servicing Payment Service Providers (ASPSPs). At its core, the Directory is an identity and access management service providing identity information supporting natural persons, organizations, and software identity classes.

The Open Banking Directory will provide the necessary functional capabilities required for Third Party Providers (TPPs) that successfully enrolled with Open Banking to identify and onboard with ASPSPs so that they can use the APIs provided by the ASPSPs. ASPSPs can utilize technical information contained within the Directory to validate organization and software identity (active/inactive), QTSP validity, and member state NCA register status (including passport information).

The functional capabilities can be broken up broadly into three capability groups:

Manage Identities and Access: The ability to issue and manage identity records for organizations and natural persons that interact with the Open Banking Directory.
Manage Certificates and Keys: The ability to upload, manage,e and remove eIDAS certificates (QWACs and QSeals), signing keys, and encryption keys. The ability to issue, manage,e and revoke OB digital certificates.
Manage Directory Information: The ability to update and find information maintained in the Directory - either through APIs and/or a self-service user interface (UI) delivered as a web application.

 

Documentation

  • Contents
    Check on the OpenAPI Documentation carefully to understand the required request and structure.
     
  • Security
    Remember to retrieve the credentials of your App in "My Apps" checking on the Consumer Key and Consumer Secret.

Error Format

All OpenBanking APIs throw errors in following JSON format:

{"Id": "123",
"Code": "123",
"Message":"Message example",
"Description": "Description of error",
"Errors":[
{
"ErrorCode":"AC17",
"Message":"Message Example",
"Path":"/accounts",
"Url":"url.example.com"
}] }
OpenAPI specification