iBanFirst API Access & Open Banking Data in the EU

iBanFirst is built around cross-border payments and multi-currency accounts, but getting a clean, programmatic view of your own balances and transactions usually means wrestling with bank portals or exports. open-banking.io gives you a simpler path: a single dashboard that links your iBanFirst accounts through regulated PSD2 open banking and keeps every byte of that data encrypted with a key only you hold.

Because the service is zero-knowledge and certificate-free, you never upload an eIDAS certificate or hand raw credentials to a third party. Your encryption keys are generated on your own device, and open-banking.io's servers only ever store your public key — they cannot read or decrypt what syncs in.

How to connect iBanFirst

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 keys are created locally, in your browser, at this moment.
  2. In the dashboard, search for iBanFirst (BIC FXBBBEBBXXX) and choose the account type you hold — iBanFirst supports both business and personal accounts.
  3. You are redirected to iBanFirst's own secure login to approve access. You grant PSD2 consent directly on the bank's screen; open-banking.io never sees your login.
  4. Your accounts sync back into the dashboard. Consent lasts up to 180 days, after which you simply re-approve on iBanFirst's side.

Access your data

Once iBanFirst is connected, reading it in code is an optional developer step. From the Developers page, create an API key and export a credentials.json — this bundles the API key together with your private decryption key. With it you can run the CLI (openbanking accounts, openbanking transactions, openbanking sync) or call the REST API and SDKs.

Every request authenticates with the X-Api-Key header, and every response is decrypted locally with your own key. An API key alone only ever returns ciphertext — without your private key, the data stays unreadable, which is exactly what zero-knowledge means. The CLI and SDKs read and sync existing connections; they never connect a bank themselves.

All of this runs on the same flat pricing: around EUR 3 per month, with no per-call or per-bank fees.

FAQ

Do I need an eIDAS certificate to access iBanFirst?

No. open-banking.io is certificate-free. You connect through the dashboard and approve access on iBanFirst's own consent screen.

Can open-banking.io read my iBanFirst data?

No. It holds only your public key. Data is encrypted on your device and decrypted locally, so the servers only ever see ciphertext.

Up to 180 days per PSD2 rules. When it expires, re-approve access in the dashboard and syncing resumes.

Ready to start? Connect iBanFirst at open-banking.io.