BCC di Flumeri Open Banking & API Access | open-banking.io

Reaching your BCC di Flumeri accounts programmatically usually means chasing bank sandboxes, eIDAS certificates and OAuth scopes. open-banking.io removes all of that. It is a certificate-free, zero-knowledge bridge to 2,600+ EU and UK banks, and BCC di Flumeri (BIC CCRTIT2TFLU) — a Campanian credit-cooperative bank in the Avellino area — is one of them. Both business and personal accounts are supported, and a single consent stays valid for up to 180 days before you renew it.

The important distinction: you never "connect" a bank by firing off an API call. Connecting happens entirely inside the open-banking.io dashboard, on BCC di Flumeri's own login screen. Only afterwards, if you are a developer, do you reach for keys and a CLI to read what has already synced.

How to connect BCC di Flumeri

  1. Sign up for open-banking.io and set your encryption passphrase. Your keys are generated locally on your device — open-banking.io only ever holds your public key.
  2. Open the dashboard and search for BCC di Flumeri, then choose the account type you want to link (business or personal).
  3. You are redirected to BCC di Flumeri's own secure login, where you approve access under PSD2 — the standard consent screen you already trust.
  4. Your approved accounts and transactions flow back into your dashboard automatically. No API key, no code, no developer redirect takes part in this step.

That consent is what the 180-day window covers; when it lapses, you simply reconnect from the dashboard.

Access your data

Once BCC di Flumeri is linked, developers can optionally read the data outside the dashboard. On the Developers page, create an API key and export a credentials.json — it bundles your 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. Requests authenticate with the X-Api-Key header, and every response is decrypted locally with your own key. These tools only read and sync existing connections — there is no connect command.

Because the platform is zero-knowledge, an API key alone returns nothing but ciphertext without your private key. At roughly EUR 3/month, that privacy is the default, not an add-on.

Does open-banking.io ever see my BCC di Flumeri data?

No. It stores only your public key; decryption happens on your device, so the servers hold ciphertext they cannot read.

Do I need an eIDAS certificate or bank sandbox?

No. Connection is certificate-free — you authorise BCC di Flumeri directly on its own PSD2 consent screen.

Can the CLI connect the bank for me?

No. Connecting is a dashboard-only flow. The CLI, SDK and API only read or sync accounts you have already linked.

Start at open-banking.io.