← Back to front page

Frequently asked questions

Short, honest answers about your keys, your banks and your bill — including the parts that are less convenient than we would like.

Your key and your passphrase

Can I roll my encryption key the way I roll an API key?

Yes — but it works differently from an API key, and it is deliberately destructive.

An API key is a credential we hold, so we can mint a new one and revoke the old one in a second. Your encryption key is different: the private half is generated inside your browser and never reaches us, and we only ever hold the public half, which is enough to encrypt data for you and never enough to read it. There is nothing on our side to re-issue.

So rolling it means replacing the whole pair. Everything already stored under the old public key stays sealed to a private key that no longer exists — permanently, on every device — so you reconnect your banks and pull your history again from scratch. **Settings → Replace your encryption key** does the whole job in one step: it disconnects every bank and closes each consent at the bank, deletes the accounts, balances and transactions we hold for you, and then installs the new key. Your API keys keep working, and so do your billing history and the account itself.

You can also bring your own key rather than let us generate one. Paste a P-256 private key as JWK, PKCS#8 or PEM, or the credentials file you exported from the Developers page. Before anything is destroyed we prove that key works: our server encrypts a random value to it, and your browser has to open it again. Rolling the key needs a signed-in browser session — an API key cannot do it, by design.

The older path on the “This device doesn’t have your key” screen is still there for a key that is genuinely lost. It cannot tell a lost key from a deliberate change, so it takes the cautious route: it revokes every API key on your account, and it cannot close your bank consents, because only your browser can read their identifiers. Prefer Settings when the choice is yours.

If you would rather not do it alone, write to info@open-banking.io and we will walk you through it.

What happens if I forget my passphrase?

We cannot recover it, and that is the point of the design. Your passphrase never leaves your device — it wraps the private key held in your browser, and we never see either one.

If the key still exists on a device you can reach, unlock it there and export it from the Developers page, then import the file on the device you are locked out of. If it is gone everywhere, the data encrypted under it is unreadable for good and the only way forward is to replace the key and sync your banks again.

How do I use my account on a second device?

Sign in on the new device and it will tell you it doesn’t have your key. On a device that already works, open the Developers page and export your key file. Paste or upload that file on the new device and choose a passphrase for it — each device wraps the same key under its own passphrase.

The import is checked against the public key on your account, so the wrong file is rejected outright instead of quietly leaving the device unable to read anything.

I cleared my browser data and now the dashboard asks for my key. What do I do?

Import your key in the browser again; you can export it from the Developers page on a device where it still works. If you no longer have the key, choose “Don't have your key? Reset and start over” just below the import. That replaces the key: data encrypted under the old one becomes unreadable, your API keys are revoked so you create new ones, and you reconnect your banks and sync again.

Can you read my banking data?

No. Everything we store for you is sealed with your public key before it is written, and only the private key in your browser can open it again. Your bank login never touches us at all — you authenticate at your bank’s own site.

What we can see is the account-level metadata we need to run the service: your email, your billing state, and when a sync ran. The full architecture is on the security page.

Until you have paid for the service, we also hold the bank session identifier for up to 14 days after you connect a bank, so we can close the bank's permission if you never pay. We do not use it to read your data.

Your banks and your data

Does my data keep updating while I am logged out?

No — and that follows from the encryption rather than being a limitation we chose. The identifier we need in order to talk to your bank is itself sealed under your key, so a sync can only start where that key is available: your browser while you are signed in, your own API client, or the CLI.

Opening the app syncs automatically, you can sync on demand from the Accounts page, and you can drive it yourself with the API and SDKs.

One exception: until you have paid for the service, we keep that identifier readable for up to 14 days after you connect a bank, only so we can close the bank's permission if you never pay.

Is there a webhook or notification when new transactions appear?

No, only polling. You hold the key to your data, so we cannot see when a new transaction arrives on your account and cannot notify you about it.

How often can I sync my accounts?

