DiPocket API Access & Open Banking Data (Finland)

Pulling your DiPocket balances and transactions into your own tools usually means wrestling with PSD2 certificates, sandbox registrations and per-bank quirks. open-banking.io removes all of that. It gives you one certificate-free path to DiPocket (BIC DIUALT22) in Finland, covering both business and personal accounts, with consent that lasts up to 180 days before you re-approve.

The difference that matters: open-banking.io is zero-knowledge. Your encryption keys are generated on your own device from a passphrase only you know, and every account response is decrypted locally. The service stores only your public key, so it can never read your DiPocket data — even though it moves it.

How to connect DiPocket

Connecting is done 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 private key is created locally at this moment and never leaves your device.
  2. In the dashboard, search for DiPocket and choose the account type you need — business or personal.
  3. You are redirected to DiPocket's own secure login, where you approve access on the bank's consent screen (standard PSD2 authorisation).
  4. Once approved, your DiPocket accounts sync back into your open-banking.io dashboard, ready to view.

That's the whole flow. You never hand credentials to open-banking.io; DiPocket authenticates you directly.

Access your data

Reading DiPocket programmatically is an optional step you take after the connection 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. Then use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API directly. Requests authenticate with the X-Api-Key header, and each response is decrypted locally with your own key. Without that private key, an API key alone returns only ciphertext — which is exactly what keeps the system zero-knowledge. Note the CLI and SDK only read and sync existing connections; there is no connect command.

All of this runs for around EUR 3/month, with no certificate paperwork.

FAQ

Do I need a PSD2 certificate for DiPocket?

No. open-banking.io handles the regulated connection, so you approve access on DiPocket's screen and never manage certificates yourself.

Can open-banking.io see my DiPocket transactions?

No. It holds only your public key. Data is decrypted on your device with a private key that never leaves it.

Can I connect DiPocket from the CLI?

No. Connecting happens in the dashboard via DiPocket's consent screen. The CLI and API only read data once the connection is live.

Start at open-banking.io.