Bankhaus Max Flessa API Access & Open Banking
Bankhaus Max Flessa — better known as Flessabank — is a private Bavarian bank, and open-banking.io lets you reach its account data without wrestling with PSD2 certificates or bank-specific paperwork. The service covers 2,600+ banks across the EU and UK, and Bankhaus Max Flessa (BIC FLESDEMMXXX) is one of them. Both business and personal accounts are supported, with a single approved consent lasting up to 180 days before you renew.
Everything runs on a zero-knowledge design: your encryption keys are generated on your own device, and open-banking.io only ever holds your public key. That means the data flowing from Bankhaus Max Flessa is readable by you alone.
How to connect Bankhaus Max Flessa
Connecting happens entirely inside the open-banking.io dashboard — there is no API call, code, or key involved in this step.
- Sign up for open-banking.io and set your encryption passphrase. Your private key is created locally and never leaves your device.
- In the dashboard, search for and select Bankhaus Max Flessa, then choose whether you're linking a business or personal account.
- You're redirected to Bankhaus Max Flessa's own secure login, where you approve access on the bank's official PSD2 consent screen.
- Once approved, your accounts and transactions sync straight into your open-banking.io dashboard.
That's the whole flow — no certificates, no developer redirect, and no handling of raw credentials on our side.
Access your data
After the connection is live, developers can optionally read it programmatically. Open 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. Every request carries the X-Api-Key header, and each response is decrypted locally with your own key. An API key on its own only ever returns ciphertext — without your private key there's nothing readable. Note the CLI and SDK only read and sync connections you've already made in the dashboard; they can't create one.
All of this comes in at roughly EUR 3/month.
Is a certificate or eIDAS setup required?
No. open-banking.io is certificate-free — the dashboard flow handles PSD2 consent for you.
Can open-banking.io see my Bankhaus Max Flessa data?
No. The architecture is zero-knowledge; only your public key is stored, so decryption happens solely on your device.
How long does access last before renewal?
Bankhaus Max Flessa consent runs for up to 180 days, after which you re-approve on the bank's login screen.
Start at open-banking.io.