SEB Denmark API Access & Open Banking Integration

Reaching your SEB (Denmark) account data no longer means wrestling with eIDAS certificates or a PSD2 sandbox. open-banking.io gives you a single dashboard for SEB alongside 2,600+ other EU and UK institutions, and it does so with a zero-knowledge design: your account data is decrypted locally with an encryption key that only you hold. SEB's Danish operation (part of Skandinaviska Enskilda Banken) covers both business and personal customers, and both account types are supported here. There is no published BIC for this connection, so selection happens by name inside the dashboard rather than by identifier.

How to connect SEB

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

  1. Sign up for open-banking.io and set your encryption passphrase. Your keys are generated on your own device, so no one else can read your data.
  2. In the dashboard, pick SEB (Denmark) and choose the account type you need — business or personal.
  3. You are redirected to SEB's own secure login, where you approve access under PSD2. Your credentials are never seen by open-banking.io.
  4. Your accounts sync back into the dashboard. Consent lasts up to 180 days, after which you simply re-approve on SEB's screen.

Access your data

Programmatic access is an optional step for developers, and only after SEB is already connected. On the Developers page, create an API key and export a credentials.json — this bundles the API key together with your private decryption key. From there you can use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API. Requests authenticate with the X-Api-Key header, and every response is decrypted locally with your own key. Without that private key an API key alone returns only ciphertext — the servers hold nothing but your public key.

Is there a SEB API key to connect the account?

No. Connecting SEB happens in the dashboard via SEB's own consent screen. API keys only read data you have already linked.

How long does SEB access stay active?

Up to 180 days per consent. When it expires, re-approve access on SEB's login page from the dashboard.

Can open-banking.io read my SEB transactions?

No. It is zero-knowledge and certificate-free; decryption happens on your device with a key only you control.

Get started at open-banking.io for around EUR 3/month.