Bankhaus Werhahn API Access & Open Banking Data

Bankhaus Werhahn, the Neuss-based private bank of the Werhahn Group, keeps your balances and transactions behind its own secure banking login. open-banking.io gives you a clean, standardised way to reach that data — across both business and personal accounts — without certificates, eIDAS QWACs, or a bespoke integration. You approve access once, and your Bankhaus Werhahn accounts (BIC WERHDED1XXX) flow into a dashboard where the data is decrypted locally with a key only you hold.

Because open-banking.io is zero-knowledge, our servers only ever see your public key. Every balance and transaction is encrypted end-to-end, so no operator — not us, not a third party — can read what syncs from your Bankhaus Werhahn accounts. One flat subscription of roughly EUR 3/month covers access to Bankhaus Werhahn and 2,600+ other EU and UK banks.

How to connect Bankhaus Werhahn

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 an encryption passphrase. Your encryption keys are generated on your own device and never leave it.
  2. In the dashboard, pick Bankhaus Werhahn and choose the account type you need — business or personal.
  3. You are redirected to Bankhaus Werhahn's own secure login, where you approve access under PSD2. Consent lasts up to 180 days before a quick re-approval is needed.
  4. Your accounts sync back into the dashboard, ready to view.

Access your data

Once the connection exists, 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 every response is decrypted locally with your own key. The API key alone returns only ciphertext; without your private key, nothing is readable. Note the CLI and SDK read and sync existing connections — they never connect a bank.

Do I need a certificate or PSD2 licence?

No. open-banking.io handles the regulated plumbing. You approve access on Bankhaus Werhahn's login screen — no QWAC, no onboarding paperwork.

Can open-banking.io see my Bankhaus Werhahn data?

No. It is zero-knowledge; the service holds only your public key, and decryption happens on your device.

How long does access last?

Bankhaus Werhahn permits consent for up to 180 days, after which you re-approve with a short login.

Start at open-banking.io.