Raiffeisenkasse Laas Open Banking & API Access

Raiffeisenkasse Laas is a cooperative Raiffeisen bank serving the Vinschgau valley in South Tyrol, Italy. With open-banking.io you can bring its account and transaction data into one privacy-first place — and, if you write code, read it programmatically afterwards. Everything is decrypted on your own device with a key only you hold, so no certificates, no eIDAS setup, and no third party ever sees your figures in the clear.

Raiffeisenkasse Laas operates under BIC RZSBIT21012 and supports both business and personal accounts. A single PSD2 consent stays valid for up to 180 days before you renew it.

How to connect Raiffeisenkasse Laas

Connecting is done entirely inside the open-banking.io dashboard — there is no API call, code, or key involved in linking an account:

  1. Sign up for open-banking.io and open the web dashboard.
  2. Set your encryption passphrase. Your key pair is generated locally on your device; open-banking.io only ever stores your public key.
  3. Pick Raiffeisenkasse Laas from the bank list and choose whether you're linking a business or personal account.
  4. Approve on Raiffeisenkasse Laas's own login. You're redirected to the bank's secure consent screen, where you authenticate directly with Raiffeisen and authorise access.
  5. Your accounts sync back into the dashboard, ready to view and refresh.

Access your data

Programmatic access is an optional step after the bank is connected. 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 your key in the X-Api-Key header, and every response is decrypted locally with your private key. The API key alone only ever returns ciphertext — without your key, the data stays unreadable, even to open-banking.io.

The whole service costs around EUR 3/month, covering 2,600+ banks across the EU and UK.

Do I need a developer account or eIDAS certificate?

No. Linking Raiffeisenkasse Laas happens in the dashboard through the bank's own consent flow. Certificates and developer credentials are never required.

Can open-banking.io read my Raiffeisenkasse Laas transactions?

No. It's zero-knowledge — it holds only your public key. Decryption happens on your device with the private key you control.

Up to 180 days per authorisation. When it expires, simply re-approve on Raiffeisenkasse Laas's consent screen to keep syncing.

Ready to start? Visit open-banking.io.