Access Morrow Bank via Open Banking & API | Norway

Morrow Bank is a Norwegian consumer bank offering savings and lending for personal customers. If you want your Morrow Bank account and transaction data flowing into your own tools, open-banking.io gives you a single, PSD2-compliant path to it — without certificates, sandbox paperwork or a bank integration project. One subscription reaches Morrow Bank alongside 2,600+ other European banks.

Morrow Bank exposes personal account types through open banking. There is no public BIC listed for the bank, and a granted consent stays valid for up to 180 days before you re-approve it. open-banking.io is zero-knowledge: your data is encrypted with keys generated on your own device, so the service stores only your public key and never sees a readable copy of your balances.

How to connect Morrow Bank

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

1. Sign up for open-banking.io and set your encryption passphrase. Your private decryption key is generated locally and never leaves your device.
2. In the dashboard, search for Morrow Bank and choose the personal account type.
3. You are redirected to Morrow Bank's own secure login, where you authenticate and approve access (the PSD2 consent, valid up to 180 days).
4. Control returns to your dashboard and your Morrow Bank accounts sync automatically.

That's the whole flow. You never hand credentials to open-banking.io — approval always happens on Morrow Bank's side.

Access your data

Reading Morrow 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 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. An API key alone only ever returns ciphertext — without your private key it stays unreadable, which is what keeps the system zero-knowledge. The CLI and SDK only read or sync connections that already exist; they cannot create the Morrow Bank link.

All of this runs on the standard subscription of roughly EUR 3/month.

Does open-banking.io need a certificate or licence for Morrow Bank?

No. There are no eIDAS certificates or developer onboarding forms — you approve access directly with Morrow Bank.

Can open-banking.io read my Morrow Bank balances?

No. Only your device holds the decryption key, so the service stores just your public key and ciphertext.

How long does Morrow Bank access last?

Up to 180 days per consent, after which you re-approve on Morrow Bank's login screen.

Start at open-banking.io.