Brandenburger Bank Volksbank API & open banking

Reading balances and transactions from Brandenburger Bank Volksbank-Raiffeisenbank doesn't have to mean chasing eIDAS certificates or standing up your own PSD2 stack. open-banking.io gives you a single, private path to your accounts at this Brandenburg an der Havel cooperative bank — covering both business and personal accounts, identified by BIC GENODEF1BRB. Everything is decrypted on your own device with a key only you hold, so the service itself never sees your statements in the clear.

How to connect Brandenburger Bank Volksbank-Raiffeisenbank

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 open-banking.io and set an encryption passphrase. Your key pair is generated locally on your device; only the public key ever leaves it.
  2. In the dashboard, choose Brandenburger Bank Volksbank-Raiffeisenbank and select the account type you want to link — business or personal.
  3. You're redirected to Brandenburger Bank's own secure login and consent screen, where you approve access directly with the bank (standard PSD2 authorisation).
  4. Your approved accounts sync back into your dashboard, ready to view. 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. Requests carry the X-Api-Key header, and every response is decrypted locally with your own key. The CLI and SDK only read and sync connections you already made in the dashboard — there is no connect command. Note that an API key alone returns ciphertext: without your private key, the data stays unreadable.

This is what zero-knowledge means in practice — open-banking.io stores only your public key and can never decrypt your Brandenburger Bank data. No certificates, no bank onboarding paperwork, all for around EUR 3 per month.

Do I need a PSD2 certificate for Brandenburger Bank?

No. open-banking.io handles the regulated connection; you just approve access on the bank's own consent screen.

Yes. Brandenburger Bank Volksbank-Raiffeisenbank supports both, and you pick the type when adding the connection in the dashboard.

How long does access stay active?

Up to 180 days per consent. When it expires, re-authorise in seconds via the bank's login.

Start at open-banking.io.