BCC Valdostana Open Banking & API Access Guide

Reading your BCC Valdostana account and transaction data no longer means chasing bank certificates or building a PSD2 stack from scratch. open-banking.io links the Aosta Valley cooperative — BIC ICRAITRRGB0 — to one dashboard that covers 2,600+ European banks, so both business and personal accounts sync into a single place. Every consent lasts up to 180 days before you renew, and the whole service runs from around EUR 3/month.

What sets it apart is the privacy model. open-banking.io is zero-knowledge: your encryption keys are generated on your own device from a passphrase only you know, and the platform stores just your public key. It never sees, holds, or decrypts your BCC Valdostana data — decryption happens locally, on your machine, every time.

How to connect BCC Valdostana

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 generated locally at this moment and never leaves your device.
  2. In the dashboard, search for and select BCC Valdostana, then choose the account type you want to link — business or personal.
  3. You are redirected to BCC Valdostana's own secure login to approve access under PSD2. You authenticate directly with the bank; open-banking.io never sees your banking credentials.
  4. Once you approve, your accounts and transactions sync back into your dashboard, encrypted under your key and readable only by you for the life of the 180-day consent.

Access your data

Programmatic access is an optional developer step you take after connecting — the dashboard connection above must already exist. On the Developers page, create an API key and export a credentials.json file, which bundles that 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. Note that these tools only read and sync connections that already exist — there is no connect command, and an API key on its own returns nothing but ciphertext without your private key.

Does open-banking.io need a certificate from BCC Valdostana?

No. It is certificate-free — you approve access on the bank's consent screen and nothing else is required.

Can open-banking.io read my BCC Valdostana balances?

No. It is zero-knowledge and holds only your public key; your data is decrypted only on your device.

How long does access last?

Up to 180 days per consent, after which you re-approve on BCC Valdostana's login screen.

Start at open-banking.io.