RSB Retail+Service Bank Open Banking & API Access

Want programmatic reach into your RSB Retail+Service Bank accounts without wrestling with eIDAS certificates or a PSD2 sandbox? open-banking.io links your RSB Retail+Service Bank profile (BIC SABUDES1XXX) to a single dashboard that covers 2,600+ European banks, then hands you clean, decrypted data whenever you need it. Both business and personal accounts are supported, and each authorisation stays valid for up to 180 days before RSB Retail+Service Bank asks you to renew consent.

The design is deliberately zero-knowledge: your encryption keys are generated on your own device from a passphrase you choose, so open-banking.io stores only your public key and can never read your balances or transactions.

How to connect RSB Retail+Service Bank

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 your encryption passphrase; your private key is created locally and never leaves your machine.
2. In the dashboard, search for RSB Retail+Service Bank and choose the account type you hold — business or personal.
3. You are redirected to RSB Retail+Service Bank's own secure login, where you approve access on the bank's PSD2 consent screen.
4. Once approved, your accounts sync back into the dashboard and stay refreshed for the length of the consent window.

That is the whole flow — you authenticate directly with RSB Retail+Service Bank, and open-banking.io only ever receives data you have explicitly authorised.

Access your data

Programmatic access is an optional step you unlock 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 call 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 — the API key alone only ever returns ciphertext. The CLI and SDK read and sync existing connections; they never create one.

All of this runs on a flat plan of roughly EUR 3/month, with no certificate purchase or bank onboarding paperwork.

FAQ

Do I need a developer account to connect RSB Retail+Service Bank?

No. Connecting is done in the dashboard by approving access on the bank's login. API keys are only needed later if you want programmatic reads.

Can open-banking.io see my RSB Retail+Service Bank transactions?

No. The service is zero-knowledge and holds only your public key. Data is decrypted on your device with a private key that never leaves it.

How long does access last?

Up to 180 days per consent, after which you re-authorise on RSB Retail+Service Bank's own screen.

Start at open-banking.io.