Crelan API Access & Open Banking Integration (Belgium)

Crelan is one of Belgium's cooperative retail banks, and open-banking.io lets you reach its account and transaction data without wrestling with eIDAS certificates or PSD2 sandboxes. You link Crelan once through your dashboard, and from that point your balances and payment history flow into a place where every byte is decrypted locally with a key that never leaves your device.

Both business and personal Crelan accounts (BIC NICABEBB) are supported, and a single consent stays valid for up to 180 days before Crelan asks you to renew it.

How to connect Crelan

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

  1. Sign up for open-banking.io and set your encryption passphrase. Your key pair is generated right there on your own device.
  2. In the dashboard, search for Crelan and choose the account type you hold — business or personal.
  3. You are redirected to Crelan's own secure login, where you approve the access request (standard PSD2 consent) directly with the bank.
  4. Once you confirm, your Crelan accounts sync back into your dashboard and stay in step for the life of the 180-day consent.

open-banking.io never sees your Crelan credentials — you authenticate on Crelan's site, not ours.

Access your data

Reading Crelan data programmatically is an optional step you take after the connection exists. From the Developers page, create an API key and export a credentials.json — it bundles the API key together with your private decryption key. From there you can use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API directly. Requests carry the X-Api-Key header, and each response is decrypted locally with your own key. The API key alone only ever returns ciphertext; without your private key it stays unreadable — which is exactly what zero-knowledge means. The CLI and SDK only read and sync connections you already made in the dashboard.

All of this runs at roughly EUR 3/month, covering 2,600+ EU and UK banks.

Is a QWAC or eIDAS certificate required?

No. open-banking.io is certificate-free — you approve access on Crelan's login screen and never handle a PSD2 certificate.

Can open-banking.io read my Crelan transactions?

No. Servers hold only your public key, so stored data is ciphertext; decryption happens on your device with a key only you possess.

Up to 180 days. After that Crelan prompts you to re-approve, which you do again through its own login.

Ready to begin? Start at open-banking.io.