canonical: https://jentic.com/apis/nordeaopenbanking.com/nordea-open-banking

# Nordea Open Banking API

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.

## For AI agents

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

## Scope

Does not handle card issuing, FX hedging, or non-Nordea bank accounts - use for Nordea PSD2 account information and payment initiation only.

## Capabilities

- 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
- Initiate a SEPA credit transfer from a customer's Nordea account
- Initiate a domestic Nordic payment between Nordea accounts
- Check payment status by payment ID after initiation
- Confirm availability of funds on an account before initiating a charge

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

| 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 |

## Key resources

- **Account Information** — List accounts, read account details, and pull transactions under PSD2 AIS
- **Payments** — Initiate SEPA and domestic payments and read payment status
- **Confirmation of Funds** — PSD2 CBPII endpoint to confirm fund availability without disclosing balance

## Why Jentic

- **Setup:** Wiring Nordea Open Banking by hand means running its OAuth 2.0 authorization-code flow, refreshing tokens against api.nordeaopenbanking.com/v3, and satisfying PSD2 rules on every account and payment call yourself. Through Jentic you install once, import the Nordea Open Banking API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Nordea puts the account id in the URL path (`/accounts/{accountId}/...`), so a rule can pin your agent to one account for reads. You choose the operations it may call, so payment initiation such as POST `/payments/sepa` or POST `/payments/domestic` is not included unless you add it.
- **Credential handling:** Your Nordea OAuth access and refresh tokens are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'initiate a SEPA payment' or 'list account transactions', and Jentic returns the matching Nordea operation with its input schema so the agent posts to `/payments/sepa` without browsing the PSD2 docs.

## Related APIs

- **Nordigen Account Information Services API** — Nordigen aggregates PSD2 access across hundreds of European banks including Nordea.
- **TrueLayer API** — TrueLayer is a UK-based PSD2 aggregator covering Nordea and other EU banks.
- **Plaid API** — Plaid covers North American banks plus a growing European footprint.
- **Salt Edge API** — Salt Edge aggregates banks across 50-plus countries including Nordea.

## FAQ

### 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 with Jentic One, the self-hosted execution layer.

### 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.

### Can I limit what my agent is allowed to do with the Nordea Open Banking API?

Yes. Because you run Jentic One yourself, your own rules decide which Nordea operations and credentials the agent may use. You pick the operations it can call, so read-only access to GET /accounts, GET `/accounts/{accountId}`, and GET `/accounts/{accountId}/transactions` can be allowed while payment initiation like POST `/payments/sepa` or POST `/payments/domestic` stays excluded until you add it. Since Nordea puts the account id in the URL path, a rule can also pin the agent to a single consented account for reads.