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

Want a private, developer-friendly way to reach your DiPocket data? open-banking.io lets you link your DiPocket account (BIC DIUALT22) and pull balances and transactions on your own terms. DiPocket supports both business and personal accounts, and a single authorisation stays valid for up to 180 days before you renew it.

There are no eIDAS certificates to buy and no PSD2 licence to obtain. open-banking.io is a zero-knowledge service: the encryption keys are generated on your own device, so the platform only ever holds your public key and can never read or decrypt what syncs through it.

How to connect DiPocket

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

  1. Sign up for open-banking.io and set your encryption passphrase; your private key is created locally and never leaves 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 (the standard consent screen).
  4. Once you confirm, your DiPocket accounts sync back into your dashboard, ready to view.

That's the whole flow — you authorise directly with DiPocket, and open-banking.io simply carries the encrypted result to you.

Access your data

Once DiPocket is connected, developers can optionally read everything programmatically. On the Developers page, create an API key and export a credentials.json — this 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 sends the X-Api-Key header, and each response is decrypted locally with your own key. An API key on its own only returns ciphertext — without your private key the data stays unreadable, even to open-banking.io. The CLI and SDK only read and sync connections you already made in the dashboard; they cannot create new ones.

Does open-banking.io need a certificate for DiPocket?

No. The service is certificate-free — no eIDAS or QWAC setup is required on your side.

Can I connect DiPocket from the command line?

No. Linking a bank is a dashboard-only step where you approve access on DiPocket's site. The CLI, SDK and API only read data from connections that already exist.

How much does it cost?

Around EUR 3 per month, covering access across 2,600+ supported EU and UK banks — DiPocket included.

Ready to start? Head to open-banking.io and connect DiPocket in minutes.