Bankhaus E. Mayer Open Banking & API Access

Bankhaus E. Mayer (BIC BKMADE61XXX) is a German private bank, and open-banking.io gives you a single, standards-based way to reach both its business and personal accounts. Instead of scraping statements or wrestling with PSD2 certificates, you approve access once and let your balances and transaction history flow into a dashboard that only you can decrypt. open-banking.io covers 2,600+ EU and UK banks, so Bankhaus E. Mayer sits alongside the rest of your financial stack under one login.

The defining trait is privacy. open-banking.io is zero-knowledge and certificate-free: encryption keys are generated on your own device, and the service stores only your public key. Everything you see is unlocked locally with a key that never leaves you.

How to connect Bankhaus E. Mayer

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 keys are created locally in your browser, so open-banking.io can never read your data.
  3. In the dashboard, search for Bankhaus E. Mayer and choose the account type you need — business or personal.
  4. You are redirected to Bankhaus E. Mayer's own secure login to approve access (standard PSD2 consent). Your credentials go only to the bank.
  5. Once approved, your Bankhaus E. Mayer accounts sync into your dashboard. Consent lasts up to 180 days, after which you simply re-approve on the bank's screen.

Access your data

After the connection exists, developers can optionally read it programmatically. 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 every response is decrypted locally with your key. An API key alone only ever returns ciphertext, which is what keeps the model zero-knowledge. Note the CLI and SDK only read and sync existing connections — the connect step above always happens in the dashboard.

All of this runs from roughly EUR 3/month.

Do I need an eIDAS or PSD2 certificate?

No. open-banking.io is certificate-free. You authorize Bankhaus E. Mayer directly on its consent screen — no TPP certificate setup required.

Can open-banking.io see my Bankhaus E. Mayer transactions?

No. Data is encrypted with keys held only by you. The service stores your public key and ciphertext, and decryption happens on your device.

How long does access to Bankhaus E. Mayer last?

Up to 180 days per consent. When it expires, re-approve on the bank's login to continue syncing.

Start at https://open-banking.io.