Intesa Sanpaolo API Access & Open Banking Integration

Intesa Sanpaolo (BIC BCITITMMXXX) is Italy's largest banking group, and open-banking.io gives you a certificate-free way to reach its account and transaction data under PSD2. There are no eIDAS certificates to buy, no sandbox onboarding and no bank-side developer contract — you authorise access yourself and everything you retrieve is decrypted on your own device with a key that never leaves it.

Both personal and business Intesa Sanpaolo accounts are supported, and each consent you grant stays valid for up to 180 days before the bank asks you to re-approve.

How to connect Intesa Sanpaolo

Connecting happens entirely inside the open-banking.io dashboard — there is no API call or key involved in this step.

  1. Sign up for open-banking.io and set your encryption passphrase. Your keys are generated locally, so only you can later decrypt what syncs in.
  2. In the dashboard, search for and select Intesa Sanpaolo, then choose whether you're linking a personal or business account.
  3. You're redirected to Intesa Sanpaolo's own secure login and consent screen, where you approve access directly with the bank — open-banking.io never sees your credentials.
  4. Once approved, your Intesa Sanpaolo accounts and transactions sync into your dashboard, ready to view.

Access your data

Reading the data programmatically is an optional developer step you take after the connection above already exists. Open 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 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 refresh connections you've already made — they cannot link a new bank.

Because open-banking.io is zero-knowledge, its servers hold only your public key. An API key on its own returns ciphertext; without your private key it stays unreadable. All of this runs on the flat ~EUR 3/month plan covering 2,600+ EU and UK banks.

Do I need an eIDAS certificate for Intesa Sanpaolo?

No. open-banking.io is certificate-free — you approve access on Intesa Sanpaolo's consent screen and skip the entire QWAC/QSEAL setup.

Can open-banking.io read my Intesa Sanpaolo data?

No. Data is decrypted only on your device with your private key. The service stores just your public key and never sees plaintext.

Up to 180 days, after which Intesa Sanpaolo prompts you to re-authorise from the dashboard.

Get started at open-banking.io.