SEB (Lithuania) API Access via open-banking.io

Reaching SEB bankas account data in Lithuania usually means wrestling with PSD2 sandboxes, eIDAS certificates and licensing paperwork. open-banking.io removes that barrier. It links your SEB (Lithuania) accounts (BIC CBVILT2X) into a single dashboard and, when you want it, exposes them through a clean read API — no certificates, no bank onboarding, and no servers that can ever see your data. Both business and personal SEB accounts are supported, and a single consent stays valid for up to 180 days before you re-approve.

The service covers 2,600+ EU and UK banks and costs roughly EUR 3/month. Every balance and transaction is encrypted so that only a key held on your own device can unlock it — open-banking.io stores just your public key and never holds a certificate on your behalf.

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 open-banking.io and set an encryption passphrase. Your keys are generated locally on your device, so the platform stays zero-knowledge.
  2. In the dashboard, search for SEB (Lithuania) 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 only ever touch SEB.
  4. Once approved, your SEB accounts sync back into the dashboard, ready to view and refresh.

Access your data

Reading SEB data programmatically is an optional step for developers, taken only after the connection above exists. 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 you can 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, and each response is decrypted locally with your private key. An API key on its own only ever returns ciphertext — without the private half no one, including open-banking.io, can read a single SEB transaction.

FAQ

Do I need an eIDAS certificate or a PSD2 licence?

No. open-banking.io is certificate-free. You approve access on SEB's consent screen and the platform handles the regulated plumbing.

Can open-banking.io read my SEB balances?

No. It is zero-knowledge and holds only your public key. Data is decrypted on your device with a key you alone control.

How long does SEB access last?

Up to 180 days per consent. After that you simply re-approve on SEB's login to keep the connection live.

Start connecting SEB (Lithuania) at open-banking.io.