SEB Luxembourg API Access & Open Banking

Reaching your SEB (Luxembourg) accounts programmatically usually means chasing PSD2 certificates and standing up your own connection layer. open-banking.io removes that overhead. It links to SEB through regulated open-banking rails, then hands you clean account and transaction data — with one important difference: everything is decrypted on your own device with a key only you hold. The servers never see your figures in the clear.

SEB S.A. in Luxembourg (BIC ESSELULL) is part of the Nordic SEB group and serves both business and personal account holders. A single consent stays valid for up to 180 days before you re-approve, so day-to-day syncing keeps running without repeated logins.

How to connect SEB

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

  1. Sign up for an open-banking.io account.
  2. Set your encryption passphrase. Your keys are generated locally on your device, so open-banking.io only ever holds your public key.
  3. In the dashboard, search for SEB (Luxembourg) and choose whether you're linking a business or personal account.
  4. You're redirected to SEB's own secure login, where you approve access directly on the bank's PSD2 consent screen.
  5. Your accounts flow back into the dashboard and begin syncing automatically.

Because approval takes place on SEB's own systems, your banking credentials are never entered on or seen by open-banking.io.

Access your data

Once SEB is connected, reading the data in code is an optional developer step. 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 directly.

Every request carries the X-Api-Key header, and every response is decrypted locally with your own key. The key alone, on the server side, only ever returns ciphertext — proof that the zero-knowledge design holds even for your own API traffic. Note there is no connect command: the CLI and SDK only read and sync connections you already made in the dashboard.

No eIDAS certificates, no bank-specific onboarding, no infrastructure to maintain — just around EUR 3/month across 2,600+ supported banks.

FAQ

Do I need a PSD2 certificate to access SEB?

No. open-banking.io handles the regulated connection. You approve access on SEB's consent screen and never touch a certificate.

Can open-banking.io read my SEB data?

No. It is zero-knowledge and stores only your public key. Your data is decrypted locally with a private key that never leaves your device.

Up to 180 days per approval, after which you simply re-confirm access on SEB's login to keep syncing.