SKB Bad Homburg EFG open banking and API access

Spar- und Kreditbank Evangelisch-Freikirchlicher Gemeinden eG (SKB, Bad Homburg) serves congregations, members and businesses across Germany. If you want a clean, private way to read your SKB balances and transactions in one place — or to feed them into your own tools — open-banking.io lets you link the bank without certificates, eIDAS setups or a PSD2 licence of your own.

open-banking.io reaches SKB through the shared PSD2 infrastructure that covers 2,600+ EU and UK banks. Everything is encrypted so that only you can read it: your keys are generated on your own device, and the service holds nothing but your public key. That is what "zero-knowledge" means here — the servers relay ciphertext they cannot open.

How to connect Spar- und Kreditbank Evangelisch-Freikirchlicher Gemeinden

Connecting happens entirely in 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 an encryption passphrase. Your private decryption key is created locally at this moment and never leaves your device.
  2. In the dashboard, search for Spar- und Kreditbank Evangelisch-Freikirchlicher Gemeinden (BIC GENODE51BH2) and choose your account type — both business and personal accounts are supported.
  3. You are redirected to SKB's own secure login, where you approve access on the bank's PSD2 consent screen. A single consent stays valid for up to 180 days before you renew it.
  4. Your approved accounts then sync automatically into your dashboard, ready to view.

Access your data

Reading data programmatically is an optional developer step you take after the connection above exists. 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. Note that an API key alone only ever returns ciphertext — without your private key there is nothing readable. The CLI and SDK read and sync existing connections; they never create one.

All of this runs for roughly EUR 3/month, with no certificate or bank partnership to arrange.

Does open-banking.io ever see my SKB data?

No. It stores only your public key and relays encrypted data; decryption happens on your device.

Can I connect SKB business accounts?

Yes — both business and personal account types are available for GENODE51BH2.

How often do I re-authorise?

Each SKB consent lasts up to 180 days, after which you re-approve on the bank's login screen.

Start at open-banking.io.