DKB API Access & Open Banking via open-banking.io

Deutsche Kreditbank (DKB) is one of Germany's largest direct banks, and reaching its account data programmatically no longer means chasing PSD2 certificates or building against a raw bank API. open-banking.io gives you a single, certificate-free path to DKB balances and transactions across business and personal accounts, with every figure decrypted on your own device using a key only you hold.

DKB operates under BIC BYLADEM1001, and a granted consent stays valid for up to 180 days before you re-authorise — so a single approval keeps your data flowing for months.

How to connect DKB

Connecting happens entirely inside the open-banking.io dashboard — there is no API call, code, or key involved in linking the bank:

  1. Sign up for open-banking.io and open the web dashboard.
  2. Set your encryption passphrase. Your key pair is generated locally on your device; open-banking.io only ever sees your public key.
  3. Pick DKB from the bank list and choose the account type you want (business or personal).
  4. Approve on DKB's own login. You are redirected to DKB's secure consent screen, where you authenticate and grant access directly to the bank — your credentials never touch open-banking.io.
  5. Watch your accounts sync back into the dashboard, ready to view or export.

Access your data

Programmatic access 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) or call the SDK and REST API. Requests carry the X-Api-Key header, and each response is decrypted locally with your own key. The API key alone returns only ciphertext; without your private key, nobody — not even open-banking.io's servers — can read it. Note the CLI and SDK only read and sync connections that already exist; there is no connect command.

That zero-knowledge, certificate-free design is the whole point: your DKB data is yours, and the service holds nothing it could decrypt. Access to 2,600+ EU and UK banks runs about EUR 3/month.

FAQ

Do I need a PSD2 certificate to access DKB?

No. open-banking.io handles the regulated connection for you — you approve access on DKB's own consent screen, with no certificate to obtain or renew.

Can open-banking.io read my DKB transactions?

No. Everything is decrypted locally with a key only you hold. The servers store only your public key and encrypted data they cannot open.

How long does a DKB connection last?

Up to 180 days per consent. After that you simply re-approve on DKB's login to keep syncing.

Ready to start? Visit open-banking.io.