Raiffeisenkasse Algund Open Banking & API Access

Raiffeisenkasse Algund (BIC RZSBIT21001) is a South Tyrolean cooperative bank, and open-banking.io lets you reach its account data without the usual PSD2 hurdles. There are no eIDAS certificates to buy, no bank sponsorship to arrange, and no infrastructure to run. You get a unified dashboard for balances and transactions, and — if you write software — an optional programmatic layer on top. Crucially, everything stays private: your data is decrypted on your own device with a key only you hold.

Both business and personal Raiffeisenkasse Algund accounts are supported, and each authorisation stays valid for up to 180 days before you renew it.

How to connect Raiffeisenkasse Algund

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; the service only ever sees your public key.
  2. In the dashboard, pick Raiffeisenkasse Algund from the bank list and choose the account type (business or personal).
  3. You are redirected to Raiffeisenkasse Algund's own secure login, where you approve access on the bank's PSD2 consent screen.
  4. Once approved, your accounts sync back into your dashboard, ready to view.

That's the whole flow — you authenticate directly with the bank, never handing credentials to open-banking.io.

Access your data

Already connected and want the data in your own code? On the Developers page, create an API key and export a credentials.json file — it 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 send an X-Api-Key header, and every response is decrypted locally with your private key. The API key alone only ever returns ciphertext, so open-banking.io's servers can never read your Raiffeisenkasse Algund data. Note there is no connect command — the CLI and SDK only read and sync connections you already made in the dashboard.

All of this runs for roughly EUR 3/month.

Do I need a certificate or developer account with the bank?

No. open-banking.io is certificate-free — you approve access on Raiffeisenkasse Algund's consent screen and nothing more.

Can open-banking.io see my transactions?

No. It is zero-knowledge and holds only your public key; decryption happens on your device.

How long does access last?

Up to 180 days per consent, after which you re-approve on the bank's login screen.

Start at open-banking.io.