Niederrheinische Sparkasse RheinLippe API & Open Banking

Reaching account data at Niederrheinische Sparkasse RheinLippe (Nispa) in Wesel usually means wrestling with PSD2 certificates and sandbox paperwork. open-banking.io removes that: it links your Nispa accounts through a single dashboard and hands you clean, decrypted data — no eIDAS certificate, no bank-specific onboarding. It covers 2,600+ EU and UK banks, so RheinLippe sits alongside the rest of your institutions in one place.

Because open-banking.io is zero-knowledge, encryption keys are generated on your own device the moment you set a passphrase. The service only ever holds your public key, meaning nobody at open-banking.io — or anyone who breaches it — can read your Niederrheinische Sparkasse RheinLippe balances or transactions.

How to connect Niederrheinische Sparkasse RheinLippe

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 never leaves your browser.
  2. In the dashboard, search for Niederrheinische Sparkasse RheinLippe (BIC WELADED1WES) and choose the account type you need — business or personal.
  3. You are redirected to Nispa's own secure login and consent screen, where you approve access directly with the bank (PSD2 strong authentication).
  4. Your accounts flow back into the dashboard and begin syncing. Consent lasts up to 180 days, after which you simply re-approve on the bank's screen.

Access your data

Once a connection exists, developers can optionally read it programmatically. On the Developers page, create an API key and export a credentials.json bundle — this holds the API key and your private decryption key. From there 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 — the API key alone only ever returns ciphertext. The CLI and SDK read and sync existing connections; they never create one.

Is my Nispa data readable by open-banking.io?

No. It is zero-knowledge — servers store only your public key, so data stays encrypted until it reaches your device.

Do I need a PSD2 certificate?

No. open-banking.io is certificate-free; you authorise access on Niederrheinische Sparkasse RheinLippe's own login screen.

What does it cost?

Around EUR 3 per month for full access across all supported banks, including RheinLippe.

Start at open-banking.io.