Connect your ERP to DNB.
DNB File Gateway, SFTP signed in with an SSH key and secured with PGP. Payments go out as pain.001.001.03; status and statements come back as pain.002, camt.053 and camt.054.
The bank
- Legal name
- DNB Bank ASA
- Head office
- Oslo, Norway
- Org. no.
- 984 851 006
- Supervisor
- Finanstilsynet
- Channel
- DNB File Gateway (SFTP)
- Payments
- pain.001.001.03
Published by the bank
The Brønnøysund Register Centre's entry for DNB Bank ASA, Finanstilsynet's register of its branches, and the debtor-agent BICs in DNB's pain.001.001.03 examples workbook v1.7.
Bank details
| Legal name | DNB Bank ASA |
| Business address | Dronning Eufemias gate 30, 0191 Oslo, Norway |
| Postal address | PO Box 1600 Sentrum, 0021 Oslo |
| Organisation number | 984 851 006 |
| Supervisor | Financial Supervisory Authority of Norway (Finanstilsynet) |
| Debtor agent BIC for accounts in Norway | DNBANOKK |
| Country | Entity | BIC | Register | Supervisor |
|---|---|---|---|---|
| Norway (head office) | DNB Bank ASA | DNBANOKK | Org. no. 984 851 006, Brønnøysund Register Centre | Finanstilsynet |
| Sweden | DNB Bank ASA, filial i Sverige | DNBASESX | Not published | Finanstilsynet |
| Denmark | DNB Bank ASA, filial i Danmark | DNBADKKX | Not published | Finanstilsynet |
| Finland | DNB Bank ASA, filial i Finland | DNBAFIHX | Not published | Finanstilsynet |
| Germany | DNB Bank ASA, filial i Tyskland | DNBADEHX | Not published | Finanstilsynet |
| United Kingdom | DNB Bank ASA, filial i Storbritannia | DNBAGB2L | Not published | Finanstilsynet |
DNB’s pain.001 examples also give DNBAUS33 as the debtor-agent BIC for accounts in the United States and Canada.
Published by the bank
DNB's SFTP channel set-up form (January 2026), Technical requirements Pre-approved payment files v1.4 (14 April 2021), Pre-approved Light RGB v0.1 (28 September 2025).
Channels
| Channel | DNB File Gateway (SFTP) |
| Protocol | SFTP; the client connects, pushes payment files and pulls reports |
| Transport | SSH to az.fgw.dnb.no, port 22 |
| Sign-in | SSH public key; the username is assigned by DNB |
| Content security | PGP: payment files signed with your key and encrypted to DNB's key; reports from DNB encrypted to your key |
| Keys | Your SSH and PGP public keys go to DNB; DNB sends its PGP public key |
| Agreement | Product agreements with DNB; every pain.001 is checked against the customer agreement |
| Countries | DNB accounts in Norway, Sweden, Denmark, Finland, Germany, the UK and the US |
| Other channels | SWIFT FileAct; DNB online bank, where files outside an auto-approved division wait for approval |
| Host | az.fgw.dnb.no |
| Port | 22 |
| Upload folder | Send |
| Download folder | PGPInbox: status reports and end-of-day statements, encrypted with your PGP key |
| Payment file name | P.<customer number>.<division number>.P001.<file type>.<your reference>; customer number always 11 digits, file type ignored |
| DNB's PGP key | DNB_MFT_PROD_PGP, RSA 4096, created 4 Dec 2024 |
| DNB's PGP key fingerprint | 05BB 5C80 3617 5D05 0D8A C01A 5FAC C278 6F66 B89F |
| Server host-key fingerprint | Not published |
| Pre-approved files, ASiC-E | pain.001 and an approval data file in an .asice container; a SHA-256 manifest signed (PKCS#7) with the private key of an enterprise certificate from a reputable issuer |
| Pre-approved files, Light RGB | The approvers travel inside the pain.001 under Dbtr/Id as SOSE or NIDN plus XARF; the file is PGP-signed and encrypted |
| Approval | Payments are approved in the ERP with a DNB-approved two-factor method; the ERP keeps a proof package DNB can request |
| On a failed approval | DNB rejects the whole file with a pain.002 |
| Statements and receipts | Unsigned, under the pre-approved ASiC-E solution |
BankConnector
Payment types and pain.001 version as built in our engine. BICs from DNB's pain.001.001.03 examples workbook v1.7.
Payment types by country
| Country | Debtor agent BIC | Channel | Payment types | pain.001 |
|---|---|---|---|---|
| Denmark | DNBADKKX | DNB File Gateway (SFTP) | SEPA credit transfer, Domestic account transfer, International payment, FIK payment | pain.001.001.03 |
| Finland | DNBAFIHX | DNB File Gateway (SFTP) | SEPA credit transfer, Domestic account transfer, International payment | pain.001.001.03 |
| United Kingdom | DNBAGB2L | DNB File Gateway (SFTP) | SEPA credit transfer, BACS, CHAPS, Faster Payment, International payment | pain.001.001.03 |
| Norway | DNBANOKK | DNB File Gateway (SFTP) | SEPA credit transfer, Domestic account transfer, International payment, KID payment | pain.001.001.03 |
| Sweden | DNBASESX | DNB File Gateway (SFTP) | SEPA credit transfer, Bankgiro, PlusGiro, Domestic account transfer, International payment | pain.001.001.03 |
Published by the bank
DNB's pain.001.001.03 MIG workbook v2.1 (change log to 18 April 2026) and MIG version 1.0 (September 2021), the camt.053.001.02 and camt.054.001.02 MIGs v2.0, the 2019 draft MIGs, Technical requirements Pre-approved payment files v1.4.
Formats DNB accepts
| Message | Version | Content | DNB guide |
|---|---|---|---|
| pain.001 | 001.03 | Payment orders for every DNB payment type; file code P001 | MIG workbook v2.1 and MIG version 1.0 |
| pain.001 | 001.09 | Payment orders | Draft MIG (2019) |
| pain.002 | 001.03 | Status reports; for pre-approved files also the ACP rejection codes | MIG v1.1; Pre-approved payment files v1.4 |
| pain.002 | 001.10 | Status reports | Draft MIG (2019) |
| camt.053 | 001.02 | Account statement | MIG v2.0 |
| camt.054 | 001.02 | Debit and credit notifications | MIG v2.0 |
| camt.055 | 001.01 | Payment cancellation request | MIG v1.0 |
| camt.029 | 001.03 | Answer to a cancellation request | MIG v1.0 |
| ASiC-E container | ETSI TS 102 918 | Pre-approved payment files: pain.001 plus approval data in one signed .asice file | Pre-approved payment files v1.4 |
| EDIFACT PAYMUL, DEBMUL, BANSTA, CONTRL | MIG v2 | Payments, debit advice, status and syntax reports | DnB NOR MIGs |
| Character set | UTF-8; empty elements are not allowed |
| Initiating party | Two OrgId/Othr entries: CUST, your DNB subscription number, and BANK, your division name in capitals |
| Agreement check | A wrong CUST number, or one with no agreement for the debit account, stops the file with no pain.002 |
| Division name | Up to 11 capital letters |
| Message ID | Unique per customer for at least 12 months |
| Duplicate control | A repeated MsgId, PmtInfId or InstrId from the same initiating party within one year is rejected: DU01, DU02, DU05 |
| Creation date | Older than 3 months or later than the day received rejects the file: DT02 |
| Debtor agent | BIC required; missing or invalid rejects the batch: RC06 |
| Debit accounts | Nordic and non-Nordic DNB accounts never in the same pain.001 |
| Batch booking | A request only; absent means false |
| Charge bearer | Default SHAR for domestic and SLEV for SEPA; cross-border DEBT, CRED, SHAR or SLEV; on one level only |
| Category purpose | TREA, SALA, PENS and INTC on the batch level only; proprietary MASS, MASG and PENN |
| Structured remittance | Norway up to 999 with credit notes; Sweden up to 525 positions; Denmark 1, no credit notes; Finland up to 9; SEPA 1 |
| Text on the payee's statement | Norway 27, Sweden 25, Denmark 20 characters |
| Salaries in Sweden | Execution date one day before the funds reach the employee |
| Swedish SEK batch clearing | MsgId, PmtInfId, InstrId, EndToEndId and remittance limited to letters, digits, space and / - ? : ( ) . , ' + |
| Cut-off times | Published on dnb.no |
Published by the bank
DNB's SFTP channel set-up form (January 2026), Technical requirements Pre-approved payment files v1.4, Pre-approved Light RGB v0.1, pain.001.001.03 MIG version 1.0.
Onboarding at DNB
| Agreement | Product agreements with DNB |
| Signed by | Not published |
| Identifiers | Customer (subscription) number, division number and division name; SFTP username from DNB |
| Divisions | Separate several systems or clients under one online banking subscription, so return files are not mixed |
| Key exchange | You send your SSH and PGP public keys; DNB returns the SFTP user, host, folders and its own PGP public key |
| Pre-approved payment files | The sending system must be approved by DNB; approvers and their rights are kept in step with DNB's authorisation database |
| BankID | Used at user enrolment, with re-authentication at least monthly, or at every approval |
| Approvers outside the Nordics | Set up in DNB's systems by its Technical Customer Implementation team |
| Technical support | Technical Customer Implementation team, tci@dnb.no |
| Your key validity | Not published |
| DNB's PGP key validity | Until 4 Dec 2027 |
| Onboarding time | Not published |
BankConnector
Questions
- How does a company connect to DNB by SFTP?
- Through DNB File Gateway at az.fgw.dnb.no, port 22. The company signs in with an SSH key under a username DNB assigns, uploads payment files to the Send folder and collects status reports and statements from PGPInbox. Files to DNB are signed with the company's PGP key and encrypted to DNB's.
- How are DNB payment files named?
- P.<customer number>.<division number>.P001.<file type>.<your reference>. The customer number is always 11 digits, P001 marks a pain.001, and DNB ignores the file type field.
- What is a division at DNB?
- A way to separate several systems or clients under one online banking subscription so their return files are not mixed. The division number goes in the file name; the division name, up to 11 capital letters, goes in the pain.001 under InitgPty with scheme code BANK.
- What are DNB pre-approved payment files?
- Files whose payments are already approved in the ERP with a DNB-approved two-factor method. DNB checks each approver against its own authorisation database and rejects the whole file if one fails. The approvals travel in a signed ASiC-E container, or under Light RGB inside the pain.001 itself.
- What changes in DNB payment files on 15 November 2026?
- Postal addresses must be structured or hybrid, with TwnNm and Ctry. A fully unstructured address is removed from a SEPA payment and rejects a cross-border one. A hybrid address carries at most two AdrLine of 35 characters.
- How long must a DNB message ID stay unique?
- At least 12 months per customer. DNB rejects a MsgId, PmtInfId or InstrId that the same initiating party repeats within one year, with codes DU01, DU02 and DU05.
Published by the bank
Dates the bank has announced. What we do about each one is ours.
Upcoming events in our register
Structured or hybrid addresses only in pain.001.001.03. Postal address optional for SEPA and mandatory for cross-border payments; TwnNm and Ctry mandatory; a fully unstructured address is removed on SEPA and rejected cross-border.
DNB’s production PGP key DNB_MFT_PROD_PGP expires: RSA 4096, created 4 December 2024.
If all of this looks like a lot, it does not have to be
Five steps to a live DNB 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 DNB
A host-to-host connection starts with an agreement, which you sign with your bank. There is nothing to configure until it is in place.
- 2
Send your public keys
We generate two key pairs for you: SSH, which signs you in to DNB's server, and PGP, for the files you and DNB exchange. You send DNB the public halves the way it asks for them. Your private keys stay in BankConnector.
- 3
DNB registers your keys
The bank sets up your user on its server and sends you the server address, your username and its own PGP public key. You enter them in the setup form, with any file-name values the bank assigned you.
- 4
Pin DNB's server
You enter the fingerprint of the bank's server key, as the bank gives it to you. We connect only to a server that presents that key, then list its folders, read-only, so you can pick the one that holds your statements.
- 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 your PGP key expires.
Sources: DNB’s Message Implementation Guidelines for pain.001.001.03 (MIG version 1.0, September 2021), its pain.001.001.03 MIG workbook v2.1 and examples workbook v1.7, the camt.053.001.02 and camt.054.001.02 MIGs v2.0, the draft pain.001.001.09 and pain.002.001.10 MIGs (2019), Technical requirements Pre-approved payment files v1.4 (14 April 2021), Pre-approved Light RGB v0.1 (28 September 2025), the SFTP channel set-up form DNB completed in January 2026, the Brønnøysund Register Centre, Finanstilsynet’s register of DNB’s branches in Sweden, Denmark, Finland, Germany and the United Kingdom, and DNB’s cut-off times. BankConnector is not affiliated with DNB Bank ASA.