Specifications

RESTful APIs that enable TPPs to access information and initiate payments for customers, by connecting to ASPSPs securely, efficiently, and with customer consent.

Allowing account providers to develop API endpoints which can be accessed by third party developers to build mobile and web applications for banking customers.

Technical information describing the Open Banking Directory, and the roles and functions of each participant in the Directory.

Defines the APIs for TPPs to submit Software Statement Assertions to ASPSPs for the purpose of creating OAuth clients that are registered with ASPSPs.

Specifications for MI Reporting of ASPSPs to Open Banking. MI specification includes detailed Data Dictionary and examples of MI reporting template.

(Requires access to Confluence Collaboration Space)

The Open Banking API standard has adopted FAPI 1 as the security profile. FAPI is a highly secured OAuth profile provided by the Open ID Foundation.
V3 of the Open Banking Standard used FAPI 1 Implementers Draft 2, which was the current specification available at the time of release.
With the introduction of v4 of the Open Banking API Standard it was determined by a vote at the Technical Design Authority to implement the final release of the FAPI 1 Advanced specification

The OpenID Financial Grade API (FAPI) specification provides implementation guidelines for online financial services by developing a REST/JSON data model protected by a highly secured OAuth profile.

A profile of the OpenID Connect Client Initiated Backchannel Authentication Flow (CIBA), that supports decoupled interaction methods. This document aligns CIBA with the other FAPI parts, providing security recommendations for use with APIs that require financial-grade security.