DiPocket API Access & Open Banking Integration

Want programmatic reach into your DiPocket accounts without wrestling with eIDAS certificates or building a PSD2 stack from scratch? open-banking.io links your DiPocket (Liechtenstein) profile to a single dashboard and lets you pull balances and transactions on your terms. DiPocket runs under BIC DIUALT22, covers both business and personal accounts, and grants a consent window of up to 180 days before you re-approve.

The service is certificate-free and zero-knowledge: your encryption keys are generated on your own device, and open-banking.io only ever holds your public key. Every figure you read is decrypted locally, so no server — not even ours — can see your DiPocket balances in the clear. It sits across 2,600+ EU and UK banks for roughly EUR 3/month.

How to connect DiPocket

Connecting happens entirely in 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 private key is created locally and never leaves your device.
  2. In the dashboard, choose DiPocket and select the account type you hold (business or personal).
  3. You are redirected to DiPocket's own secure login, where you approve access under PSD2 on the bank's consent screen.
  4. Your DiPocket accounts sync back into the dashboard, refreshing for the length of the 180-day consent.

Access your data

Once DiPocket is connected, developers can optionally read it programmatically. On the Developers page, create an API key and export a credentials.json — this bundles the API key together with your private decryption key. From there, use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API. Requests authenticate with the X-Api-Key header, and each response is decrypted locally with your key. The API key alone returns only ciphertext — readable data requires your private key too. The CLI and SDK read and sync existing connections; they never create them.

Does open-banking.io store my DiPocket credentials?

No. You authenticate on DiPocket's own login, and the service holds only your public key — it cannot decrypt your data.

Can I connect DiPocket business accounts?

Yes. DiPocket supports both business and personal account types through the same dashboard flow.

How often do I re-approve access?

DiPocket allows a consent of up to 180 days, after which you re-confirm on its consent screen.

Start at open-banking.io.