MKB Mittelstandskreditbank API Access & Open Banking

Reading account and transaction data from MKB Mittelstandskreditbank no longer means running your own PSD2 gateway or maintaining eIDAS certificates. open-banking.io gives you a single, certificate-free path to MKB Mittelstandskreditbank (BIC GENODEF1MKB) covering both business and personal accounts, with every payload decrypted on your own device using a key only you hold.

The service is zero-knowledge by design: your encryption keys are generated locally, and open-banking.io servers only ever store your public key. That means the platform can move ciphertext for you but can never read your MKB Mittelstandskreditbank balances or statements.

How to connect MKB Mittelstandskreditbank

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 an open-banking.io account.
  2. Set an encryption passphrase; your private and public keys are generated right there on your device.
  3. In the dashboard, search for MKB Mittelstandskreditbank and choose the account type you need — business or personal.
  4. You are redirected to MKB Mittelstandskreditbank's own secure login and consent screen, where you approve access under PSD2. Consent can run for up to 180 days before you re-authorise.
  5. Your approved accounts sync back into the dashboard, ready to view.

Access your data

Programmatic access is an optional step you take after the bank is connected. 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, use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API. Requests authenticate with the X-Api-Key header, and each response is decrypted locally with your own key. The CLI and SDK only read and sync connections that already exist — they cannot create a bank link. Without your private key, an API key alone returns nothing but ciphertext.

At roughly EUR 3 per month, this replaces the cost and overhead of direct bank integrations.

Is a certificate or eIDAS setup required?

No. open-banking.io is certificate-free — you authenticate directly on MKB Mittelstandskreditbank's consent screen.

Can open-banking.io see my MKB Mittelstandskreditbank data?

No. It is zero-knowledge and holds only your public key, so it can never decrypt your data.

Which account types are supported?

Both business and personal MKB Mittelstandskreditbank accounts, with consent lasting up to 180 days.

Start at open-banking.io.