Introduction

This page contains documentation of Danske Bank's Openbanking UK and PSD2 apis.

Danske Bank provides the following sets of APIs:

• Openbanking APIs - APIs for customers in UK, implementation of UK regulations. Requires a network+signing certificate issued by Openbanking UK Directory or a QWAC+QSEAL issued by a QTSP.
• PSD2 APIs - APIs for customers in Denmark, Finland, Ireland, Norway, Poland, Sweden, implementation of PSD2 directive. Requires a QWAC+QSEAL issued by a QTSP.
• Sandbox APIs - testing facilities for Openbanking and PSD2 APIs. Requires a network+signing certificate issued by Openbanking UK Directory or a QWAC+QSEAL issued by a QTSP. Test certificates issued by Microsec are also accepted.

All APIs are based on Open Banking UK standards described here: link. Where necessary the APIs were enhanced to support other EU countries. The API technical specification about each API can be found in the View Specification section. The API urls for Production and Sandbox testing facilities are described in the Endpoints section.

Basic terminology

A network certificate is an x509 certificate that will be used for providing mutual TLS between Danske Bank and the party invoking its APIs. A signing certificate is an x509 certificate that will be used for digitally signing content sent to Open Banking APIs. TPP means a Third Party Provider. TPP is any person / company that wants to integrate with Open Banking APIs and provide a solution based on them. The identity of the provider needs to be well established. That's why the network and signing certificates can be issued only by qualified providers who are able to confirm TPPs identity (and good intentions). PSU means Payment Service User. In most cases PSU refers to a bank customer that uses solutions prepared by TPPs and gives permission to access to his resources via Open Banking APIs. For example it might be a confirmation of a payment or approval to access his account history to provide some analytic insights.