Bank integration · DNB
How to connect your ERP or system to DNB.
DNB offers a PGP-encrypted SFTP connection with SSH authentication. That sounds complicated. It really is not with BankConnector. Even though they can set your "Divisjon" in "TestModus" as they call it, you actually do not need to. You can move straight to production, which makes DNB's SFTP connection one of the easiest to use.
DNB connectivity profile
Formats, markets, setup.
Connectivity
PGP-encrypted SFTP, straight to production.
DNB runs on a PGP-encrypted, SSH-authenticated SFTP connection. The setup is straightforward: sign the agreement, exchange keys, and you are live. DNB offers a "TestModus" where they can set your Divisjon, but you do not need it. You can skip straight to production, making this one of the simplest SFTP connections in the world.
All Norwegian payments
All Norwegian payment types are supported, including KID (Kundeidentifikasjon) for invoice-based collections. Domestic, SEPA and international transfers flow through the same connection.
Scandinavian coverage
DNB operates in Scandinavia, the UK and the US. Data quality is strongest in their core Scandinavian markets.
No test environment required
Unlike most banks, DNB lets you go straight to production. No waiting for test cycles. No mandatory sandbox. Just sign, exchange keys, and start sending payments.
Why integration quality matters
Anyone can drop a file on an SFTP server. Doing it properly is the hard part.
There are a lot of shortcuts vendors take to get a green checkmark in a demo. Skip the PGP encryption. Use password authentication. Fire-and-forget the upload. Call it integrated. It works right up until the day it quietly does not, and with payments, quietly does not means real money in the wrong place.
We do not build it that way. If you care about security and usability the way we do, you do the unglamorous work:
Verify bank signatures
Every response and statement file from DNB is cryptographically verified before we trust a single byte of it. If a file fails PGP verification, it does not enter your reconciliation.
Encrypt every payload with PGP
Outbound payment files are PGP-encrypted per the DNB spec, with keys that are encrypted at rest and never logged. Your encryption material is treated like the crown jewels, because it is.
Authenticate with SSH, not passwords
The SFTP connection uses SSH key authentication. No shared secrets over the wire, no password rotation headaches. Just cryptographically strong identity verification on every connection.
Handle duplicates, every time
Network blips, retries, and double-clicks happen. We use end-to-end identifiers and idempotency checks so a payment is submitted once. A resend never becomes a second debit.
Reconcile status, do not assume it
We do not mark a payment done because the SFTP upload succeeded. We read DNB's pain.002 acknowledgements and camt statements back, match them to what we sent, and tell you the real state: accepted, rejected, or pending, with the reason.
Fail loudly and recover gracefully
Rejections surface with the bank's actual reason code, not a generic error. Retries are deliberate and bounded. Nothing important fails in silence.
The lazy version of this integration is faster to ship. Ours is the one you actually want sitting between your ERP and your bank account.
How a DNB integration goes live
From agreement to first reconciled payment.
- 1. Signed agreement. You sign the host-to-host agreement with DNB, listing the accounts and services.
- 2. Key exchange. PGP keys and SSH credentials are exchanged securely between DNB and BankConnector.
- 3. Production. You are live. No mandatory TestModus. No long test cycles. Just a fairly easy onboarding process and you are sending payments.Wait?? Legacy Bank Integrators really charges thousands for this process?
Things teams ask about DNB
Common questions.
What do I need to set up DNB SFTP?
A host-to-host agreement with DNB, PGP key exchange and SSH authentication setup. BankConnector guides you through every step with clear instructions.
Which markets does DNB cover?
DNB is present in Scandinavia, the UK and the US. Data quality is best in their core Scandinavian markets.
Does DNB support ISO 20022?
Yes. DNB supports pain.001, pain.002, camt.053 and camt.054. All Norwegian payment types including KID. BankConnector normalises them into one JSON shape your product can consume.
What is RGB and how does it work with DNB?
RGB (regnskabsgodkjente betalinger) is the Norwegian AML requirement to verify approver identity for external payments. Most Norwegian banks accept a Personummer in the payment file. DNB uses a webservice ASIC Container for asynchronous approver identity submission. BankConnector has perfected this integration, so approver identity is submitted automatically.
How long does onboarding take?
A fairly easy process. Once the agreement is signed and keys are exchanged, you can go straight to production without mandatory test cycles.
Do I need to use DNB TestModus?
No. DNB offers a TestModus where they can set your Divisjon, but it is optional. You can skip straight to production, which is why DNB's SFTP connection is one of the easiest to use in the world.
Ready to connect your DNB accounts?
Talk to us about your Norwegian payments and approval workflows. We will tell you exactly what DNB needs you to sign and how soon you can be live.