BCC Altofonte e Caccamo Open Banking & API Access
Want a single, private way to reach your BCC Altofonte e Caccamo accounts? open-banking.io lets you link this Sicilian Banca di Credito Cooperativo (BIC ICRAITRR9H0) and pull balances and transactions into one place — without certificates, screen-scraping, or handing anyone your credentials. The service covers 2,600+ EU/UK banks and works for both business and personal BCC Altofonte e Caccamo accounts, with a PSD2 consent that stays valid for up to 180 days before you renew it.
Everything is zero-knowledge by design. Your encryption keys are generated on your own device, and open-banking.io only ever holds your public key — so account data is decrypted locally, by you, and never in readable form on any server.
How to connect BCC Altofonte e Caccamo
Connecting happens entirely in the open-banking.io dashboard — there is no code or API call involved:
- Sign up for open-banking.io and set your encryption passphrase. Your private key is created locally on your device at this step.
- In the dashboard, choose BCC Altofonte e Caccamo and select the account type you want to link (business or personal).
- You are redirected to BCC Altofonte e Caccamo's own secure login and consent screen, where you approve access directly with the bank under PSD2.
- Once approved, your accounts sync back into your open-banking.io dashboard, ready to view.
That's the whole flow — you authenticate with BCC Altofonte e Caccamo, not with us, and the ~EUR 3/month subscription covers the connection.
Access your data
After a connection exists, developers can optionally read it programmatically. On the Developers page, create an API key and export a credentials.json — this bundles the API key together with your private decryption key. Then 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 system zero-knowledge.
Do I need certificates or a developer agreement with BCC Altofonte e Caccamo?
No. open-banking.io is certificate-free. You approve access on the bank's consent screen; no eIDAS certificate or direct bank onboarding is required.
Can the CLI connect my BCC Altofonte e Caccamo account?
No. The CLI and SDK only read or sync connections that already exist. Linking BCC Altofonte e Caccamo is always done in the dashboard.
How long does my consent last?
Up to 180 days, after which you re-approve access with BCC Altofonte e Caccamo to keep syncing.
Start at https://open-banking.io.