Raiffeisenbank Geiselhöring-Pfaffenberg open banking

Reading account data from Raiffeisenbank Geiselhöring-Pfaffenberg eG — the cooperative bank based in Geiselhöring, Niederbayern — usually means eIDAS certificates and a PSD2 sandbox onboarding. open-banking.io removes that entirely. It gives you consented, PSD2-grade access to your Raiffeisenbank Geiselhöring-Pfaffenberg (BIC GENODEF1GPF) balances and transactions without you ever handling a certificate, and every figure is decrypted on your own device with a key only you hold.

Whether you run a personal current account or a business account at the bank, the flow is the same, and it starts in your browser — not in code.

How to connect Raiffeisenbank Geiselhöring-Pfaffenberg

Connecting happens in the open-banking.io dashboard, not through any API call:

  1. Sign up for open-banking.io and set your encryption passphrase. Your key pair is generated locally on your device — the service only ever sees your public key.
  2. In the dashboard, search for Raiffeisenbank Geiselhöring-Pfaffenberg and choose your account type (business or personal).
  3. You are redirected to Raiffeisenbank Geiselhöring-Pfaffenberg's own secure login, where you approve access on the bank's consent screen. Your credentials stay with the bank.
  4. Your accounts sync straight into the dashboard. Consent lasts up to 180 days, after which you simply re-approve.

No API key, no endpoint, no code is involved in linking the bank — approval happens entirely on Raiffeisenbank Geiselhöring-Pfaffenberg's side.

Access your data

Once the connection is live, 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. The CLI and SDK only read and sync connections that already exist — there is no connect command.

Because open-banking.io is zero-knowledge, its servers hold only ciphertext and your public key. An API key alone returns unreadable data; without your private key it stays encrypted. All of this — certificate-free, local-decryption access — costs around EUR 3/month.

Does open-banking.io store my banking password?

No. You authenticate directly on Raiffeisenbank Geiselhöring-Pfaffenberg's own login page, so the service never sees your credentials.

Can I connect both a business and a personal account?

Yes. Raiffeisenbank Geiselhöring-Pfaffenberg supports both account types; add each as a separate connection in the dashboard.

How long does access last before I re-approve?

Up to 180 days per consent, the PSD2 maximum, after which you re-authorise from the dashboard.

Start at open-banking.io.