Frankfurter Bankgesellschaft API Access & Open Banking

Frankfurter Bankgesellschaft (BIC FBGADEF1XXX) serves private and corporate clients across Germany, and open-banking.io lets you reach that account data without wrestling with eIDAS certificates or a bank sandbox. It is a zero-knowledge, certificate-free bridge to more than 2,600 EU and UK banks: your balances and transactions are encrypted and only ever decrypted on your own device, with a key that never leaves your hands. Both business and personal Frankfurter Bankgesellschaft accounts are supported, under PSD2 consent that lasts up to 180 days before you refresh it.

How to connect Frankfurter Bankgesellschaft

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 an open-banking.io account.
  2. Set an encryption passphrase. Your key pair is generated locally on your device, so open-banking.io only ever holds your public key.
  3. In the dashboard, search for Frankfurter Bankgesellschaft and choose the account type you need — business or personal.
  4. You are redirected to Frankfurter Bankgesellschaft's own secure login to approve access on the bank's PSD2 consent screen.
  5. Once approved, your accounts sync back into the dashboard, ready to view.

That consent stays valid for up to 180 days, after which a quick re-approval keeps the connection live.

Access your data

Reading the data programmatically is an optional step you take only after the connection above exists. Open the Developers page, create an API key, and export a credentials.json — this bundles your API key together with your private decryption key. From there the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API all work the same way: requests carry your key in the X-Api-Key header, and every response is decrypted locally with your private key. The CLI and SDK only read and sync connections that already exist — they never establish one. Hold the API key without your private key and all you get back is ciphertext, which is exactly what zero-knowledge means: open-banking.io's servers cannot read your Frankfurter Bankgesellschaft data even if they wanted to.

All of this runs for roughly EUR 3 per month, with no certificate paperwork and no per-bank onboarding.

Do I need an eIDAS certificate?

No. open-banking.io is certificate-free — you connect through the standard bank consent flow with nothing to register.

Can open-banking.io see my transactions?

No. Data is decrypted only on your device with a key you alone hold; the servers store just your public key and ciphertext.

Can I connect a Frankfurter Bankgesellschaft account with the CLI?

No. Connecting is done in the dashboard via the bank's consent screen. The CLI, SDK, and API only read or sync connections you have already approved.

Ready to begin? Visit open-banking.io to connect Frankfurter Bankgesellschaft.