Access DiPocket in Sweden via Open Banking API

Want to pull your DiPocket balances and transaction history into your own tools? open-banking.io gives you a PSD2 route to your DiPocket (Sweden) data without certificates, eIDAS registration, or a bank-side developer programme. You connect once in a web dashboard, and from there your accounts stay in sync — ready to read on your own terms.

DiPocket is an e-money and prepaid provider (BIC DIUALT22) covering both business and personal accounts. A single authorisation grants up to a 180-day consent window before DiPocket asks you to renew, so you get months of uninterrupted access from one approval.

How to connect DiPocket

Connecting happens entirely inside the open-banking.io dashboard — there is no API call, endpoint, or key involved in this step.

  1. Sign up for open-banking.io and open the dashboard.
  2. Set an encryption passphrase. Your key pair is generated locally on your device; open-banking.io only ever sees your public key.
  3. In the dashboard, pick DiPocket and choose the account type — business or personal.
  4. You are redirected to DiPocket's own secure login, where you approve access on their consent screen (standard PSD2 flow).
  5. Your DiPocket accounts sync back into your dashboard, and stay refreshed for the life of the consent.

That's it — no code required to get your data flowing.

Access your data

Once DiPocket is connected, developers can optionally read the data programmatically. On the Developers page, create an API key and export a credentials.json — this bundles your API key together with your private decryption key. Then reach for whatever fits:

  • CLI: openbanking accounts, openbanking transactions, openbanking sync
  • an SDK, or the REST API directly

Requests authenticate with the X-Api-Key header, and every response is decrypted locally with your own key. The API key alone only ever returns ciphertext — without your private key, nobody (including open-banking.io) can read a thing. Note that the CLI and SDK only read and sync connections you've already made; they never connect a bank.

This is what zero-knowledge means in practice: open-banking.io holds your encrypted data and your public key, and the plaintext exists only on your machine. All of it for around EUR 3/month.

FAQ

Do I need an eIDAS certificate to access DiPocket?

No. open-banking.io is certificate-free — you authorise directly on DiPocket's login screen, no QWAC or QSEAL required.

Can open-banking.io read my DiPocket transactions?

No. Data is encrypted with a key generated on your device. Servers store only ciphertext and your public key.

Each account type is authorised separately, but both are supported, each with a 180-day consent window.

Ready to start? Visit open-banking.io.