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

Want a single, private window into your DiPocket (Portugal) money? open-banking.io lets you link DiPocket alongside 2,600+ other EU and UK banks and read the data on your own terms. Nothing is decrypted on our servers — we hold only your public key, so balances and transactions become readable only on your device, with a key that never leaves your hands. No eIDAS certificate, no bank-specific paperwork, just a clean dashboard and, if you want it, a developer toolkit.

DiPocket operates under BIC DIUALT22 and supports both business and personal accounts, with PSD2 consent lasting up to 180 days before you re-approve.

How to connect DiPocket

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

  1. Sign up for open-banking.io and set your encryption passphrase. Your keys are generated locally on your own device at this step.
  2. In the dashboard, choose DiPocket and select the account type — business or personal.
  3. You are redirected to DiPocket's own secure login and consent screen, where you approve access directly with your bank (standard PSD2 flow).
  4. Once approved, your DiPocket accounts sync back into your dashboard, ready to view.

That's the whole flow — you, your bank, and your passphrase. open-banking.io never sees your DiPocket credentials.

Access your data

After DiPocket is connected, developers can optionally read the data programmatically. Open the Developers page, create an API key, and export a credentials.json — this bundles the API key together with your private decryption key. Then reach for the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API. 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 it stays unreadable. Note that the CLI and SDK only read and sync connections that already exist; there is no connect command.

All of this runs at roughly EUR 3/month.

Do I need a certificate or DiPocket developer account?

No. open-banking.io is certificate-free; you approve access on DiPocket's normal consent screen.

Can open-banking.io read my DiPocket transactions?

No. It's zero-knowledge — servers hold only your public key, so data is decrypted solely on your device.

How long does access last before renewal?

DiPocket consent runs up to 180 days, after which you re-approve on the bank's screen.

Ready to start? Visit open-banking.io.