Connect your ERP to Danske Bank.
EDI Web Services for accounts in Denmark, Finland, Norway, Sweden, Poland, the UK and Ireland, secured with two certificates issued through PKI Web Services. Payments go out as pain.001.001.03 or .09; status and statements come back as pain.002, camt.052, camt.053 and camt.054.
The bank
- Legal name
- Danske Bank A/S
- Head office
- Copenhagen, Denmark
- CVR
- 61126228
- Supervisor
- Danish FSA
- Channels
- EDI Web Services, SFTP, SWIFTNet
- Payments
- pain.001.001.03 and pain.001.001.09
Published by the bank
The legal footers of Danske's country sites and its London branch page, and the debtor-agent BIC list in the pain.001.001.03 MIG v3.6.
Bank details
| Legal name | Danske Bank A/S |
| Registered office | Bernstorffsgade 40, DK-1577 Copenhagen V, Denmark |
| CVR | 61126228, Danish Business Authority |
| Supervisor | Danish Financial Supervisory Authority |
| Northern Ireland | Northern Bank Limited is a member of the Danske Bank Group |
| Country | Entity | BIC | Register | Supervisor |
|---|---|---|---|---|
| Denmark (head office) | Danske Bank A/S | DABADKKK | CVR 61126228, Danish Business Authority | Danish Financial Supervisory Authority |
| Finland | Danske Bank A/S, Suomen sivuliike | DABAFIHH | Business ID 1078693-2 | Not published |
| Sweden | Danske Bank A/S, Danmark, Sverige Filial | DABASESX | Org. no. 516401-9811, Swedish Companies Registration Office | Danish Financial Supervisory Authority |
| Norway | Danske Bank A/S NUF | DABANO22 | Org. no. 977074010 | Danish Financial Supervisory Authority and Financial Supervisory Authority of Norway |
| Poland | Danske Bank A/S Spółka Akcyjna Oddział w Polsce | DABAPLPW | KRS 0000250684, District Court for the City of Warsaw | Polish Financial Supervisory Authority and Danish Financial Supervisory Authority |
| England | Danske Bank A/S, London Branch | DABAGB2L | Branch no. BR000080, England and Wales | Danish Financial Supervisory Authority; authorised by the Prudential Regulation Authority, regulated by the Financial Conduct Authority |
| Northern Ireland | Northern Bank Limited, trading as Danske Bank | DABAGB2B | R568, Northern Ireland; FCA register 122261 | Prudential Regulation Authority and Financial Conduct Authority |
| Ireland | Danske Bank A/S, Irish branch | DABAIE2D | Registered branch, company no. 905623 | Danish Financial Supervisory Authority; Central Bank of Ireland for conduct of business rules |
Published by the bank
Channels and Security page on danskeci.com, EDI Web Services v5.2, PKI Web Services v2.9.
Channels
| Channel | EDI Web Services |
| Protocol | SOAP 1.1 on the WSDL defined by Sampo Bank, Nordea and OP-Pohjola; request-response, the client always connects |
| Transport | HTTPS |
| Content security | Every request signed (XML signature) and encrypted to Danske's encryption certificate; replies signed by Danske and normally encrypted; GZIP or DEFLATE |
| Keys and certificates | Two X.509 certificates, signing and encryption, issued by Danske through PKI Web Services from your PKCS#10 requests; 2048-bit RSA |
| Agreement | District agreement with the EDI Web Services module, and a User Authorisation for the user |
| Countries | Denmark, Finland, Norway, Sweden, Poland, the UK, Ireland |
| Other channels | SFTP with OpenPGP; SWIFTNet FileAct; SWIFTNet FIN, MT formats only; District, Danske's online banking, with eSafeID or Finnish, Norwegian or Swedish BankID |
| EDI Web Services address | https://businessws.danskebank.com/financialservice/edifileservice.asmx |
| PKI Web Services address | https://businessws.danskebank.com/ra/pkiservice.asmx |
| Message lifetime | SOAP messages older than 5 minutes are not accepted |
| RequestId | Unique for three months |
| Upload size | 70 MB per file, after compression |
| Files per agreement per day | Up to 80,000 uploaded and 269,190 downloaded; up to 10,000 file references per DownloadFile |
| File list | NEW by default; downloaded files become unavailable overnight. Danske asks for lists at fixed times, not every five minutes |
| Service window | 02:55 to 02:56 CET every night; requests in that minute are not handled |
The setup steps at the foot of this page cover EDI Web Services. SFTP is secured with OpenPGP and SWIFTNet runs on SWIFT, so those steps do not apply to them.
BankConnector
Payment types and pain.001 versions as built in our engine. BICs from Danske's pain.001.001.03 MIG v3.6.
Payment types by country
| Country | Debtor agent BIC | Channel | Payment types | pain.001 |
|---|---|---|---|---|
| Denmark | DABADKKK | EDI Web Services | SEPA credit transfer, SEPA Instant credit transfer, Domestic account transfer, International payment, FIK payment | pain.001.001.03 |
| Finland | DABAFIHH | EDI Web Services | SEPA credit transfer, SEPA Instant credit transfer, Domestic account transfer, International payment | pain.001.001.03 |
| United Kingdom | DABAGB2B | EDI Web Services | SEPA credit transfer, BACS, CHAPS, Faster Payment, International payment | pain.001.001.03 |
| Norway | DABANO22 | EDI Web Services | SEPA credit transfer, Domestic account transfer, International payment, KID payment | pain.001.001.03 |
| Poland | DABAPLPW | EDI Web Services | SEPA credit transfer, Split payment (MPP), International payment | pain.001.001.03 |
| Sweden | DABASESX | EDI Web Services | SEPA credit transfer, SEPA Instant credit transfer, Bankgiro, PlusGiro, Domestic account transfer, International payment | pain.001.001.03 |
Danske’s MIG also lists DABAGB2L for the London branch and DABAIE2D for Ireland as debtor-agent BICs.
Published by the bank
EDI Web Services v5.2 Appendix D and E, pain.001.001.03 MIG v3.6 (10 July 2026) and Appendix v5.3 (5 August 2026).
Formats Danske Bank accepts
| Message | Version | File type | Content |
|---|---|---|---|
| pain.001 | 001.03, 001.09 | pain.001.001.03, pain.001.001.09 | Payment orders |
| pain.002 | 001.03, 001.10 | pain.002.001.03, pain.002.001.10 | Status: ACK after the format check, REJECTED after the payment check, BOOKED after execution |
| camt.053 | 001.02 | camt.053.001.02 | End-of-day account statement, subtype FIN |
| camt.052 | 001.02 | camt.052.001.02 | Intraday report, generated at each download: BAL balances, ACC entries since the last camt.052 |
| camt.054 | 001.02 | camt.054.001.02 | Debit and credit notifications: DNOT, CNOT, DCNOT, DBNSAL, DBOSAL, DBNSWEEP, CRNSWEEP; FBFOPFI in Finland |
| camt.055 | 001.01 | camt.055.001.01 | Cancellation request for payments sent as pain.001.001.02 or .03, and for SEPA direct debits |
| camt.029 | 001.03 | camt.029.001.03 | Answer to a payment cancellation request |
| pain.008 | 001.02 | pain.008.001.02 | SEPA Core and B2B direct debits to Collection Service |
| MT940, MT941, MT942 | SWIFT | MT940SW, MT941SW, MT942SW | Statement, balance and transaction reports; German and SAP variants of MT940 and MT942 also listed |
| Character set | UTF-8, ISO-8859-1 or ISO-8859-15, processed as Windows-1252; other characters become look-alikes or ? |
| Message ID | Unique per District agreement for at least 3 months; a duplicate rejects the message |
| EndToEndId | Unique per District agreement for at least 3 to 4 months; a duplicate rejects the payment |
| PmtInfId and InstrId | Uniqueness not checked |
| Transaction count | NbOfTxs is not checked and comes back in the pain.002 |
| Debtor agent | BIC always required |
| Initiating party and debtor name | Accepted and ignored; the debtor name comes from Danske's records |
| Creditor name | Up to 70 characters |
| Creditor address, Danske's order of preference | Structured; hybrid with up to 2 address lines; address lines only, up to 7 |
| Charge bearer | CRED, DEBT, SHAR or SLEV; SLEV and blank are read as SHAR |
| Unstructured remittance | One occurrence of 140 characters on SEPA |
| Denmark | ONCL standard transfer by default, SDCL same-day; INST for SEPA Instant |
| Norway, approvers | SOSE, NIDN or USER (District user ID) on the debtor; SOSE preferred; the first 5 approvers are validated |
| Regulatory reporting | Transfers abroad above SEK 150,000 from Sweden and NOK 100,000 from Norway |
Published by the bank
EDI Web Services v5.2, PKI Web Services v2.9, Danske Bank Root Certificate Verification for EDI Web Services, Danske Bank CA Certification Practice Statement v1.1.
Onboarding at Danske Bank
| Step | EDI Web Services |
|---|---|
| Agreement | District agreement with the EDI Web Services module |
| Signed by | The company signs the District agreement and a User Authorisation that gives the user access to EDI Web Services |
| Identifiers | Customer User ID: the lowest level of user under a District agreement, written into the certificates and sent as SenderId and CustomerId |
| Activation | Customer User ID and PIN code; the PIN works once and expires |
| PIN delivery | Not published |
| Bank certificates | Root DBGROOT downloaded from Danske as DBGROOT_1111110003.zip, signed by Danske Bank A/S and checked with jarsigner; GetBankCertificate then returns Danske's encryption and signing certificates |
| Your certificates | Two 2048-bit RSA key pairs, one for signing and one for encryption; two PKCS#10 requests sent with CreateCertificate, carrying the PIN and encrypted to Danske's encryption certificate. Danske returns both certificates and its issuing CA certificate |
| Key source | Software or HSM, declared in the request; Danske recommends an HSM |
| Validity and renewal | Two years or less; renewed before expiry with RenewCertificate, signed with the current signing certificate, with no PIN |
| Revocation | Signing and encryption certificates are revoked as a pair, through RevokeCertificate or the customer centre |
| Revocation list for Danske's own certificates | Issued every 24 hours, valid for 48 hours |
| Through a service bureau | Its certificate can sign for your Customer User ID when it is allowed to handle payments for you |
| Onboarding time | Not published |
BankConnector
Questions
- Does Danske Bank EDI Web Services use certificates?
- Yes, two: one for signing and one for encryption. They are issued through Danske's PKI Web Services against your Customer User ID and a one-time PIN code. Your keys are 2048-bit RSA, the certificates last two years or less, and RenewCertificate replaces them before expiry without a new PIN.
- What agreement does Danske EDI Web Services need?
- A District agreement with the EDI Web Services module. The company also signs a User Authorisation that gives the user access to EDI Web Services. The Customer User ID belongs to that District agreement and is written into the certificates.
- Which pain.001 versions does Danske Bank accept?
- EDI Web Services takes pain.001.001.03 and, since version 5.2 of 8 October 2026, pain.001.001.09. Status reports come back as pain.002.001.03 or pain.002.001.10. The current MIG for pain.001.001.03 is version 3.6 of 10 July 2026.
- Which countries does one Danske Bank connection cover?
- Danske's MIG lists debtor-agent BICs for Denmark (DABADKKK), Norway (DABANO22), Sweden (DABASESX), Finland (DABAFIHH), the London branch (DABAGB2L), Northern Bank in Northern Ireland (DABAGB2B), Ireland (DABAIE2D) and Poland (DABAPLPW). Its MIG comments apply to every country the Danske Bank Group operates in.
- How does Danske Bank deliver intraday reports?
- As camt.052.001.02, a real-time file Danske generates each time it is downloaded. Subtype BAL carries balances and ACC carries the postings since the last camt.052.
- Does Danske Bank accept camt.055 payment cancellations?
- Yes. camt.055.001.01 cancels payments sent as pain.001.001.02 or pain.001.001.03, and SEPA direct debits sent to Collection Service. Danske answers a payment cancellation with camt.029.001.03.
Published by the bank
Dates the bank has announced. What we do about each one is ours.
Upcoming events in our register
Sweden: the execution date of salary payments sent in files changes.
Sweden: unstructured addresses are no longer supported in domestic ISO 20022 XML payments, and file traffic is routed through each bank instead of Bankgirot (Autogiro and Kontofråga excepted).
Poland: SORBNET3 moves to ISO 20022 and stops accepting unstructured postal addresses. Cross-border payments in PLA format are rejected.
Sweden: Bankgiro and Plusgiro payments finish their move to the new clearing, and Bg Max is phased out.
Poland: the KSeF e-invoice number becomes mandatory in payment details.
Denmark’s new payment infrastructure: beneficiary name mandatory for account transfers and salaries, short messages to beneficiaries discontinued, new character limits, and Extended Remittance Information available.
Poland: Elixir moves to ISO 20022 for domestic payments.
camt.052, camt.053 and camt.054 version 8 launch on Danske’s channels between 2027 and 2028. MT and camt version 2 statements stay supported, with changes announced at least 18 months ahead.
Danske’s root certificate DBGROOT expires: serial 1111110003, valid from 9 June 2018.
If all of this looks like a lot, it does not have to be
Five steps to a live Danske Bank connection.
You do not need to know what any of the codes above mean. Our setup guide walks you through it one screen at a time.
- 1
Request the agreement from Danske Bank
A bank web service starts with an agreement, which you sign with your bank. There is nothing to configure until it is in place.
- 2
Enter your activation credentials
Your user ID and activation code come from Danske Bank, partly with the signed agreement and partly sent to you separately. The setup form asks for each of them.
- 3
Enrol your certificates
We generate your keys, send Danske Bank the certificate requests, authenticated with the activation code, and store the certificates the bank issues. Your private keys stay in BankConnector.
- 4
Verify Danske Bank's signatures
We check the certificates you are issued against the bank's root certificate, and the signature on every reply the bank sends. A reply whose signature fails is refused before it reaches your books.
- 5
Go live with one small payment
Choose who approves payments and switch the connection on. Start with one small payment and follow it all the way to your statement. Payments go out as pain.001; status and statements come back as pain.002 and camt. We alert you 30, 14 and 7 days before a certificate expires.
Sources: Danske Bank’s EDI Web Services v5.2, PKI Web Services v2.9, Root Certificate Verification for EDI Web Services, the Danske Bank CA Certification Practice Statement v1.1, its ISO 20022 XML documents (pain.001.001.03 MIG v3.6, Appendix v5.3), the Channels and Security and Upcoming Changes pages, the legal footers of its country sites and its London branch page. BankConnector is not affiliated with Danske Bank A/S.