DiPocket API Access & Open Banking Data Export

Pulling your DiPocket balances and transactions into your own tools normally means wrestling with PSD2 certificates and sandbox paperwork. open-banking.io removes that: it is a certificate-free bridge to 2,600+ EU and UK institutions, DiPocket (BIC DIUALT22) among them. You link the account once in a browser, and everything after that is decrypted on your own device with a key nobody else holds.

DiPocket exposes both business and personal accounts here, and a single approval keeps data flowing for up to 180 days before you re-confirm.

How to connect DiPocket

Connecting is done entirely in the open-banking.io dashboard — there is no endpoint to call and no key to paste:

  1. Create an open-banking.io account and set your encryption passphrase. Your key pair is generated locally, so only the public half ever leaves your machine.
  2. Open 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 on their PSD2 consent screen.
  4. Control returns to your dashboard and your DiPocket accounts begin syncing.

Because the approval happens on DiPocket's side, open-banking.io never sees your banking credentials — and because the service is zero-knowledge, its servers store only ciphertext plus your public key.

Access your data

Reading DiPocket programmatically is an optional step you take after the connection exists. On the Developers page, generate an API key and export a credentials.json — it bundles that API key with your private decryption key. From there you can use the CLI:

openbanking accounts
openbanking transactions
openbanking sync

or call the same data through an SDK or the REST API. Every request carries your key in the X-Api-Key header, and each response is decrypted locally with your private key. The API key alone only ever returns ciphertext, which is what keeps the model zero-knowledge. Note the CLI and SDK read and refresh existing links — they cannot create the DiPocket connection itself; that stays in the dashboard.

All of this runs on flat pricing of roughly EUR 3/month, with no per-call fees or certificate renewals.

Do I need an eIDAS certificate for DiPocket?

No. open-banking.io is certificate-free — the dashboard consent flow handles PSD2 access for you.

Can open-banking.io read my DiPocket transactions?

No. It holds only your public key and encrypted blobs; decryption happens on your device with a key only you have.

How long does DiPocket access last?

Up to 180 days per approval, after which you re-confirm consent on DiPocket's login screen.

Start linking DiPocket at open-banking.io.