DiPocket Slovenia Open Banking API Access Guide

Want programmatic access to your DiPocket (Slovenia) account data without wrestling with eIDAS certificates or a PSD2 sandbox? open-banking.io gives you a single, privacy-first route to your e-money balances and transactions. It reaches 2,600+ banks and payment institutions across the EU and UK, and every figure that lands in your dashboard is decrypted locally with a key that never leaves your device.

DiPocket carries the BIC DIUALT22 and covers both business and personal account types, so whether you run a company wallet or a personal card, the same flow applies. Consent lasts up to 180 days before DiPocket asks you to renew it.

How to connect DiPocket

Connecting happens entirely inside the open-banking.io dashboard — there is no API call, code, or key involved in linking your account.

  1. Sign up for open-banking.io and set your encryption passphrase. Your cryptographic keys are generated right there on your own device.
  2. Open the dashboard, choose DiPocket (Slovenia), and select whether you're linking a business or personal account.
  3. You're redirected to DiPocket's own secure login, where you approve access under PSD2 — your credentials only ever touch DiPocket, never us.
  4. Once approved, your accounts and transactions sync straight into your dashboard.

That's the whole connection. No developer redirect, no client secret, no certificate to provision.

Access your data

Reading DiPocket data programmatically is an optional step you take after the account is connected. On the Developers page, generate an API key and export a credentials.json — it bundles that 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 directly. Every request authenticates with the X-Api-Key header, and each response is decrypted locally with your own key. Note there is no connect command — the tooling only reads and syncs connections you already made in the dashboard.

This is what zero-knowledge means in practice: our servers hold only your public key, so an API key on its own returns ciphertext. Without your private key, nobody — not even us — can read a single transaction. All for around EUR 3/month.

FAQ

Do I need an eIDAS certificate to access DiPocket?

No. open-banking.io is certificate-free — you connect through DiPocket's own consent screen in the dashboard.

Can the CLI connect my DiPocket account?

No. The CLI and SDK only read and sync existing connections. Linking DiPocket happens in the dashboard.

How long does my access stay valid?

DiPocket grants consent for up to 180 days, after which you re-approve access to keep syncing.

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