Hvidbjerg Bank Open Banking & API Access | open-banking.io

Reach your Hvidbjerg Bank accounts through a single, privacy-first interface. open-banking.io links to Hvidbjerg Bank under PSD2 and lets you view balances and transactions in a clean dashboard — with an optional developer layer for programmatic access when you need it. There are no eIDAS certificates to buy and no bank-specific integration to build; the same flow that works for 2,600+ European banks works here.

Crucially, open-banking.io is zero-knowledge. When you sign up you set an encryption passphrase, and the keys are generated on your own device. The service only ever holds your public key, so your Hvidbjerg Bank data is decrypted locally — never on our servers.

How to connect Hvidbjerg Bank

Connecting happens entirely in the open-banking.io dashboard — there is no API call, code, or key involved in this step.

  1. Create your open-banking.io account and set your encryption passphrase (your keys are generated locally at this moment).
  2. In the dashboard, search for and select Hvidbjerg Bank, then choose the account type you want to link — business or personal.
  3. You are redirected to Hvidbjerg Bank's own secure login to approve access on their consent screen.
  4. Once approved, your accounts sync into your open-banking.io dashboard automatically.

Hvidbjerg Bank grants consent for up to 180 days, after which you simply re-approve on their screen to keep the connection live. (No BIC is required to select the bank in the dashboard.)

Access your data

After your Hvidbjerg Bank accounts are connected, developers can optionally read them 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. Every request sends the X-Api-Key header, and each response is decrypted locally with your own key. Note that the CLI and SDK only read and sync connections that already exist — they never create one. An API key on its own returns only ciphertext; without your private key the data stays unreadable.

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

Do I need a certificate or developer account with Hvidbjerg Bank?

No. open-banking.io is certificate-free. You approve access on Hvidbjerg Bank's consent screen and everything else runs through your dashboard.

Can open-banking.io read my Hvidbjerg Bank data?

No. It is zero-knowledge — decryption happens on your device with a key only you hold. Our servers store just your public key.

How long does access to Hvidbjerg Bank last?

Hvidbjerg Bank consent lasts up to 180 days. Re-approve on the bank's screen to renew it.

Ready to start? Visit open-banking.io.