DiPocket Open Banking & API Access in Hungary

Want a private, developer-friendly way to reach your DiPocket balances and transactions? open-banking.io links your Hungarian DiPocket account (BIC DIUALT22) to a single dashboard that covers 2,600+ EU and UK banks. Both business and personal DiPocket accounts are supported, and a granted consent stays valid for up to 180 days before you renew it.

What sets this apart is the zero-knowledge design. When you register you set an encryption passphrase, and your keys are generated locally on your own device. open-banking.io stores only your public key, so its servers never hold anything they can read — every figure that reaches you is decrypted on your machine. There are no eIDAS certificates to buy and no QWAC to configure; the whole thing runs for around EUR 3/month.

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 at open-banking.io and set your encryption passphrase (your private key is created on your device).
  2. Open the dashboard and choose DiPocket from the bank list, then pick the account type — business or personal.
  3. You are redirected to DiPocket's own secure login, where you approve access under PSD2.
  4. Your DiPocket accounts sync back into the dashboard, ready to view.

That consent lasts up to 180 days, after which you simply reauthorise from the same screen.

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 together with your private decryption key. From there use the CLI (openbanking accounts, openbanking transactions, openbanking sync), 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 API key alone only ever returns ciphertext — without your private key, nothing is readable. Note there is no connect command: the CLI and SDK read and sync existing connections only.

Do I need a certificate or license for DiPocket?

No. open-banking.io is certificate-free — no eIDAS or QWAC. You sign in and approve on DiPocket's own screen.

Can open-banking.io read my DiPocket transactions?

No. It holds only your public key. Decryption happens on your device with a key that never leaves it.

DiPocket consent runs up to 180 days. Reauthorise from the dashboard to keep syncing.

Start at open-banking.io.