Nordea Open Banking API

Name: Nordea Open Banking API
Brand: Nordea Open Banking API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceBankingoauth27 EndpointsREST

For Agents

Read Nordea bank accounts, transactions, and balances, and initiate SEPA or domestic payments on behalf of consented Nordea customers under PSD2.

Install Jentic One Beta

Connect the Nordea Open Banking API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Nordea Open Banking 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 Nordea Open Banking API.

List Nordea accounts a customer has consented to share

Read full account details including IBAN, currency, and product type

Pull historical transactions for a Nordea account within a date range

GET STARTED

Start building with Nordea Open Banking API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Nordea Open Banking API, keeping it validated and agent-ready. Nordea Open Banking provides PSD2-compliant access to Nordea customer accounts across the Nordics, exposing account information services (AIS), payment initiation services (PIS) for SEPA and domestic transfers, and confirmation of funds for issuers. The API surfaces account listings, balances, transactions, and payment status under OAuth 2.0 with strong customer authentication. Licensed third-party providers, fintechs, and treasury platforms use it to read accounts and initiate payments on customer mandate.

Use Cases

Patterns agents use Nordea Open Banking API for, with concrete tasks.

★ Consumer account aggregation

Personal finance apps aggregating customer bank accounts use the AIS endpoints to list a Nordea customer's accounts and pull balances and transactions for budgeting categorisation. After PSD2 consent, /accounts and /accounts/{accountId}/transactions return the data the app needs to display the customer's full Nordea position alongside other banks. Transaction polling stays within PSD2's four-call-per-day unattended limit by caching responses.

Call /accounts to list consented accounts, then /accounts/{accountId}/transactions for each to build a 30-day transaction history

B2B SEPA payment initiation

Treasury platforms initiating supplier payments on behalf of corporate Nordea customers use POST /payments/sepa to push a SEPA credit transfer. After strong customer authentication, the API returns a payment ID that the platform polls via /payments/{paymentId} until status reaches accepted or rejected. This replaces file-based bulk payment imports with real-time API initiation.

POST /payments/sepa with the supplier IBAN, amount EUR 1200, and reference 'Invoice 4521', then poll /payments/{paymentId} until status is accepted

Confirmation of funds for card issuers

Card issuers needing to confirm available funds before authorising a debit-style transaction call POST /confirmation-of-funds with the account ID and amount. The endpoint returns yes/no without disclosing the actual balance, satisfying PSD2's CBPII flow. This is the prerequisite for issuing payment instruments that draw on a Nordea account.

POST /confirmation-of-funds with accountId and amount=EUR 75 to verify funds availability before authorising a card transaction

AI agent for personal finance

An AI personal finance assistant can answer 'what did I spend last month at the grocery store' by pulling the user's Nordea transactions through Jentic, filtering by merchant category, and summarising. Jentic hides the OAuth 2.0 token refresh and PSD2 consent mechanics from the agent, so the operation is just a search-load-execute call.

Through Jentic, search 'list Nordea transactions', load /accounts/{accountId}/transactions, and execute with the consented account ID and last-30-days range

Key Endpoints

7 endpoints — jentic publishes the only available openapi specification for nordea open banking api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/accounts

List consented Nordea accounts

GET

/accounts/{accountId}

Get account details for a consented account

GET

/accounts/{accountId}/transactions

List transactions on a Nordea account

POST

/payments/sepa

Initiate a SEPA credit transfer

POST

/payments/domestic

Initiate a domestic Nordic payment

GET

/payments/{paymentId}

Read payment status

POST

/confirmation-of-funds

Confirm fund availability without disclosing balance

GET

/accounts

List consented Nordea accounts

GET

/accounts/{accountId}

Get account details for a consented account

GET

/accounts/{accountId}/transactions

List transactions on a Nordea account

POST

/payments/sepa

Initiate a SEPA credit transfer

POST

/payments/domestic

Initiate a domestic Nordic payment

Why Jentic?

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

Credential isolation

Nordea OAuth 2.0 access tokens and refresh tokens are stored encrypted in the Jentic vault. Agents receive scoped access; raw tokens never appear in the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'initiate a SEPA payment') and Jentic returns the matching Nordea operation with its input schema, so the agent posts to /payments/sepa without reading PSD2 docs.

Time to first call

Direct Nordea integration: 1-2 weeks for TPP registration, OAuth flow, SCA handling, and PSD2 compliance plumbing. Through Jentic: under a day once consent is captured — search, load schema, execute.

FAQs

Specific to using Nordea Open Banking API through Jentic.

Why is there no official OpenAPI spec for Nordea Open Banking API?

Nordea Open Banking does not publish a single canonical OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Nordea Open Banking API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Nordea Open Banking API use?

Nordea Open Banking uses OAuth 2.0 with strong customer authentication under PSD2. You register as a TPP, redirect the customer through SCA to obtain a consent and access token, then call account or payment endpoints with the token. Through Jentic, refresh and rotation are handled by the runtime.

Can I initiate a SEPA payment with the Nordea Open Banking API?

Yes. POST /payments/sepa with the debtor account, creditor IBAN, amount, and reference. The response returns a payment ID; poll GET /payments/{paymentId} to track progress through to accepted, rejected, or settled.

What are the rate limits for the Nordea Open Banking API?

Under PSD2, Nordea allows up to four unattended AIS calls per consented account per day plus on-demand calls when the customer is present. Payment initiation does not have the same per-account daily cap but is bound by SCA. Cache transaction responses to stay within the unattended budget.

How do I read a customer's Nordea transactions through Jentic?

Install with pip install jentic, then search 'list Nordea transactions', load GET /accounts/{accountId}/transactions, and execute. The customer must have completed PSD2 consent before the call; Jentic stores the access token in the encrypted vault.

Does the Nordea Open Banking API support corporate accounts?

Yes. The same /accounts and /payments endpoints apply to corporate Nordea accounts, with consent flows that route through the corporate signatory rather than a single individual. Check Nordea's developer portal for the corporate consent UI specifics.

Nordea Open Banking API

Connect the Nordea Open Banking API to your agent

Capabilities

Start building with Nordea Open Banking API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs