Documentation

This is where you will get background and supplementary information about security model and other pre-requisites for accessing the APIs. This serves as a supplement and additional background to the information available in the API documentation. Also refer to the in-detail sections on TPP Onbarding and Environments

In order to ensure that we have the correct information and that we can trust the certificates that are used for TPP authentication and message sealing, we need to perform an enrollment of TPP. This

All API communication in the context of PSD2 will be handled by using a combination of certificates. There are 2 distinct flows that 3rd party clients need to use in every transaction:

  1. Identificat

The diagram below depicts an overview of the flow, taking place during the creation and authorisation of a payment, including who plays what role. The respective banks responsibility is limited to the

The NemID applet is implemented as customizable. At the same time, it is possible to select the NemID mode limited/standard.

The solution is implemented as parameters to each SCA URL. See example

The diagram below depicts an overview of the flow, taking place during the creation of consent, including who plays what role. BEC's responsibility is limited to the actions happening between the TPP

The scope of this portal and the associated APIs is an implementation of the services described and specified under the PSD2 RTS:

  • Account Information Services (AIS) + Consents
  • Payment

The APIs are made available to TPPs authorized by a local NCA (in Denmark Finanstilsynet) to operate as an AISP, PISP or PIISP under the PSD2 directive. For TPPs registered under a different national