Bulgarian American Credit Bank Open Banking Access

Pulling account and transaction data out of Bulgarian American Credit Bank normally means wrestling with PSD2 certificates, sandbox registrations and per-institution API quirks. open-banking.io removes all of that. It is a certificate-free, zero-knowledge service covering 2,600+ EU and UK banks, and it treats Bulgarian American Credit Bank (BIC BGUSBGSF) like any other supported institution — you approve access once, and both business and personal accounts flow into a single dashboard.

The privacy model is the point of difference. Your encryption keys are generated on your own device from a passphrase you choose. open-banking.io's servers only ever hold your public key, so the data they store and sync is ciphertext they cannot read. Decryption happens locally, on your machine, with a private key nobody else holds.

How to connect Bulgarian American Credit 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 key pair is created locally at this moment.
  2. In the dashboard, search for Bulgarian American Credit Bank and choose the account type you want to link — business or personal.
  3. You are redirected to Bulgarian American Credit Bank's own secure login and consent screen, where you authenticate directly with the bank and approve access (standard PSD2 consent).
  4. Once approved, your accounts sync back into your dashboard. The consent lasts up to 180 days, after which you simply re-approve on the bank's screen.

At no point does open-banking.io — or any developer — see your Bulgarian American Credit Bank credentials; you enter them only on the bank's site.

Access your data

After a connection exists, developers can optionally read it programmatically. On the Developers page, create an API key and export a credentials.json bundling that key with your private decryption key. Then 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 own key. The API key alone returns only ciphertext — without your private key it is unreadable. The CLI and SDK only read and sync existing connections; they never create them.

All of this runs on a flat subscription of roughly EUR 3/month.

Do I need a PSD2 certificate?

No. open-banking.io is certificate-free — you only approve access on Bulgarian American Credit Bank's consent screen.

Can open-banking.io read my transactions?

No. It is zero-knowledge and holds only your public key; data is decrypted on your device.

How long does access last?

Up to 180 days per consent, then you re-approve with the bank.

Ready to start? Visit open-banking.io.