Sparkasse Meißen API Access & Open Banking Data

Sparkasse Meißen serves the Saxon Elbland with everyday banking for households and companies alike, and open-banking.io lets you reach that account data through a single, privacy-first hub. Whether you run a Meißen-based business or manage a personal current account, you can pull balances and transactions into one place without handshaking eIDAS certificates or standing up PSD2 infrastructure yourself. Both business and personal account types are supported, keyed to Sparkasse Meißen's BIC SOLADES1MEI.

The defining trait of open-banking.io is that it is genuinely zero-knowledge. When you sign up you set an encryption passphrase, and the keys are generated on your own device — the service only ever holds your public key. Everything you later read back is decrypted locally, so no server (not even open-banking.io's) can see inside your Sparkasse Meißen data.

How to connect Sparkasse Meißen

Connecting happens entirely in 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 personal keys are created right there on your device.
  2. In the dashboard, search for and select Sparkasse Meißen, then choose the account type you want — business or personal.
  3. You are redirected to Sparkasse Meißen's own secure login, where you approve access under PSD2. Consent lasts up to 180 days, after which you simply re-approve.
  4. Your approved accounts sync back into your dashboard, ready to view.

Because approval happens on the bank's own screen, your credentials never touch open-banking.io.

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 — 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. Requests authenticate with the X-Api-Key header, and each response is decrypted locally with your own key. An API key alone only ever returns ciphertext; without your private key it stays unreadable. The CLI and SDK read and sync existing connections — they never create one.

All of this runs for roughly EUR 3/month.

Do I need an eIDAS certificate?

No. open-banking.io is certificate-free — you approve access directly on Sparkasse Meißen's consent screen and skip the entire certificate process.

Can open-banking.io read my Sparkasse Meißen data?

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

How long does access last before renewal?

Sparkasse Meißen grants consent for up to 180 days; re-approve from the dashboard when it expires.

Start at open-banking.io.