As often as you like. There are call limits, but you will usually not hit them at all. Think of it as fair use.

Can you tell me when an account stops receiving new data even though everything looks fine?

No. We can’t, because we don’t hold any of your banking data unencrypted, so we cannot look inside it to notice that new transactions have stopped arriving.

Why do I have to reconnect my bank every few months?

PSD2 puts an expiry on the consent you give your bank, and most banks set it to 180 days. Once it lapses we cannot fetch anything new until you re-approve at the bank. We email you before it happens and show a banner in the app.

Reconnecting keeps everything already synced — it never starts you over.

How far back does my transaction history go?

On the first sync we ask for about two years and negotiate downwards if the bank refuses, with a floor of 90 days — the minimum PSD2 guarantees. What you actually get is the bank’s decision: some hand over several years, some stop at 90 days. You can see each bank’s consent rules on the supported banks page.

After that, every sync is incremental and additive. We never delete transactions we have already stored for you.

Which details does each transaction include, such as the payment reference or the bank’s transaction ID?

We give you everything we get from your bank. Banks are not required to share more than they do today until PSD3 is in force.

Can I remove a single account without disconnecting the whole bank?

Yes. A bank consent usually covers more accounts than you actually want. On the Accounts page you can permanently remove the ones you don’t need, and they stop counting towards your bill from the next month.

Removing an account also deletes the data imported for it, and it cannot be undone.

Pricing and billing

What does it cost?

€3 per month covers your first connected account, plus €1 per month for each additional one, VAT included. Fees are drawn from a small prepaid wallet, and part-months are prorated, so you are never billed ahead for accounts you don’t have.

You only pay for accounts with a live bank connection. Proration, auto-pay and the refundable wallet buffer are all spelled out in how billing works.

Is API access included in the price?

Yes. Server-to-server API keys are part of the plan, so your own server can fetch new transactions once a day or more often. There are some request limits, but you will rarely hit them. Create a key on the Developers page.

Can you invoice my company, also outside Denmark?

Yes. We can invoice all companies, and we support reverse charge VAT.

What happens if I disconnect everything?

The monthly fee goes to zero and the data you already have stays viewable for free.

Any unused wallet balance is still your money: write to info@open-banking.io and we refund it, free of charge. If you want the data gone as well, see deleting your account.

API keys and your account

How do I rotate an API key?

Create a new key on the Developers page, move your integration across, then revoke the old one. A key is shown once, at creation, so store it when you make it.

Replacing your encryption key from Settings leaves your API keys alone — they keep working. The older reset on the “This device doesn’t have your key” screen does revoke all of them at once, so if you have just been through that, expect to mint fresh ones. The clients that consume them are on GitHub.

Can we use open-banking.io in an app for our own customers?

Unfortunately not. We do not support onboarding new partners.

How do I delete my account and everything in it?

Settings has a danger zone that permanently deletes the lot: bank connections, accounts, transactions, balances, API keys and the public key we hold for you. You confirm by typing your email address. On the way out your browser also tells each bank to end its sharing permission — when it can. If your key isn't unlocked at that moment those permissions run out on their own instead. The key stored locally is wiped either way.

It is irreversible and there is no export afterwards, so take your CSV or PDF export first if you want to keep anything.

About the service

How long has the service been running?

Tatic ApS, the company behind open-banking.io, is five years old and has used AISP access for several years. The product was commercialised in May 2026.

Do I need a PSD2 licence of my own to use the service?

No. You do not need anything else as long as you use it on behalf of your own company, organisation or private account.

Can I use it commercially, for example as a sole trader?

Yes. It is your connection, and how you use your own data is up to you, whether that is AI, an integration with your ERP system or something else. You cannot resell the product. If you give another person access to your credentials, that is your own decision and responsibility, not ours, but we support you in owning your own data.

Still stuck?

Write to info@open-banking.io. A person reads it, and questions that come up twice end up on this page.