DiPocket API Access & Open Banking via open-banking.io

Want programmatic access to your DiPocket accounts? open-banking.io lets you link DiPocket (BIC DIUALT22) and pull balances and transactions into one place — without certificates, sandbox paperwork, or a PSD2 licence of your own. It covers 2,600+ European banks for roughly EUR 3/month, and its defining trait is privacy: it is zero-knowledge. Your encryption keys are generated on your own device, so the platform only ever holds your public key and stores ciphertext it cannot read.

How to connect DiPocket

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 your encryption passphrase. Your private key is created locally, right there in your browser.
  2. In the dashboard, choose DiPocket from the bank list and pick the account type you need — DiPocket supports both business and personal accounts.
  3. You're redirected to DiPocket's own secure login, where you approve access under PSD2. open-banking.io never sees your banking credentials.
  4. Your accounts sync back into the dashboard. The consent you grant lasts up to 180 days, after which you simply re-approve on DiPocket's screen.

Access your data

Once DiPocket is connected, developers can optionally read the data programmatically. Open the Developers page, create an API key, and export a credentials.json — this bundles your API key together with your private decryption key.

From there, 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 each response is decrypted locally with your own key. Note that the API key alone returns only ciphertext — without your private key, the data stays unreadable, which is exactly what zero-knowledge means. The CLI and SDK only read and sync connections you already made in the dashboard; they cannot establish a new one.

Do I need a developer account with DiPocket?

No. You only need your own DiPocket online banking login to approve access. No bank-side API registration is required.

Can open-banking.io see my DiPocket transactions?

No. Data is encrypted with a key only you hold. The servers store an unreadable copy and never have your private key.

How long does access stay active?

Up to 180 days per consent. When it expires, re-approve on DiPocket's login screen to keep syncing.

Ready to start? Visit open-banking.io.