Raiffeisenbank am Kulm API Access & Open Banking

Reach your Raiffeisenbank am Kulm accounts through a single, privacy-first interface. open-banking.io links to this Bavarian cooperative bank (BIC GENODEF1SPK) under PSD2, covering both business and personal accounts, so you can pull balances and transactions without juggling separate portals or arranging your own eIDAS certificate.

The design is deliberately zero-knowledge. When you register you set an encryption passphrase, and the matching key pair is generated on your own device. open-banking.io keeps only your public key, which means the service can relay your Raiffeisenbank am Kulm data but can never read or decrypt it. Everything you see is unlocked locally, by a key that never leaves you.

How to connect Raiffeisenbank am Kulm

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 open-banking.io and set your encryption passphrase (your keys are created locally at this moment).
  2. In the dashboard, choose Raiffeisenbank am Kulm and select the account type you want to link — business or personal.
  3. You are redirected to Raiffeisenbank am Kulm's own secure login, where you approve access on the bank's consent screen.
  4. Your accounts then sync back into your dashboard, ready to view.

Consent under PSD2 lasts up to 180 days, after which you simply re-approve on the bank's screen to keep the connection live.

Access your data

Programmatic access is an optional step once a connection already exists. On the Developers page, create an API key and export a credentials.json file, which bundles that API key with your private decryption key. From there you can use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API. Every request carries your key in the X-Api-Key header, and each response is decrypted locally with your private key. An API key on its own only ever returns ciphertext — readable data requires the key only you hold. The CLI and SDK read and sync existing connections; they never create one.

All of this runs for roughly EUR 3/month.

Is a certificate required?

No. open-banking.io is certificate-free — no eIDAS or QWAC to obtain or renew.

Which Raiffeisenbank am Kulm accounts are supported?

Both business and personal accounts under BIC GENODEF1SPK.

Can open-banking.io see my transactions?

No. It holds only your public key, so data stays encrypted until you decrypt it locally.

Start at open-banking.io.