SEB Norway API Access & Open Banking Connection

Reaching your SEB (Norway) accounts programmatically usually means chasing eIDAS certificates, sandbox onboarding and PSD2 paperwork. open-banking.io removes all of that. It is a zero-knowledge, certificate-free bridge to 2,600+ EU and UK banks, and SEB (BIC ESSENO22) is one of them. You link the account once in a browser, and every byte that flows back is decrypted on your own machine with a key that never leaves it.

SEB in Norway supports both business and personal accounts, and a single approval keeps your access live for up to 180 days before you re-consent.

How to connect SEB

Connecting happens entirely inside the open-banking.io dashboard — there is no API call, code snippet or key involved in this step.

  1. Sign up for open-banking.io and set an encryption passphrase. Your key pair is generated locally on your device; open-banking.io only ever sees your public key.
  2. In the dashboard, pick SEB (Norway) from the bank list and choose whether you are linking a business or personal account.
  3. You are redirected to SEB's own secure login, where you approve access under PSD2 — your credentials go straight to the bank, never through us.
  4. Once SEB confirms consent, your accounts and transactions sync into the dashboard automatically.

That is the whole flow: a bank-hosted approval, nothing self-hosted, no sandbox registration.

Access your data

Developers can optionally read the connected data in code — a step that only exists after the link above is live. On the Developers page, create an API key and export a credentials.json, which bundles that key together with your private decryption key. From there use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API directly.

Every request carries your key in the X-Api-Key header. The API key alone only returns ciphertext; each response is decrypted locally with your private key, so open-banking.io's servers can never read your SEB data. Note there is no connect command — the CLI and SDK only read and refresh connections you already established in the dashboard.

All of this runs for roughly EUR 3/month, with no per-bank certificate or enterprise contract.

FAQ

Do I need an eIDAS certificate for SEB?

No. open-banking.io is certificate-free — the dashboard connection and SEB's PSD2 consent screen cover authorisation entirely.

Can open-banking.io read my SEB balances?

No. It holds only your public key. Data is encrypted for you and decrypted on your device, so the service stays zero-knowledge.

Up to 180 days. After that you simply re-approve access on SEB's login screen from the dashboard.

Ready to start? Visit open-banking.io.