Raiffeisenbank Auerbach-Freihung Open Banking API

Pulling account data out of Raiffeisenbank Auerbach-Freihung eG — the Oberpfalz cooperative bank behind BIC GENODEF1AUO — normally means wrestling with PSD2 certificates and sandbox registrations. open-banking.io removes all of that. It is a certificate-free bridge to 2,600+ EU and UK banks, so you reach your Auerbach-Freihung accounts without a QWAC, an eIDAS seal, or a developer contract with the bank.

The service is zero-knowledge by design. Your encryption keys are generated on your own device from a passphrase only you know, and open-banking.io only ever holds your public key. Every statement, balance, and transaction from Raiffeisenbank Auerbach-Freihung is decrypted locally, so the platform's servers never see your readable financial data.

How to connect Raiffeisenbank Auerbach-Freihung

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 private key is derived on your device and never leaves it.
  2. In the dashboard, pick Raiffeisenbank Auerbach-Freihung from the bank list and choose the account type you need — both business and personal accounts are supported.
  3. You are redirected to Raiffeisenbank Auerbach-Freihung's own secure login, where you approve access on the bank's PSD2 consent screen. Your credentials go only to the bank.
  4. Your accounts sync back into your dashboard. Consent lasts up to 180 days, after which you simply re-approve on the bank's screen.

Access your data

Once a connection exists, 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 directly.

Every request authenticates with the X-Api-Key header, and each response is decrypted locally with your own key. The API key alone only ever returns ciphertext — without your private key, nobody, including open-banking.io, can read it. The CLI and SDK only read and sync existing connections; they never create one.

All of this runs at roughly EUR 3/month.

Is a PSD2 certificate required?

No. open-banking.io is certificate-free — you never need a QWAC or eIDAS seal to reach Raiffeisenbank Auerbach-Freihung.

Can open-banking.io read my transactions?

No. It is zero-knowledge and stores only your public key. Decryption happens on your device with a key only you hold.

Which account types are supported?

Both business and personal Raiffeisenbank Auerbach-Freihung accounts, with consent valid for up to 180 days per approval.

Start at open-banking.io.