LKU Open Banking API Access via open-banking.io

LKU (Lietuvos centrinė kredito unija, BIC LCKULT22XXX) is a Lithuanian credit-union network, and open-banking.io lets you reach its account and payment data without wrestling with eIDAS certificates or a bespoke PSD2 sandbox. It is part of a single service covering 2,600+ EU and UK banks, so LKU sits behind the same dashboard and the same tooling as every other institution you connect. The defining trait is zero-knowledge: your data is encrypted with a key generated on your device, and open-banking.io only ever holds your public key — it can never read or decrypt what syncs through it.

How to connect LKU

Connecting happens entirely in the open-banking.io dashboard, not through any API call or code.

  1. Sign up and set an encryption passphrase — your key pair is generated locally, on your own device.
  2. In the dashboard, pick LKU and choose the account type you hold: business or personal are both supported.
  3. You are redirected to LKU’s own secure login, where you approve access (standard PSD2 consent). open-banking.io never sees your banking credentials.
  4. Your accounts sync back into the dashboard, and the connection stays valid for up to the 180-day maximum consent window before LKU asks you to re-authorise.

There is no API key, POST request, or developer redirect anywhere in this flow — it is a straightforward bank-approval step.

Access your data

Reading LKU data programmatically is an optional step you take after the connection exists. On the Developers page, create an API key and export a credentials.json that bundles that key with your private decryption key. From there use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API directly. Requests authenticate with the X-Api-Key header, and every response is decrypted locally with your own key. None of these tools can connect a bank — there is no connect command; they only read and refresh connections you already approved in the dashboard.

FAQ

Does open-banking.io store my LKU login or data unencrypted?

No. It is zero-knowledge and holds only your public key. Credentials go straight to LKU, and synced data is decrypted on your device.

What does it cost?

Around EUR 3 per month for full access across all supported banks, LKU included.

Can I read LKU data with just an API key?

No. The API key alone returns ciphertext. Without your private decryption key you cannot read anything, which is what keeps the service certificate-free yet private.

Ready to start? Visit open-banking.io.