Kreissparkasse Euskirchen API Access & Open Banking

Kreissparkasse Euskirchen (BIC WELADED1EUS) serves the Eifel region of North Rhine-Westphalia, and open-banking.io lets you reach both business and personal accounts held there without wrestling with eIDAS certificates or a PSD2 developer programme. You get a single, tidy dashboard view of balances and transactions — and everything is decrypted on your own device with a key that never leaves it.

The service spans 2,600+ European banks, so if you also bank elsewhere, Kreissparkasse Euskirchen simply becomes one more account that syncs into the same place.

How to connect Kreissparkasse Euskirchen

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 an open-banking.io account.
  2. Set an encryption passphrase. Your key pair is generated locally on your device; open-banking.io only ever stores your public key.
  3. In the dashboard, pick Kreissparkasse Euskirchen and choose the account type — business or personal.
  4. You are redirected to Kreissparkasse Euskirchen's own secure login and consent screen, where you approve access directly with the bank (standard PSD2 consent).
  5. Your accounts sync into your dashboard, ready to view.

Consent lasts up to 180 days, after which you simply re-approve on the bank's screen to keep the connection live.

Access your data

Once the connection exists, reading it programmatically is an optional developer step. 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 you can 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 API key alone only ever returns ciphertext — without your private key, the data stays unreadable, even to open-banking.io.

This is what zero-knowledge means in practice: the servers hold your encrypted data and public key, nothing more. All of it runs at around EUR 3/month.

Do I need an eIDAS certificate?

No. open-banking.io is certificate-free — you approve access on Kreissparkasse Euskirchen's consent screen, and no QWAC or developer onboarding is required.

Can I connect both business and personal accounts?

Yes. Kreissparkasse Euskirchen supports both account types; add each one from the dashboard and approve it separately with the bank.

Can open-banking.io read my transactions?

No. Data is decrypted only on your device with your private key. The service stores ciphertext and your public key, so it cannot read your Kreissparkasse Euskirchen data.

Ready to start? Visit open-banking.io.