iBanFirst Open Banking API Access | open-banking.io

iBanFirst is a cross-border payments and multi-currency bank serving businesses across Europe, and open-banking.io lets you reach your iBanFirst account data without wrestling with PSD2 certificates or eIDAS onboarding. You sign up once, hold your own encryption key, and pull a clean feed of balances and transactions into a dashboard you control. Both business and personal iBanFirst accounts are supported, identified by BIC FXBBBEBBXXX, and each consent stays valid for up to 180 days before iBanFirst asks you to renew it.

What makes this different is the trust model. open-banking.io is zero-knowledge: the encryption keys are generated on your own device, and the service only ever stores your public key. Everything you retrieve is decrypted locally, so open-banking.io servers physically cannot read your iBanFirst statements. No bank-facing certificate, no regulated TPP status, and no infrastructure to maintain on your side.

How to connect iBanFirst

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

  1. Create an open-banking.io account and set an encryption passphrase; your keys are generated locally on your device.
  2. In the dashboard, choose iBanFirst from the bank list and pick the account type (business or personal).
  3. You are redirected to iBanFirst's own secure login, where you approve access under PSD2 consent.
  4. Your iBanFirst accounts sync back into your dashboard, ready to view.

That consent lasts up to 180 days, after which you simply repeat the approval on iBanFirst's screen.

Access your data

Once iBanFirst is connected, reading the data programmatically is an optional developer step. From the Developers page, create an API key and export a credentials.json file — 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. Every request carries the X-Api-Key header, and every response is decrypted locally with your own key. An API key on its own returns only ciphertext; without your private key, nobody — not even open-banking.io — can turn it into readable data.

All of this runs at roughly EUR 3/month, across 2,600+ supported EU and UK banks.

Do I need an eIDAS certificate for iBanFirst?

No. open-banking.io is certificate-free — you authorise access directly on iBanFirst's login screen.

Can the CLI connect my iBanFirst account?

No. The CLI and SDK only read and sync connections that already exist; connecting is always done in the dashboard.

Who can decrypt my iBanFirst data?

Only you. Decryption happens on your device with a private key open-banking.io never holds.

Start at open-banking.io.