UnipolPay API Access & Open Banking (Italy) Guide

Want a clean, private route to your UnipolPay data? open-banking.io lets you link your UnipolPay accounts and pull balances and transactions on your own terms — no bank certificates to register, no eIDAS setup, and no infrastructure to run. UnipolPay (BIC UNPLIT22XXX) is covered for both business and personal accounts, with PSD2 consent lasting up to 180 days before you re-authorise.

The distinction that matters: connecting the bank is a point-and-click action in the dashboard, while programmatic access is an optional add-on for developers who want the data in scripts.

How to connect UnipolPay

Everything starts in the open-banking.io dashboard — there is no API call, code, or key involved in linking your bank.

  1. Sign up for an open-banking.io account.
  2. Set your encryption passphrase. Your key pair is generated locally on your device; only you ever hold the private key.
  3. Pick UnipolPay in the dashboard and choose the account type — business or personal.
  4. Approve on UnipolPay's own login. You're redirected to UnipolPay's secure consent screen to authorise access under PSD2 — your credentials go only to the bank.
  5. Watch your accounts sync back into the dashboard, ready to view.

That's the whole connection flow. No developer redirect, no client secret, no connect command.

Access your data

Once UnipolPay is linked, developers can optionally read the data in code. 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 use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API. Requests carry the X-Api-Key header, and every response is decrypted locally with your key. The CLI and SDK only read and sync existing connections — they never create them.

Because open-banking.io is zero-knowledge, its servers store only your public key and can never read or decrypt your data. All of this runs at roughly EUR 3/month.

FAQ

Do I need a developer account to connect UnipolPay?

No. Connecting happens entirely in the dashboard. API keys and credentials.json are only for reading the data programmatically afterwards.

Can an API key alone read my UnipolPay transactions?

No. Without your private decryption key you receive only ciphertext. Decryption always happens locally on your device.

Up to 180 days per PSD2, after which you re-approve access on UnipolPay's consent screen.

Ready to start? Head to open-banking.io.