- Overview
- GET /v1/accounts
- GET /v1/accounts/{account-id}
- GET /v1/accounts/{account-id}/balances
- GET /v1/accounts/{account-id}/transactions
- GET /v1/accounts/{account-id}/transactions/{resourceId}
- POST /v1/consents/confirmation-of-funds
- GET /v1/consents/confirmation-of-funds/{consentId}/status
- DELETE /v1/consents/confirmation-of-funds/{consentId}
- GET /v1/consents/confirmation-of-funds/{consentId}
- GET /v1/consents/confirmation-of-funds/{consentId}/authorisations
- POST /v1/consents/confirmation-of-funds/{consentId}/authorisations
- GET /v1/consents/confirmation-of-funds/{consentId}/authorisations/{authorisationId}
- PUT /v1/consents/confirmation-of-funds/{consentId}/authorisations/{authorisationId}
- POST /v1/consents
- DELETE /v1/consents/{consentId}
- GET /v1/consents/{consentId}
- GET /v1/consents/{consentId}/authorisations
- POST /v1/consents/{consentId}/authorisations
- GET /v1/consents/{consentId}/authorisations/{authorisationId}
- PUT /v1/consents/{consentId}/authorisations/{authorisationId}
- GET /v1/consents/{consentId}/status
- POST /v1/funds-confirmations
- Definitions
Overview
Confirmation of Funds Service (PIIS) returns a confirmation of funds request at the ASPSP.
The Account Information Service (AIS) offers the following services
- Transaction reports for a given account or card account including balances if applicable.
- Balances of a given account or card account ,
- A list of available accounts or card account ,
- Account details of a given account or card account or of the list of all accessible accounts or card account relative to a granted consent
Processes on starting authorisations, update PSU identification or PSU authentication data and explicit authorisation of transactions by using SCA are very similar in PIS and AIS and signing baskets services. The API calls supporting these processes are described in the following independently from the service/endpoint. For reasons of clarity, the endpoints are defined always for the Payment Initiation Service, the Payment Cancellation, the Account Information Service (Consents), and Signing Baskets separately. These processes usually are used following a hyperlink of the ASPSP.
Summary
The NextGenPSD2 Framework Version 1.3 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.
Berlin Group is proposing three different models to provide PSU credentials to the API out of which the Redirect Flow is by far the most flexible and provides support for any type of strong customer authentication method already used by the ASPSP. All APIs provide support for the Redirect Flow.
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.
## 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.
This API definition contains the REST-API for requests from the TPP to the ASPSP.
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".