Merck Finck Open Banking and API Access Guide

Merck Finck, the Munich private bank (BIC MEFIDE21XXX), holds both business and personal accounts under PSD2 open-banking rules. With open-banking.io you can bring that account data into one place — and, if you build software, read it programmatically — without certificates, bank-specific integrations, or handing anyone your credentials. Everything is decrypted on your own device with a key that never leaves it.

How to connect Merck Finck

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 open-banking.io and set your encryption passphrase. Your keys are generated locally, so only you can ever unlock your data.
  2. In the dashboard, search for Merck Finck and choose the account type you hold — business or personal.
  3. You are redirected to Merck Finck's own secure login, where you approve access on the bank's consent screen.
  4. Your accounts and transactions sync back into your dashboard automatically.

Each consent lasts up to 180 days, after which you simply re-approve on Merck Finck's site to keep the connection live.

Access your data

Reading Merck Finck data in code is an optional step that comes after you have connected the bank. 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 directly. Requests authenticate with the X-Api-Key header, and every response is decrypted locally with your own key. The tooling only reads and syncs the connection you already made — there is no connect command.

Because open-banking.io is zero-knowledge, its servers hold only your public key. An API key alone returns ciphertext; without your private key, nobody — not even open-banking.io — can read your Merck Finck data. All of this is included for around EUR 3 per month.

Do I need a developer certificate for Merck Finck?

No. open-banking.io is certificate-free. Approval happens on Merck Finck's own login, and setup takes minutes.

Can open-banking.io see my account balances?

No. Data is decrypted only on your device with your private key. The service stores encrypted data and your public key.

How long does access to Merck Finck last?

Up to 180 days per consent. When it expires, re-approve on Merck Finck's consent screen to renew.

Start at open-banking.io.