CBNK Open Banking: API Access to Your Bank Data

Reaching your CBNK accounts programmatically no longer means wrestling with eIDAS certificates or a PSD2 sandbox. open-banking.io gives you a certificate-free path to CBNK (BIC CCOCESMM) that covers both business and personal accounts, with consent valid for up to 180 days before you renew it. Everything your bank returns is decrypted on your own device with a key only you hold — the service is zero-knowledge and never sees your data in the clear.

How to connect CBNK

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

  1. Sign up and set an encryption passphrase. Your key pair is generated locally on your device, so only your public key ever leaves it.
  2. In the dashboard, choose CBNK and select the account type you want to link — business or personal.
  3. You are redirected to CBNK's own secure login, where you approve access under PSD2 on the bank's consent screen.
  4. Once CBNK confirms, your accounts and transactions sync straight into your dashboard.

That's the whole flow. You authenticate directly with CBNK, and open-banking.io only ever stores encrypted results tied to your public key.

Access your data

If you're a developer, reading CBNK data programmatically is an optional step you take after the connection exists. Open 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:

  • Use the CLI: openbanking accounts, openbanking transactions, openbanking sync.
  • Or call the REST API / SDK, sending your key in the X-Api-Key header.

Every response is decrypted locally with your private key. An API key on its own only ever returns ciphertext — without your key there is nothing readable to leak. Note the CLI and SDK read and refresh existing connections; they never create one.

All of this runs for roughly EUR 3/month, with no certificate purchase and no per-call enterprise contract.

Is a QWAC or eIDAS certificate required for CBNK?

No. open-banking.io handles the PSD2 layer, so you connect CBNK without any certificate of your own.

Can open-banking.io read my CBNK transactions?

No. It holds only your public key, so stored data stays encrypted and is decrypted solely on your device.

Do the CLI or SDK connect my CBNK account?

No. Connecting is done once in the dashboard on CBNK's consent screen; the tools only sync and read that existing link.

Start linking CBNK at https://open-banking.io.