Raiffeisenkasse Sarntal API Access & Open Banking

Raiffeisenkasse Sarntal is a Raiffeisen cooperative bank serving the Sarntal (Sarentino) valley in South Tyrol. With open-banking.io you can reach its account and transaction data through one PSD2 workspace — no eIDAS certificates, no bespoke integration, and no need to touch the bank's technical stack yourself. Whether you hold a business or personal account, the connection is set up once and then kept in sync for you.

The defining trait of open-banking.io is that it is zero-knowledge. When you create your workspace, an encryption key pair is generated on your own device. The service only ever stores your public key, so the data flowing back from Raiffeisenkasse Sarntal is encrypted before it lands anywhere you don't control. Decryption happens locally, with a private key that never leaves your hands.

How to connect Raiffeisenkasse Sarntal

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 open the dashboard.
  2. Set your encryption passphrase; your key pair is generated right there on your device.
  3. Search for and select Raiffeisenkasse Sarntal, then choose your account type — business or personal.
  4. You are redirected to Raiffeisenkasse Sarntal's own secure login, where you approve access on the bank's PSD2 consent screen.
  5. Your accounts sync back into the dashboard, and stay refreshed for the duration of the consent.

Consent for Raiffeisenkasse Sarntal (BIC RZSBIT21032) can run for up to 180 days before you re-approve, so you set it and forget it for months at a time.

Access your data

Once the bank is connected, developers can optionally read the data 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. Requests authenticate with the X-Api-Key header, and every response is decrypted locally with your own key. The API key alone only ever yields ciphertext.

All of this runs at roughly EUR 3/month.

Do I need an eIDAS certificate?

No. open-banking.io is certificate-free — the platform handles PSD2 licensing so you never manage certificates.

Can open-banking.io read my Raiffeisenkasse Sarntal data?

No. It holds only your public key. Data is decrypted on your device with a private key it never sees.

Does the CLI connect the bank for me?

No. Connecting is done in the dashboard via the bank's consent screen. The CLI and SDK only read and sync connections that already exist.

Get started at open-banking.io.