Raiffeisenbank Bütthard-Gaukönigshofen Open Banking API

Reaching account data at Raiffeisenbank Bütthard-Gaukönigshofen eG (BIC GENODEF1BHD) no longer means wrestling with eIDAS certificates or a bank sandbox. open-banking.io is a PSD2 aggregation service covering 2,600+ banks across the EU and UK, and this small Bavarian cooperative bank is one of them. You get a single dashboard for business and personal accounts, and the data that lands there is decrypted only on your own device with a key that never leaves it.

How to connect Raiffeisenbank Bütthard-Gaukönigshofen

Connecting happens entirely inside the open-banking.io dashboard — there is no code, endpoint, or API key at this stage.

  1. Sign up for an open-banking.io account.
  2. Set an encryption passphrase. Your key pair is generated locally in your browser; open-banking.io only ever stores your public key.
  3. In the dashboard, search for Raiffeisenbank Bütthard-Gaukönigshofen and choose the account type you need — business or personal.
  4. You are redirected to Raiffeisenbank Bütthard-Gaukönigshofen's own secure login, where you approve access on the bank's PSD2 consent screen. Consent lasts up to 180 days before you re-authorise.
  5. Your approved accounts sync back into the dashboard, already encrypted to your key.

Access your data

Programmatic access is an optional step you take after the connection exists. 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 the CLI (openbanking accounts, openbanking transactions, openbanking sync), the SDKs, or the REST API read your synced data. Every request carries an X-Api-Key header, and each response is decrypted locally with your private key. Note that these tools only read existing connections — there is no connect command, because connecting always happens through the bank's consent flow.

Because the design is zero-knowledge, an API key on its own returns only ciphertext; without your private key the payload is unreadable. That is the whole point — certificate-free, and no server that can see your balances. All of this runs for roughly EUR 3 per month.

Is a QWAC or eIDAS certificate required?

No. open-banking.io handles the regulated connection, so you never provision or manage a certificate for Raiffeisenbank Bütthard-Gaukönigshofen.

Can open-banking.io read my Raiffeisenbank Bütthard-Gaukönigshofen transactions?

No. It holds only your public key. Decryption happens on your device with a key only you possess.

Up to 180 days, after which you re-approve on Raiffeisenbank Bütthard-Gaukönigshofen's consent screen.

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