24/Mar/2021 18:27:39 PM CET


Production and Sandbox Endpoints

Production and Sandbox URLs:


# Summary The **NextGenPSD2** *Framework Version 1.3.6* offers a modern, open, harmonised and interoperable set of Application Programming Interfaces (APIs) as the safest and most efficient way to provide data securely. The NextGenPSD2 Framework reduces XS2A complexity and costs, addresses the problem of multiple competing standards in Europe and, aligned with the goals of the Euro Retail Payments Board, enables European banking customers to benefit from innovative products and services ('Banking as a Service') by granting TPPs safe and secure (authenticated and authorised) access to their bank accounts and financial data. The possible Approaches are: * Redirect SCA Approach * OAuth SCA Approach * Decoupled SCA Approach * Embedded SCA Approach without SCA method * Embedded SCA Approach with only one SCA method available * Embedded SCA Approach with Selection of a SCA method Not every message defined in this API definition is necessary for all approaches. Furthermore this API definition does not differ between methods which are mandatory, conditional, or optional. Therefore for a particular implementation of a Berlin Group PSD2 compliant API it is only necessary to support a certain subset of the methods defined in this API definition. **Please have a look at the implementation guidelines if you are not sure which message has to be used for the approach you are going to use.** ## Some General Remarks Related to this version of the OpenAPI Specification: * **This API definition is based on the Implementation Guidelines of the Berlin Group PSD2 API.** It is not a replacement in any sense. The main specification is (at the moment) always the Implementation Guidelines of the Berlin Group PSD2 API. * **This API definition contains the REST-API for requests from the PISP to the ASPSP.** * **This API definition contains the messages for all different approaches defined in the Implementation Guidelines.** * According to the OpenAPI-Specification [https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.1.md] "If in is "header" and the name field is "Accept", "Content-Type" or "Authorization", the parameter definition SHALL be ignored." The element "Accept" will not be defined in this file at any place. The elements "Content-Type" and "Authorization" are implicitly defined by the OpenApi tags "content" and "security". * There are several predefined types which might occur in payment initiation messages, but are not used in the standard JSON messages in the Implementation Guidelines. Therefore they are not used in the corresponding messages in this file either. We added them for the convenience of the user. If there is a payment product, which needs these fields, one can easily use the predefined types. But the ASPSP need not to accept them in general. * **We omit the definition of all standard HTTP header elements (mandatory/optional/conditional) except they are mentioned in the Implementation Guidelines.** Therefore the implementer might add these in his own realisation of a PSD2 comlient API in addition to the elements defined in this file. ## General Remarks on Data Types The Berlin Group definition of UTF-8 strings in context of the PSD2 API has to support at least the following characters a b c d e f g h i j k l m n o p q r s t u v w x y z A B C D E F G H I J K L M N O P Q R S T U V W X Y Z 0 1 2 3 4 5 6 7 8 9 / - ? : ( ) . , ' + Space


Alle Aktuell
Posted By JayMoney80 on 1598522766000
Alle Aktuell
Posted By JayMoney80 on 1598522767000
Alle Aktuell
Posted By JayMoney80 on 1598522767000


You require an access token to try the API. Please login and subscribe to the API to generate an access token.   If you already have an access token, please provide it below.

Warning! The selected application does not have an access token for the selected environment. Please go to the subscription page and generate an access token first.
Authorization : Bearer
Name Summary
PSD2 API Solution - DKB Documentation Supported DKB products and methods, which are available for AISP (Account Information Service Provider), PISP (Payment Initiation Service Provider) and PIIS (Payment Instrument Issuing Service Provider) via the XS2A interface. Download
Implementation Guidelines NextGenPSD2 Access to Account Interoperability Framework Download
TPP FAQs Frequently Asked Questions from our Customer Service – TPP Support Download
OperationalRulesV1.3 20181221 NextGenPSD2 Access to Account Interoperability Framework - Operational Rules V1.3_20181221.pdf - Berlin Group functional document Download
BG XS2A Extended Service IG Consent CoF V2.0 20190301 NextGenPSD2 XS2A Framework Implementation Guidelines Extended Services Confirmation of Funds Consent Download
PSD2 API Solution - Documentation for TPPs v2.1 TPP documentation of our PSD2 compliant XS2A interface. This document assists TPPs to set up their application against the "CLX PSD2 API Solution". It describes the Sandbox and TPP registration process and explains the architecture and workflows Download
Name Summary
Contingency Measures - YAML-File The YAML-File for using the Contingency Measures Download