PBZ API Access & Open Banking (Croatia) | open-banking.io

Privredna banka Zagreb (PBZ) is one of Croatia's largest banks, and open-banking.io gives you a certificate-free way to reach your PBZ account and transaction data under PSD2. There are no eIDAS certificates to buy and no bank-specific paperwork to file — you sign up, connect PBZ through a standard consent flow, and your data starts flowing into a dashboard that only you can decrypt. PBZ is identified by BIC PBZGHR2X, and both business and personal accounts are supported, with a consent that stays valid for up to 180 days before you renew it.

How to connect PBZ

Connecting happens entirely inside the open-banking.io dashboard — there is no API call, key, or code involved in this step.

  1. Create your open-banking.io account and set an encryption passphrase. Your keys are generated locally on your own device, so nobody else — not even open-banking.io — ever holds them.
  2. In the dashboard, choose PBZ from the bank list and pick the account type you want to link (business or personal).
  3. You're redirected to PBZ's own secure login, where you authenticate and approve access on the bank's PSD2 consent screen.
  4. Once approved, your PBZ accounts and transactions sync back into your dashboard automatically.

That's the whole flow: you authorise directly with PBZ, and open-banking.io never sees your banking credentials.

Access your data

Reading PBZ data programmatically is an optional step you take after the connection exists. On the Developers page, create an API key and export a credentials.json — this bundle holds the API key plus your private decryption key. From there you can use the CLI (openbanking accounts, openbanking transactions, openbanking sync), an SDK, or the REST API directly.

Every request sends your API key in the X-Api-Key header. Responses come back encrypted, and each one is decrypted locally with your own key. Because the service is zero-knowledge — it stores only your public key — an API key on its own returns nothing but ciphertext without your private key present.

All of this runs at roughly EUR 3/month, covering the connection, syncing, and developer access across 2,600+ supported EU/UK banks.

Do I need an eIDAS certificate for PBZ?

No. open-banking.io is certificate-free — you connect through PBZ's standard consent screen without any TPP certificate.

Can open-banking.io read my PBZ transactions?

No. Data is encrypted with keys generated on your device. The service holds only your public key and can never decrypt what it stores.

How long does PBZ access last?

A PBZ consent is valid for up to 180 days. After that you simply re-approve on PBZ's login to keep syncing.