Last updated: 21 December 2021
This page offers the most recent versions of the openFinance API Framework documents. The documents are offered for free. When downloading documents from this page, you agree to be bound by the following Berlin Group license conditions:
“Creative Commons Attribution-NoDerivatives 4.0 International Public License”
This means that the Specification can be copied and redistributed in any medium or format for any purpose, even commercially, and when shared, that appropriate credit must be given, a link to the license must be provided, and indicated if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use. In addition, if you remix, transform, or build upon the Specification, you may not distribute the modified Specification.
Any OpenAPI files offered on this page are bound by “Creative Commons Attribution 4.0 International Public License” and are allowed to be changed. However, please note that the normative reference still is the Implementation Guidelines document.
Implementation of certain elements of this Specification may require licenses under third party intellectual property rights, including without limitation, patent rights. The Berlin Group or any contributor to the Specification is not, and shall not be held responsible in any manner for identifying or failing to identify any or all such third party intellectual property rights.
Any right, title and interest in and to the copyright and all related rights in topic-related Scheme Rulebooks, belong to the respective Scheme Manager (amongst others, the European Payments Council AISBL - EPC).
The Specification, including technical data, may be subject to export or import regulations in different countries. Any user of the Specification agrees to comply strictly with all such regulations and acknowledges that it has the responsibility to obtain licenses to export, re-export, or import (parts of) the Specification.
The openFinance Taskforce has defined extended value-added services for the openFinance API Framework:
Request to Pay Services
The following documents are defining scheme-independent Request to Pay (RTP) Services for the openFinance API Framework in a first version. It fully derives from the (RESTful) architecture and payment data modelling of NextGenPSD2 APIs. Future functional developments are indicated in the documents.
Resource Status Notification Service
This service communicates status changes of openFinance resources like payment initiations or RTPs. It offers the ASPSP to push this information or a lean callback information to the API Client for example to avoid unnecessary polling traffic on both sides. This specifically applies to asynchronous authorisation processes like introduced by the RTP Services. The subscription to this extended service is done implicitly by the API Client during the creation of the resource. This subscription is valid only during the lifecycle of the resource.
OpenAPI file: follows later
Push Account Information Services
The Services allow banks to push account entries, account statements, account balances as well as incoming Request to Pay messages (RTPs) to API Clients. The API Client can configure detailed trigger criteria during a subscription process to the addressed service. Specifically, the Services will allow merchants to be informed about incoming instant payments immediately after the payment has been booked by the bank. In addition it completes the full process chain for RTP processing by forwarding RTPs immediately to a Corporate client after the RTP has been received by the bank.
05. Berlin Group openFinance API Framework - Operational Rules Push Account Information Services V1.0.pdf
06. Berlin Group openFinance API Framework - Implementation Guidelines Push Account Information Services V1.0.pdf
OpenAPI file: follows later
Archived files are no longer published and can only be made available upon request
Change Management Process:
As a support to the future evolution of the openFinance Framework, a formalised Change Management Process has been established. The current openFinance Framework development is still relying on the NextGenPSD2 Framework. Therefore, the openFinance Change Management Process is still fully connected to the NextGenPSD2 Change Management Process (ref. Available Documents - Change Management Process).
Please have a look at this dedicated page for an overview of existing and past market consultations.