Reference:
Q:
How to determine if the product is Personal or Business one?
We need this information to determine whether the account is Personal or Business.
A:
We have separate endpoints for Personal and Business segments. This allows you to access product-specific details tailored to each segment by invoking the respective endpoints.
Q:
What could be the reason of the following error ("code": "error.validation", "description": "Invalid V4 Account-id", "path": "id")?
{"group_header": {"message_identification": "2b1f3d711527165e","creation_date_time": "2024-11-21T08:50:11.635235805Z","http_code": 400},"error": {"request": {"url": "/v5/accounts/id-v4-to-v5/FINOQqJXir{redacted}nEwMl4DyAztU"},"failures": [{"code": "error.validation","description": "Invalid V4 Account-id","path": "id"}
A:
Please see: Invalid V4 Account-id error (Personal Accounts API)
Q:
Do you expose children accounts via PSD2 APIs? If yes, is it possible to identify them as children accounts?
A:
Please see: Children accounts (Accounts API) FAQ
Q:
Is a credit limit included in balances provided by Nordea?
A:
The available balance includes the credit limit.
Q:
When a PSU (Payment Service User) initiates an AIS consent, are all of their accounts always visible and selectable, or can certain accounts be hidden from the selection screen or the GET /accounts endpoint?
A:
The account consent can be limited to particular account via providing them in account_list while obtaining the consent (v5/authorize or v5/decoupled/authorizations)
Q:
Does the account_name parameter equal account holder's name?
A:
Yes, the account_name parameter corresponds to the account holder's name.
Q:
How reliable is the account_name field? Is there any way for users to modify the account_name field within their own client accounts?
A:
Users cannot modify the account_name field within their own client accounts.
Q:
In certain scenarios, we receive account_name values as a single string, which contradicts our understanding that this field should contain both Firstname and Lastname. Is this variation expected?
A:
You can expect that personal accounts endpoints will return the account_name as a single string value.
Q:
Is it possible to identify shared accounts through your PSD2 APIs in Sweden?
A:
Shared co-owner account identification is currently part of our long-term roadmap (we cannot provide a timeline yet).
Note: In the case of multiple co-owners, we currently share the name of the PSU who has given consent.
Q:
Regarding the account types, what are the possible values for the product field (e.g., "PERSONKONTO", "SPARKONTO") and the account_type field (e.g., "Current", "Savings")?
A:
Product: Product name of the account.
Account_type: Returns only "Current" or "Savings".
Q:
If a user has 20 accounts, will a single request to:
return all accounts, or will the response be paginated requiring multiple requests?
A:
The maximum number of accounts returned per request is 50.
Q:
For:
you mention the following in your documentation:
Does this mean that these fields can now return empty responses?
A:
Yes, given that these fields are now optional parameters, the endpoints can return responses without populating these values.
Q:
What could be the reason for the missing booking_date parameter of the following transactions?
response body: {\"group_header\":{\"message_identification\":\"22a59943816a1681\",\"creation_date_time\":\"2025-11-03T04:36:35.970676671Z\",\"message_pagination\":{\"continuation_key\":\"CSC20251103:21***9.030001\"},\"http_code\":200},\"response\":{\"transactions\":[
...
{\"currency\":\"DKK\",\"status\":\"reserved\",\"transaction_date\":\"2025-11-02\",\"amount\":\"-372.81\"}, \"currency\":\"DKK\",\"status\":\"reserved\",\"transaction_date\":\"2025-11-02\",\"amount\":\"-169.0\"}],\"account_number\":{\"value\":\"26***9935\",\"_type\":\"BBAN_DK\"},\"_links\":[{\"rel\":\"self\",\"href\":\"/v5/accounts/DKxjOJs***_G6TU33AjZU/transactions?from_date=2025-10-03&to_date=2025-11-03\"},{\"rel\":\"next\",\"href\":\"/v5/accounts/DKxjOJs***_G6TU33AjZU/transactions?from_date=2025-10-03&to_date=2025-11-03&continuation_key=CSC20251103:21***9.030001\"}]}}
A:
Transactions might not yet be executed and therefore not booked, so they do not have a booking date.
Q:
In Finland, we want to identify fees and taxes from transactions. We see that tax transactions have the type_description "Korkotulon lähdevero." Should this designation apply to all taxes? What about fees? What values does the type_description have for fees and taxes in Denmark, Sweden, and Norway?
A:
Open Banking does not control the type descriptions for transaction fees and taxes. Values in the type_description field can differ depending on the country and transaction scenario. Fee and tax transactions have type_descriptions based on the transaction type, with values varying by country and set by country-specific local systems. Across different countries, example description texts include deposit fees, withdrawal fees, overdraft fees, etc.
Q:
When requesting:
GET personal/v5/accounts/{id}/transactions
in the sandbox, the field "currency_conversion_fee_currency" returns the value "currencyConversionFeeCurrency". This occurs only on transactions involving currency conversion. Could this field return a valid currency instead?
GET https://api.nordeaopenbanking.com/personal/v5/accounts/DKEgActRn33uO3NUcWMet_M3HePq45AqiSK1YgN69p5G4/transactions
Authorization=Bearer eyJjdHkiOiJ***-UXcx15YEQg
Content-Type=application/json
X-Nordea-Originating-User-Ip=1***1
"X-Nordea-Originating-Date=Tue, 10 Feb 2026 11:16:18 GMT"
X-Nordea-Originating-Host=api.nordeaopenbanking.com
bank-id=Tm9yZG***tLSw==
X-IBM-Client-Id=a4191***8700
X-IBM-Client-Secret=9535***afd9
x-tpp-id=c37144ea-***-b2b96bf8e0ac
x-correlation-id=c63a949d-***-48ad2280428d
Response:
{
"group_header" : {
"message_identification" : "c3fdaf0e8233267f0735c2d556e9cb35",
"creation_date_time" : "2026-02-10T11:22:49.334598437Z",
"message_pagination" : {
"continuation_key" : "sandboxContinuationKey-2"
},
"http_code" : 200
},
"response" : {
"transactions" : [ {
"transaction_id" : "6fccdb5a-90e3-4ee6-b39c-52d05df678ce",
"currency" : "DKK",
"booking_date" : "2026-02-10",
"value_date" : "2026-02-10",
"type_description" : "NORDEA PAY KØB",
"narrative" : "Nordea pay køb, . Sheraton: No Reference 1570018411497333",
"status" : "billed",
"counterparty_account" : "0",
"counterparty_name" : "Sheraton",
"transaction_date" : "2026-02-10",
"card_number" : "4026 *** 1180",
"payment_date" : "2026-02-10",
"original_currency" : "DKK",
"amount" : "-780.30",
"currency_conversion_fee_currency" : "currencyConversionFeeCurrency",
"exchange_rate" : "7.4",
"currency_conversion_fee" : "1.48",
"foreign_bank_fee" : "1.23",
"received_currency" : "NOK"
}
A:
As no currency conversion occurs in the sandbox, a dummy fixed value for "currency_conversion_fee_currency" is returned in the API response.
Q:
What are the possible values for the transaction_type parameter?
A:
These values vary depending on multiple factors, including account ledgers, and therefore we cannot supply a definitive list.
Q:
Our organisation implements direct integration with Nordea through PSD2 AIS APIs and requires clarification regarding agreement relationships with user profiles and account access. Consider this scenario: when parents possess access to multiple profiles, including personal accounts and children's accounts, do these constitute separate agreements? Does account connection across multiple profiles necessitate individual authentication processes for each agreement? Does the sandbox environment support multi-agreement scenario testing, or does this functionality exist exclusively in production environments?
A:
Please refer to: Access Authorization: FAQ