DiPocket API Access & Open Banking Guide (Malta)

Want a single, private window into your DiPocket (Malta) accounts? open-banking.io links your DiPocket profile to a zero-knowledge dashboard that covers 2,600+ EU and UK banks. Everything you see is decrypted on your own device with a key only you hold — DiPocket's balances and transactions never sit in readable form on our servers. DiPocket (BIC DIUALT22) supports both business and personal accounts, and a single approval keeps your data flowing for up to 180 days.

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 for open-banking.io and set your encryption passphrase. Your keys are generated locally on your device, so the passphrase never leaves it.
  2. In the dashboard, choose DiPocket from the bank list 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. open-banking.io never sees your DiPocket credentials.
  4. Once approved, your DiPocket accounts sync straight into your dashboard. That consent stays valid for 180 days before DiPocket asks you to renew it.

No certificates, no eIDAS setup, no manual configuration — just the bank's standard consent screen.

Access your data

Already connected and want to pull DiPocket data into your own tools? This developer step is entirely optional. On the Developers page, create an API key and export a credentials.json — it bundles that key 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 carries the X-Api-Key header, and each response is decrypted locally with your own key. The CLI and SDK only read and refresh connections you've already made in the dashboard — there's no connect command, because linking a bank always goes through DiPocket's consent flow. Note that an API key alone returns only ciphertext; without your private key, the data stays unreadable.

FAQ

Can open-banking.io read my DiPocket transactions?

No. The service is zero-knowledge and stores only your public key. Decryption happens on your device, so we can't read or reconstruct your DiPocket data.

Do I need a developer setup to use DiPocket here?

No. Viewing accounts in the dashboard needs no code. The API key and credentials.json are only for reading data programmatically after you've connected.

What does it cost?

Around EUR 3 per month covers access to DiPocket and every other supported bank — no per-connection or certificate fees.

Ready to begin? Head to open-banking.io and link DiPocket in minutes.