BCC Leverano API Access & Open Banking Data

Reading your BCC Leverano accounts programmatically usually means chasing PSD2 certificates and per-bank paperwork. open-banking.io removes that entirely: it covers 2,600+ EU and UK banks — including BCC Leverano — behind one dashboard, so you can pull balances and transactions without ever registering as a licensed third party. BCC Leverano supports both personal and business accounts, and a single approval keeps your connection live for up to 180 days before you re-confirm.

Everything stays private by design. open-banking.io is zero-knowledge: your encryption keys are generated on your own device from a passphrase you choose, and the service only ever holds your public key. It never sees a certificate on your behalf and it cannot read your data.

How to connect BCC Leverano

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 your encryption passphrase; your private key is created locally and never leaves your device.
  2. In the dashboard, search for BCC Leverano and choose the account type you want to link — personal or business.
  3. You are redirected to BCC Leverano's own secure login and consent screen, where you approve access directly with the bank (standard PSD2 consent).
  4. Once approved, your accounts sync back into your open-banking.io dashboard, ready to view.

The consent you grant BCC Leverano lasts up to 180 days, after which you simply repeat the approval.

Access your data

After the connection exists, developers can optionally read it in code. On the Developers page, create an API key and export a credentials.json — this bundles the API key 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. Without that private key, an API key alone returns only ciphertext — which is exactly what keeps the model zero-knowledge. Note the CLI and SDK only read and sync existing connections; there is no connect command.

All of this runs on a flat subscription of roughly EUR 3/month, with no certificate costs and no BIC required (BCC Leverano's BIC is not needed here).

Do I need a PSD2 certificate for BCC Leverano?

No. open-banking.io handles the regulated access layer, so you approve consent on BCC Leverano's site and skip certificates entirely.

Can open-banking.io read my BCC Leverano transactions?

No. Data is decrypted only on your device with a key that never leaves it. The service holds just your public key.

Does connecting require writing any code?

No. Connecting is done in the dashboard by approving access on BCC Leverano's own login. Code is only for the optional read step afterward.

Start at open-banking.io.