Bankhaus Rautenschlein API Access & Open Banking

Bankhaus Rautenschlein (BIC GENODEF1RTS) is a long-established German private bank, and open-banking.io lets you reach its account and transaction data without wrestling with eIDAS certificates or a bespoke PSD2 integration. You link the bank once through a guided dashboard, and everything you see afterwards is decrypted on your own device with a key that never leaves it. Both business and personal Bankhaus Rautenschlein accounts are supported, with a PSD2 consent that stays valid for up to 180 days before you renew.

The service covers 2,600+ EU and UK banks, so a Bankhaus Rautenschlein link sits alongside every other account you hold under one consistent, certificate-free setup.

How to connect Bankhaus Rautenschlein

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 an open-banking.io account.
  2. Set your encryption passphrase. Your key pair is generated locally on your device, so only you can later unlock the data.
  3. In the dashboard, search for and select Bankhaus Rautenschlein, then choose the account type you want to link — business or personal.
  4. You are redirected to Bankhaus Rautenschlein's own secure login and consent screen, where you approve access directly with the bank.
  5. Your approved accounts sync back into the dashboard, ready to view.

Because approval takes place on Bankhaus Rautenschlein's side, open-banking.io never sees your banking credentials.

Access your data

Reading the data programmatically is an optional developer step you take 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 you can use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API. Every request carries 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.

This is what zero-knowledge means here: open-banking.io stores only your public key, so its servers can never read or decrypt your Bankhaus Rautenschlein data. All of it, including the API access, runs at around EUR 3 per month.

Does connecting Bankhaus Rautenschlein need a certificate?

No. There are no eIDAS or QWAC certificates to obtain. You connect through the dashboard and approve on the bank's consent screen.

Can I use the CLI to connect my account?

No. The CLI, SDK, and API only read or sync connections you have already approved in the dashboard. There is no connect command.

Up to 180 days. After that you simply re-approve access on the bank's consent screen to keep syncing.

Ready to start? Visit open-banking.io.