Dnb No DNB PSD2 Payments API

Name: DNB PSD2 Payments API
Brand: DNB PSD2 Payments API
Availability: InStock

✓ Official Vendor SpecFinanceBankingoauth25 EndpointsREST

For Agents

List DNB bank accounts, fetch transactions, and initiate domestic Norwegian payments through PSD2-compliant Account Information and Payment Initiation Services. For licensed TPPs and personal-finance agents.

Install Jentic One Beta

Connect the DNB PSD2 Payments API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DNB PSD2 Payments API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with DNB PSD2 Payments API.

List the DNB accounts a customer has consented to share via GET /accounts

Retrieve a single account's details and balances via GET /accounts/{accountId}

Fetch transaction history for a consented account through /accounts/{accountId}/transactions

GET STARTED

Start building with DNB PSD2 Payments API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use DNB PSD2 Payments API for, with concrete tasks.

★ Personal Finance Dashboards over DNB Accounts

Norwegian fintech apps can show DNB account balances, recent transactions, and categorised spending by combining GET /accounts, GET /accounts/{accountId}, and the transactions endpoint. Users grant consent through DNB's PSD2 SCA flow once, after which the TPP can refresh data on the consent's lifetime. This delivers a Mint/Tink-style experience without scraping or screen-mirroring the DNB website.

List DNB accounts via GET /accounts, then GET /accounts/{accountId}/transactions for the last 90 days for each account and aggregate by merchant category.

Initiating Domestic Payments from a Customer's DNB Account

Licensed Payment Initiation Service Providers (PISPs) can let DNB customers pay merchants, friends, or themselves directly from their bank account, avoiding card-network fees. POST /payments/domestic accepts the debit account, creditor account, amount, and reference, and DNB handles authentication and settlement. Status is tracked via GET /payments/{paymentId} until the payment is finalised.

POST /payments/domestic with debit account, creditor account, NOK amount, and reference; then poll GET /payments/{paymentId} until status is 'ACSC' (settled).

Accountancy and Reconciliation Integrations

Bookkeeping platforms and treasury teams can pull DNB transactions directly into their ledgers via /accounts/{accountId}/transactions, removing manual CSV exports and the lag between bank statement and ledger. Categorisation rules can be applied client-side using transaction descriptions and counterparty IDs. Combined with PISP payments, businesses can also pay supplier invoices straight from their accounting tool.

Fetch the previous day's transactions for the DNB business account and post them into the accounting ledger as unreconciled entries, matched to invoices where reference IDs align.

AI Agent Banking Copilot for DNB Customers

An AI personal-finance agent can answer 'How much did I spend on groceries last month?' or 'Pay rent of NOK 12,000 to my landlord' by chaining DNB AIS and PIS operations through Jentic. OAuth2 client credentials and consent tokens stay in MAXsystem so the agent never holds bearer tokens directly, and the customer's SCA approval still happens at DNB.

Search Jentic for 'list DNB transactions', load the GET /accounts/{accountId}/transactions operation, and execute it with the consented account ID and date range to summarise spending by category.

Key Endpoints

5 endpoints — dnb is norway's largest bank, and its psd2 payments api exposes regulator-compliant access to dnb customers' bank accounts and payment initiation services.

METHOD

PATH

DESCRIPTION

GET

/accounts

List consented DNB accounts

GET

/accounts/{accountId}

Retrieve a specific account's details

GET

/accounts/{accountId}/transactions

Fetch transactions for an account

POST

/payments/domestic

Initiate a domestic Norwegian payment

GET

/payments/{paymentId}

Check payment status

GET

/accounts

List consented DNB accounts

GET

/accounts/{accountId}

Retrieve a specific account's details

GET

/accounts/{accountId}/transactions

Fetch transactions for an account

POST

/payments/domestic

Initiate a domestic Norwegian payment

GET

/payments/{paymentId}

Check payment status

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

DNB OAuth2 client credentials, eIDAS-derived material, and the customer's consent token are stored encrypted in Jentic's MAXsystem vault. Agents call AIS and PIS operations through scoped Jentic sessions; the raw bearer tokens never enter the agent's context. SCA still happens at DNB as required by PSD2.

Intent-based discovery

Agents search by intent (e.g., 'list DNB transactions' or 'initiate a domestic payment') and Jentic returns the matching DNB operation with its input schema, so the agent calls the right /accounts or /payments endpoint without browsing the developer portal.

Time to first call

Direct DNB integration: 4-8 weeks including PSD2 license verification, eIDAS certificate provisioning, OAuth2 + consent flow, and SCA redirect handling. Through Jentic: under 1 hour to call individual operations once licensed credentials are loaded into the vault.

FAQs

Specific to using DNB PSD2 Payments API through Jentic.

What authentication does the DNB PSD2 Payments API use?

DNB requires OAuth2 with PSD2 eIDAS QWAC and QSealC certificates and a consent token tied to the customer's Strong Customer Authentication (SCA). Only licensed TPPs registered with the Norwegian FSA (or passported from another EEA regulator) can call the API. Through Jentic, OAuth client credentials are held in the MAXsystem vault and injected at execution; the customer's SCA still happens at DNB.

Can I initiate a domestic Norwegian payment with the DNB API?

Yes, POST /payments/domestic accepts the debit account, creditor account, NOK amount, and a reference. The customer is redirected to DNB to authorise via SCA before the payment is executed. Status updates are available via GET /payments/{paymentId}.

What are the rate limits for the DNB PSD2 Payments API?

Rate limits follow PSD2 Regulatory Technical Standards: a maximum of four AIS calls per consented account per day without customer interaction, and per-TPP throttles set by DNB. Refer to DNB's developer portal for production thresholds and sandbox burst allowances.

How do I retrieve a customer's DNB transactions through Jentic?

Search Jentic for 'list DNB transactions', load the schema for GET /accounts/{accountId}/transactions, and execute it with the consented accountId and a date range. Jentic returns the transaction list including counterparty, amount, and booking date.

Is the DNB PSD2 Payments API free?

DNB does not charge for AIS and PIS calls under PSD2 obligations, but TPPs must hold a PSD2 license and the required eIDAS certificates. Costs come from the certificates and the licensing/audit overhead, not from per-call fees.

Can I list a customer's DNB accounts before initiating a payment?

Yes, after the customer grants AIS consent, GET /accounts returns the accounts in scope. Use that list to confirm the debit account before constructing a POST /payments/domestic request.