DiPocket Open Banking & API Access | open-banking.io

DiPocket is a Cyprus-based e-money and card platform (BIC DIUALT22) serving both business and personal account holders. With open-banking.io you can pull your DiPocket balances and transaction history into one place and — if you want — read them programmatically. Everything stays private by design: open-banking.io is zero-knowledge and certificate-free, so your data is decrypted on your own device with a key that never leaves it. There are no eIDAS certificates to buy and no bank paperwork to file.

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 at open-banking.io and set your encryption passphrase. Your key pair is generated locally, so only you hold the private key.
  2. In the dashboard, search for DiPocket and choose your account type — business or personal.
  3. You are redirected to DiPocket's own secure login, where you approve access under PSD2. open-banking.io never sees your credentials.
  4. Your DiPocket accounts sync into the dashboard. A single consent lasts up to 180 days, after which you simply re-approve on DiPocket's screen.

Access your data

Once DiPocket is connected, developers can optionally read the data outside the dashboard. On the Developers page, create an API key and export a credentials.json — this file bundles your API key with your private decryption key. From there:

  • Use the CLI: openbanking accounts, openbanking transactions, openbanking sync.
  • Or call the REST API / SDK, sending your key in the X-Api-Key header.

Every response arrives encrypted and is decrypted locally with your own key. The API key alone only returns ciphertext — without your private key, nobody (including open-banking.io) can read it. The CLI and SDK only read and sync connections you already made in the dashboard; there is no connect command.

All of this is included for about EUR 3/month.

Do I need a developer account to use DiPocket?

No. Connecting and viewing DiPocket works in the dashboard alone. API keys are only for reading the data in your own code.

Can open-banking.io see my DiPocket transactions?

No. The service is zero-knowledge and holds only your public key. Decryption happens on your device.

How long does DiPocket access stay active?

Up to 180 days per consent. When it expires, re-approve on DiPocket's secure login to keep syncing.

Start at open-banking.io.