Danske Bank Web Services is our channel for secure automatic payments. You can use this channel, for example, to exchange payment files with Danske Bank by connecting your IT platform (such as ERP, treasury, forecasting and netting systems) to Danske Bank’s central EDI Gateway.

The benefits for you to bring your IT platforms closer to Danske Bank’s IT platform are principally from automation. Automated integration solutions that enable straight-through processing make bank-related processes simpler, efficient, secure, standardized and cost-effective.

The automated channel:

  • improves the transfer process
  • makes it more secure
  • avoids manual processing
  • it can be invoked at any time
  • offers nearly real-time transaction updating inside the ERP/Treasury management system of your choice

Two sets of Web Services combined

At the Danske Bank Group, the Web Services solution is divided into two categories of service:

  • PKI Web Services - provide authentication and confidentiality to the communication
  • EDI Web Services - provide the communication services

Since PKI Web Services provide authentication and confidentiality to the communication, you have to implement PKI Web Services first, and EDI Web Services second. Accordingly, in the text that follows, we will consider them in that order.

PKI Web Services

PKI Web Services handle certificates used to secure the files. With PKI Web Services you are able to do the following:

  • Create certificates used to sign and secure the files
  • Renew the certificates
  • Perform other activities related to certificate processing

EDI Web Services

EDI Web Services handles the communication. With EDI Web Services, you are able to do the following:

  • Send a file with e.g. payments to the Bank
  • Receive a list of files ready to be downloaded from the Bank
  • Receive a file with e.g. an account statement from the Bank

What you need before you start the process of integration

You must have a District agreement with Danske Bank in order to benefit from using the Web Services.

Integration steps

The steps of the integration can be outlined as follows:

1) Get familiar with the roadmap

by reading this document: Implementation Overview (pdf).

2) Two kinds of services

EDI Web Services and PKI Web Services are explained on a high level in these two documents: EDI Web Services (pdf) and PKI Web Services (pdf).

On the implementation level, both of them are based on the same principles, which are described in Encryption, Signing and Compression in Web Services (pdf). Download the examples cited in the document: Encryption and Signing Examples (zip).

You have to get familiar with all the three documents to successfully implement the integration. Additional examples for each kind of message you will be creating, alongside with WSDL and XSD files can be found in WS Examples and Schemas (zip).

3) Implementation of certificates

Implement GetBankCertificate for the PKI Web Services first, as described in the documents above.

Verify the obtained certificate with Danske Bank Root certificate (zip).

The zip-file is signed by the banks VeriSign (Symantec) certificate. You can verify the signature using the procedure described in Danske Bank Root Certificate Verification (pdf).

In addition to the root certificate above, you can look at our Certificate Policy and Certification Practice Statement.

Download Certificate Policy (CP) for the Danske Bank Group PKI Services (pdf)

Download Danske Bank Group Certification Practice Statement - financial services, Finland (pdf)

4) Implement the rest of the PKI calls

Implement at least GetBankCertificate, CreateCertificate and RenewCertificate. A glossary of tags for PKI Web Services can be found in the PKI Web Services (pdf).

5) Implement EDI Web Services

After you have created and registered your certificate, you can implement the integration with EDI Web Services. A glossary of tags for EDI Web Services can be found in EDI Web Services (pdf).