Bank für Kirche und Diakonie KD-Bank open banking
Bank für Kirche und Diakonie - KD-Bank (BIC GENODED1DKD) serves churches, diaconal organisations and their members across Germany. With open-banking.io you can reach both business and personal KD-Bank accounts through a single PSD2 connection — no eIDAS certificate, no bank-specific integration work, and no raw credentials ever leaving your device. Balances and transactions land in your dashboard already encrypted under a key that only you hold.
Because open-banking.io is zero-knowledge, its servers store only your public key. Every figure you see is decrypted locally, so the service can move your KD-Bank data without ever being able to read it.
How to connect Bank für Kirche und Diakonie - KD-Bank
Connecting happens entirely inside the open-banking.io dashboard — there is no API call, key or code involved in this step.
- Sign up for open-banking.io and set an encryption passphrase. Your key pair is generated on your own device.
- In the dashboard, pick Bank für Kirche und Diakonie - KD-Bank and choose the account type you need — business or personal.
- You are redirected to KD-Bank'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.
- Your approved accounts sync back into the dashboard, ready to view.
Access your data
Reading KD-Bank data programmatically is an optional developer step you take after the connection 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. Then use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API. Requests carry your key in the X-Api-Key header, and every response is decrypted locally with your private key. Note the CLI and SDK only read and sync connections you already approved — there is no connect command, and an API key alone returns only ciphertext.
At around EUR 3 per month, you get certificate-free, privacy-first access to KD-Bank and 2,600+ other EU and UK banks.
Does open-banking.io see my KD-Bank balances?
No. It holds only your public key. Data is decrypted on your device, so the platform never reads your accounts.
Can I connect KD-Bank from the CLI?
No. Connecting is done in the dashboard via KD-Bank's consent screen. The CLI and SDK only read or sync existing connections.
How long does my consent last?
Up to 180 days per approval, after which you re-authorise on KD-Bank's login to keep syncing.
Get started at open-banking.io.