Raiffeisenkasse Passeier Open Banking & API Access

Raiffeisenkasse Passeier serves the Passeier Valley in South Tyrol as part of the regional Raiffeisen cooperative network. If you want a clean, programmatic view of your Passeier accounts and transactions, open-banking.io gives you PSD2 access without certificates, custom integrations, or handing your data to a third party. It supports both business and personal accounts (BIC RZSBIT21026), with consent valid for up to 180 days before you re-approve.

The difference from most aggregators is architecture: open-banking.io is zero-knowledge. Your encryption keys are generated on your own device, and the service only ever holds your public key. Everything you read is decrypted locally, so no server — not even open-banking.io — can see your Raiffeisenkasse Passeier balances or statements.

How to connect Raiffeisenkasse Passeier

Connecting happens entirely inside the open-banking.io dashboard — there is no API call, code, or key involved in this step.

  1. Sign up at open-banking.io and set your encryption passphrase. Your private key is created locally and never leaves your device.
  2. In the dashboard, choose Raiffeisenkasse Passeier and select the account type you hold — business or personal.
  3. You are redirected to Raiffeisenkasse Passeier's own secure login, where you approve access on the bank's PSD2 consent screen.
  4. Your accounts sync back into your dashboard, and the connection stays active for up to 180 days.

Access your data

Programmatic access is an optional step you take after the bank is connected. On the Developers page, create an API key and export a credentials.json file — this bundles your API key together with your private decryption key. From there you can use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API directly.

Requests authenticate with the X-Api-Key header, and each response is decrypted locally with your own key. An API key on its own only ever returns ciphertext — without your private key, the data stays unreadable. The CLI and SDK read and sync existing connections; they never establish one.

All of this runs for about EUR 3/month, with no certificate setup or enterprise onboarding.

Do I need a developer account to use Raiffeisenkasse Passeier?

No. Connecting and viewing accounts works in the dashboard alone. API keys are only for optional programmatic access.

Can open-banking.io see my Raiffeisenkasse Passeier data?

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

How long does access last?

Raiffeisenkasse Passeier grants consent for up to 180 days, after which you re-approve on the bank's login screen.

Get started at open-banking.io.