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

Need a clean, private route into your DiPocket account data? open-banking.io links your DiPocket profile to a single dashboard and keeps the whole flow zero-knowledge: your balances and transactions are decrypted on your own device with a key that never leaves it. DiPocket serves both business and personal accounts (BIC DIUALT22), and a granted consent stays live for up to 180 days before you re-approve — so most of the time you just watch the data flow in.

There are no eIDAS certificates to buy and no PSD2 sandbox to register for. For roughly EUR 3/month you get supervised access to 2,600+ EU and UK banks, DiPocket included.

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 key pair is generated locally; the service only ever holds your public key.
  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 are entered only on DiPocket's screen.
  4. Confirm consent (valid up to 180 days) and your accounts sync straight into your open-banking.io dashboard.

That's it — no developer redirect, no certificate upload, nothing to host.

Access your data

Once DiPocket is connected, reading it programmatically is an optional developer step. On the Developers page, create an API key and export a credentials.json — this bundles the API key with your private decryption key. From there:

  • Use the CLI: openbanking accounts, openbanking transactions, openbanking sync.
  • Or call the REST API / SDK, sending your key in the X-Api-Key header.

Every response is ciphertext until it is decrypted locally with your private key. The CLI and SDK only read and sync connections you already made in the dashboard — there is no connect command, and an API key alone returns nothing readable.

FAQ

Do I need a PSD2 licence to access DiPocket?

No. open-banking.io is the regulated intermediary. You approve access on DiPocket's own login screen; no certificates or licences on your side.

Can open-banking.io read my DiPocket transactions?

No. It is zero-knowledge and stores only your public key. Data is decrypted on your device with a key only you hold.

DiPocket supports business and personal accounts, and each consent lasts up to 180 days before renewal.

Ready to start? Head to open-banking.io.