DiPocket API Access & Open Banking (Lithuania)

Reaching your DiPocket balances and transactions from your own tools no longer means chasing a PSD2 licence or juggling QWAC certificates. open-banking.io sits between you and DiPocket (Lithuania, BIC DIUALT22), handling the regulated connection so you can focus on the data. It works with both business and personal DiPocket accounts, and a single approval keeps the link alive for the full 180-day consent window before you refresh it.

Everything is built around a zero-knowledge, certificate-free design: your data is encrypted with a key generated on your own device, and the service only ever holds your public key. That means the servers relaying your DiPocket feed can never read a single transaction.

How to connect DiPocket

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

  1. Sign up for open-banking.io and set your encryption passphrase. Your decryption keys are created locally, on your device.
  2. In the dashboard, search for DiPocket and choose the account type you hold — business or personal.
  3. You are redirected to DiPocket's own secure login, where you approve access under PSD2. Your credentials stay with DiPocket.
  4. Once approved, your DiPocket accounts sync straight into your dashboard, ready to view.

Access your data

Want DiPocket data in your own scripts? That is an optional step you take after connecting. Open 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

…or reach the same data through an SDK or the REST API. Every request carries the X-Api-Key header, and each response is decrypted locally with your own key. The CLI and SDK only read and sync connections that already exist — the bank link itself is always made in the dashboard.

Does open-banking.io ever see my DiPocket transactions?

No. It is zero-knowledge and holds only your public key. Decryption happens on your machine.

Is the API key enough to read my data?

No. An API key alone returns ciphertext. Readable data requires your private decryption key, which lives in your credentials.json.

What does it cost?

Around EUR 3/month, covering DiPocket and 2,600+ other EU and UK banks.

Start at open-banking.io.