Intesa Sanpaolo Private Banking API & Open Banking

Intesa Sanpaolo Private Banking (BIC FIBKITMMXXX) serves Italian private clients, and open-banking.io lets you reach that account data without wrestling with PSD2 certificates or a bank sandbox. It is a zero-knowledge service covering 2,600+ EU and UK banks: your figures are decrypted on your own device with a key only you hold, so nobody else — not even open-banking.io — can read them. Personal accounts are supported, and each authorisation runs for up to 180 days before you renew it.

How to connect Intesa Sanpaolo Private Banking

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 cryptographic keys are generated locally on your device.
  2. In the dashboard, choose Intesa Sanpaolo Private Banking and select the personal account type.
  3. You are redirected to Intesa Sanpaolo Private Banking's own secure login and consent screen, where you approve access under PSD2.
  4. Once approved, your accounts sync back into your open-banking.io dashboard and refresh on schedule.

Because you authorise directly on the bank's screen, your credentials never touch open-banking.io.

Access your data

Reading the data programmatically is an optional step you take after the connection above exists. On the Developers page, create an API key and export a credentials.json — this bundles the API key together with your private decryption key. From there you can 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. The CLI and SDK only read and sync connections that already exist — they cannot create one. An API key on its own returns nothing but ciphertext without your private key.

At around EUR 3/month, you skip the eIDAS certificates and lengthy TPP onboarding that a direct PSD2 integration would demand.

Does open-banking.io see my Intesa Sanpaolo Private Banking data?

No. It is zero-knowledge and stores only your public key; decryption occurs on your device.

Can I connect using the CLI or an API key?

No. Connecting is done in the dashboard by approving on the bank's consent screen. The CLI and API keys only read existing connections.

How long does my authorisation last?

Up to 180 days per PSD2 consent, after which you re-approve access to keep syncing.

Start at open-banking.io.