KBC Brussels API Access & Open Banking Connect

Belgium's KBC Brussels serves both households and companies, and open-banking.io lets you pull that account data into a single private workspace. Instead of juggling manual bank exports, you link KBC Brussels once and keep a live, encrypted copy of your balances and transactions that only you can read. There is no certificate to register and no eIDAS onboarding — just a passphrase you choose and encryption keys generated on your own device.

How to connect KBC Brussels

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

  1. Sign up for open-banking.io and set your encryption passphrase. Your keys are created locally, so the service only ever holds your public key.
  2. In the dashboard, pick KBC Brussels (BIC KREDBEBB387) and choose the account type you hold — business or personal.
  3. You are redirected to KBC Brussels's own secure login, where you approve access under PSD2. Consent lasts up to 180 days, after which you simply renew it.
  4. Your approved accounts sync back into the dashboard, and balances and transactions refresh automatically.

Access your data

Reading data programmatically is an optional developer step you take after the account is connected. Open 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 carries the X-Api-Key header, and each response is decrypted locally with your own key. An API key on its own only ever returns ciphertext — without your private key, nobody, including open-banking.io, can read it.

That is the point of the zero-knowledge design: your KBC Brussels data is encrypted end to end, and the servers store only your public key. All of this runs for roughly EUR 3/month across 2,600+ supported EU and UK banks.

Do I need a developer certificate for KBC Brussels?

No. open-banking.io is certificate-free. You authorise access directly on KBC Brussels's consent screen — no eIDAS or QWAC certificate required.

Can the CLI connect my KBC Brussels account?

No. The CLI and SDK only read and sync connections that already exist. Linking KBC Brussels always happens in the dashboard through the bank's own login.

How long does access last?

KBC Brussels consent is valid for up to 180 days. When it expires, reauthorise from the dashboard to keep your data flowing.

Start linking your accounts at open-banking.io.