NextGenPSD2 Downloads

Last updated: 19 November 2020

This page offers the most recent version of the NextGenPSD2 Access to Account 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.

​

  • 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.

​

Creative Commons

Available Documents

Core PSD2 Compliancy:

Download the above Core PSD2 Compliancy documents as a .ZIP file.
  • OpenAPI 3.0 files:
    • psd2-api 1.3.8 2020-11-18v1.yaml
      Please note that this OpenAPI file may be updated frequently due to technical errata and that the normative reference still is the Implementation Guidelines document. Also note that starting from the version ‘psd2-api 1.3.6 2020-05-28’ the version number and contents of the OpenAPI file are related to the corresponding published and latest version of the Implementation Guidelines plus errata (previous versions of the OpenAPI file sometimes had a deviating version numbering which made it difficult to match with published Implementation Guidelines). The date in the OpenAPI filename (format: yyyy-mm-dd) is reflecting the date of publication of the OpenAPI file.
Former versions of the NextGenPSD2 Framework Operational Rules document: Former versions of the NextGenPSD2 Framework Implementation Guidelines document:

Extended value-added services:

The NextGenPSD2 Taskforce has defined extended value-added services for the NextGenPSD2 XS2A Framework:

The Core NextGenPSD2 services are requiring the TPP to pull information about status changes on resources created by the TPP. The Lean Push Service offers the ASPSP to push this information or a lean callback information to the TPP for example to avoid unnecessary polling traffic on both sides. The subscription to this extended service is done implicitly by the TPP during the creation of the resource. This subscription is valid only during the lifecycle of the resource.

OpenAPI file: psd2-api-lean_push_notifications v1.0.0-20200519v2.yaml

Following PSD2 requirements, the PSU consent for Confirmation of Funds Requests is given directly from the PSU to the ASPSP. The Confirmation of Funds Consent Service enables the TPP to support this service as part of the PSU onboarding process directly via the NextGenPSD2 XS2A interface. There is no subscription supported for this service in the XS2A interface.

OpenAPI file: psd2-confirmation-of-funds-consent 2.0 20190607.yaml

This document defines Additional Account Information Services for the NextGenPSD2 XS2A Interface. The additional account information standardised in this version of the service addresses the provision of the TPP with the list of trusted beneficiaries (noted as "List of Trusted Beneficiaries Service"), where “trusted beneficiaries” are referencing to the definitions within [EBA-RTS].

OpenAPI file: psd2-api-trusted_beneficiaries v1.0.0 20200519v1.yaml

The service defined in this document offers the possibility for a Third Party Provider (TPP) to request information on single card accounts that are used to reconcile credit card transactions, allowing the TPP to distinguish on card accounts with multiple Primary Account Numbers (PANs), also in the consent modelling.

OpenAPI file: psd2-api-ais-single-cards 1.1.0 2020-11-18v1.yaml

The service defined in this document offers a consent API which specifies in detail the nature and scope of the TPP access to account information. This is especially helpful for TPPs when they are offering AIS services to different subsystems or to other companies under regulation of civil law. The new extended service allows TPPs to be aware of the PSU identity and to aggregate the PSU related consent details from different sources within their system or from companies with which they have a cooperation.
For the extended value-added services it is not determined whether a contract between ASPSP and TPP to use these services is established.



Archive:

Archived files are no longer published and can only be made available upon request

  • psd2-api 1.3.6 2020-08-14.yaml
  • 04. NextGenPSD2 XS2A Interoperability Framework - Extended Services - cardBalances V1.0_20200714.pdf
  • 03a. NextGenPSD2 Access to Account Interoperability Framework - V1.3.6 Errata_20200714.pdf
  • 05. NextGenPSD2 Access to Account Interoperability Framework - V1.3.6 Domestic Payment Definitions_20200807.pdf
  • 06. NextGenPSD2 Access to Account Interoperability Framework - Security Bulletin V1_20191106.pdf
  • psd2-api 1.3.6 2020-05-28.yaml
  • 05. NextGenPSD2 Access to Account Interoperability Framework - V1.3.6 Domestic Payment Definitions_20200327.pdf
  • 03a. NextGenPSD2 Access to Account Interoperability Framework - V1.3.6 Errata_20200327.pdf
  • 05. NextGenPSD2 XS2A Interoperability Framework - V1.3.4 Domestic Payment Definitions 20190705.pdf
  • 20191106 - Status NextGenPSD2 Change Requests.pdf
  • psd2-api 1.3.5 20191216v1.yaml
  • 06. NextGenPSD2 XS2A Interoperability Framework - Security Bulletin V1_20191106.pdf
  • 07. NextGenPSD2 XS2A Interoperability Framework - Extended IG Standing Order Report V1_20191106.pdf
  • 08. NextGenPSD2 XS2A Interoperability Framework - Extended IG Account Owner Name V1_20191125.pdf
  • 09. NextGenPSD2 XS2A Interoperability Framework - V1_3_4Errata 20191206.pdf
  • psd2-api 1.3.4 20190717v1.yaml
  • 20190701 - Status NextGenPSD2 Change Requests.pdf
  • psd2-api 1.3.3 20190412.yaml
  • 05. NextGenPSD2 XS2A Interoperability Framework - V1_3 Domestic Payment Definitions 20190329.pdf
  • 04a. NextGenPSD2 XS2A Interoperability Framework - V1_3Errata 20181220.pdf
  • 04b. NextGenPSD2 XS2A Interoperability Framework - V1_3Errata 20190214.pdf
  • 04c. NextGenPSD2 XS2A Interoperability Framework - V1_3Errata 20190329.pdf
  • psd2-api 1.3.3 20190318.yaml
  • psd2-api 1.3.2 20190228.yaml
  • psd2-api 1.3.2 20190215.yaml
  • 04. NextGenPSD2 XS2A Interoperability Framework - V1_3Errata 20181220.pdf
  • psd2-api 1.3 20181220.yaml
  • 04. NextGenPSD2 XS2A Interoperability Framework - ChangeLog V12 V13 20181019.pdf
  • 01. NextGenPSD2 XS2A Interoperability Framework - General Introduction Paper V1_20180208.pdf
  • psd2-api 1.2 Update 2018-08-17.yaml
  • NextGenPSD2 XS2A Interoperability Framework - ChangeLog V11 V12 20180813.pdf
  • NextGenPSD2 XS2A Interoperability Framework - Bulletin 01 - 20180914.pdf
  • psd2-api 1.2 Update 2018-07-27.yaml
  • psd2-api 1.2 Update 2018-07-26.yaml
  • psd2-api 1.2 2018-07-25.yaml
  • NextGenPSD2 XS2A Interoperability Framework - ChangeLog V1 V11 20180518.pdf

Change Management Process:

As a support to the future evolution of the NextGenPSD2 Framework, a formalised Change Management Process has been established. The established Change Management Process accounts for technical and business implications of raised change requests. Multiple institutions are involved in the assessment and decision-making process, ensuring a balanced and transparent approach. Please use the below Template Change Request Form for submitting change requests, according to the procedure described in the Change Management Process document.

A Catalogue of Change Requests shows the status and classification of each submitted Change Request, providing also a link to the detailed Change Requests: Please note that the Catalogue of Change Requests is frequently updated and only includes submitted Change Requests that have had a first assessment and discussion by the NextGenPSD2 Taskforce.



Market Consultations:

Please have a look at this dedicated page for an overview of existing and past market consultations.



© The Berlin Group - Disclaimer and Dataprivacy Policy