Bulgarian Development Bank Open Banking & API Access

Bulgarian Development Bank is Bulgaria's state-owned development bank, and open-banking.io gives you a private, certificate-free way to reach its account and transaction data under PSD2. Both business and personal accounts are supported, identified by BIC NASBBGSF, with a single consent lasting up to 180 days before you renew it.

What makes open-banking.io different is the trust model. It is zero-knowledge: your encryption keys are generated on your own device from a passphrase only you know, and the platform stores nothing but your public key. Every figure you pull from Bulgarian Development Bank is decrypted locally, so the servers relaying your data can never read it. There are no eIDAS certificates to buy or QWAC files to manage — coverage across 2,600+ EU and UK banks is included for roughly EUR 3/month.

How to connect Bulgarian Development Bank

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 private key is derived on your device and never leaves it.
  2. In the dashboard, search for Bulgarian Development Bank and choose the account type you hold — business or personal.
  3. You are redirected to Bulgarian Development Bank's own secure login, where you authenticate and approve access on the bank's PSD2 consent screen.
  4. Once approved, your accounts sync back into the dashboard, and balances and transactions appear ready to view.

Because you approve directly on the bank's page, your credentials are only ever seen by Bulgarian Development Bank.

Access your data

Reading Bulgarian Development Bank data programmatically is an optional step you take after connecting. 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. Requests authenticate with the X-Api-Key header, and every response is decrypted locally with your key. An API key on its own returns only ciphertext — without your private key, the data stays unreadable.

Is a certificate required?

No. open-banking.io is certificate-free; there are no eIDAS or QWAC files to obtain for Bulgarian Development Bank.

Can open-banking.io see my Bulgarian Development Bank data?

No. The service is zero-knowledge and holds only your public key. Decryption happens on your device.

Up to 180 days per approval, after which you re-confirm access on Bulgarian Development Bank's consent screen.

Start at open-banking.io.