SEB Latvia Open Banking API Access for Developers

Reaching your SEB (Latvia) accounts programmatically usually means wrangling PSD2 certificates, sandbox registrations and eIDAS paperwork. open-banking.io removes all of that. It is a zero-knowledge bridge to 2,600+ European banks where the data leaving SEB is encrypted against a key generated on your own device — so only you can ever read it. No QWAC certificate, no bank onboarding forms, and no server that can see your balances.

SEB is one of the Baltics' largest banks (BIC UNLALV2X), and open-banking.io supports both personal and business accounts held there. A single consent stays valid for up to 180 days before SEB asks you to re-approve, so you are not re-authenticating every week.

How to connect SEB

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

  1. Sign up at open-banking.io and set an encryption passphrase. Your encryption keys are generated locally, on your device, and the passphrase never leaves it.
  2. In the dashboard, choose SEB (Latvia) and pick the account type you want to link — personal or business.
  3. You are redirected to SEB's own secure login, where you approve the access request directly on the bank's PSD2 consent screen.
  4. Once SEB confirms, your accounts sync back into your dashboard, already encrypted with your key.

That is the whole flow: authorise on SEB's side, and the data appears in your dashboard.

Access your data

Want the data in your own code? This step is optional and comes after the account is connected. On the Developers page, create an API key and export a credentials.json — it bundles the API key together with your private decryption key.

From there, use the CLI or an SDK:

openbanking accounts
openbanking transactions
openbanking sync

The CLI, SDKs and REST API only ever read and sync connections that already exist — there is no connect command. Requests authenticate with the X-Api-Key header, and each response is decrypted locally with your private key. The API key alone returns nothing but ciphertext; without your key, open-banking.io's servers (which hold only your public key) cannot read a thing.

All of this runs for around EUR 3/month.

FAQ

Does open-banking.io need a PSD2 certificate for SEB?

No. It is certificate-free. You approve access on SEB's own consent screen — no eIDAS or QWAC setup required.

Can the CLI connect my SEB account?

No. Connecting is done once in the dashboard on SEB's login page. The CLI and SDKs only read and sync existing connections.

Can open-banking.io read my SEB balances?

No. Data is decrypted only on your device with a key you alone hold. The service is genuinely zero-knowledge.

Start at open-banking.io.