DiPocket Open Banking API Access — open-banking.io

Want programmatic, privacy-first access to your DiPocket (Slovakia) account data? open-banking.io lets you link your DiPocket e-money accounts through regulated PSD2 access and pull balances and transactions on your own terms. DiPocket carries the BIC DIUALT22, supports both business and personal accounts, and grants a maximum consent window of 180 days before you renew — all handled for you inside the service.

Because open-banking.io is zero-knowledge and certificate-free, there is no eIDAS certificate to buy and no server that can ever read your statements. Your encryption keys are generated on your own device, so DiPocket data is only ever decrypted locally, by you.

How to connect DiPocket

Connecting happens entirely in 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 keys are created locally on your device; the service only ever holds your public key.
  2. In the dashboard, search for and select DiPocket and choose the account type you hold — business or personal.
  3. You are redirected to DiPocket's own secure login and consent screen, where you approve access directly with the bank (standard PSD2 authorisation).
  4. Once approved, your DiPocket accounts sync back into your open-banking.io dashboard, ready to view. Renew before the 180-day consent expires to keep the link live.

Access your data

Reading DiPocket data programmatically is an optional step you take after the connection above already exists. 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. Every request sends the X-Api-Key header, and each response is decrypted locally with your own key. The CLI and SDK only read and sync connections that already exist — there is no connect command, and an API key on its own returns only ciphertext without your private key.

All of this runs for roughly EUR 3 per month, across 2,600+ supported EU and UK banks.

Does connecting DiPocket require a certificate or API key?

No. You connect in the dashboard and approve on DiPocket's own screen. API keys are only for the optional developer read step afterwards.

Can open-banking.io staff see my DiPocket transactions?

No. The service is zero-knowledge and holds only your public key; data is decrypted locally with a key only you hold.

Business and personal accounts, with a maximum consent of 180 days per authorisation before renewal.

Ready to start? Visit open-banking.io.