ING Luxembourg Open Banking & API Access Guide

Reaching your ING (Luxembourg) accounts no longer means wrestling with bank APIs, eIDAS certificates or PSD2 licences. open-banking.io gives individuals and developers a direct, read-only line to ING's data across the EU and UK — one of 2,600+ supported institutions — for roughly EUR 3 per month. What sets it apart is the trust model: your ING statements and balances are encrypted and only ever decrypted on your own device, using a key that never leaves your hands.

ING in Luxembourg operates under BIC CELLLULL and covers both business and personal accounts. A single consent lets open-banking.io keep those accounts in sync for up to 180 days before ING asks you to re-approve.

How to connect ING

Connecting happens entirely inside the open-banking.io dashboard — there is no code, endpoint or API key at this stage.

  1. Create an open-banking.io account and set an encryption passphrase. Your cryptographic keys are generated locally on your device the moment you do.
  2. Open the dashboard, search for ING (Luxembourg) and choose the account type you hold — business or personal.
  3. You are redirected to ING's own secure login, where you approve access under PSD2. open-banking.io never sees your banking credentials.
  4. Once ING confirms, your accounts flow back into the dashboard and begin syncing automatically.

That consent stays valid for 180 days, after which a quick re-approval on ING's screen renews it.

Access your data

Reading ING data programmatically is an optional step you take after the connection exists. 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), call the REST API, or use an SDK. Every request carries the X-Api-Key header, and each response is decrypted locally with your own key. The CLI and SDK only read and refresh connections you already made in the dashboard — they cannot create one.

Because open-banking.io is zero-knowledge, its servers hold only your public key. An API key alone returns nothing but ciphertext; without your private key, the data stays unreadable.

Do I need an ING developer or eIDAS certificate?

No. open-banking.io is certificate-free — you approve access directly on ING's consent screen.

Can open-banking.io read my ING transactions?

No. Data is decrypted only on your device with a key you alone control.

How often do I re-authorise ING?

ING's PSD2 consent lasts up to 180 days, then you re-approve in a single step.

Ready to start? Visit open-banking.io.