What Is Open Banking? And Why Apps Want to Connect

Published: October 12, 2026
📖 6 min read

A budgeting app, an accounting tool or a checkout page asks to connect to your bank account. It feels like handing over a key, and the instinct to hesitate is a reasonable one.

There are two completely different mechanisms behind that request. One is a regulated arrangement in which you never give the app your bank credentials. The other is the app asking for your actual login and using it. From your side they can look almost identical, and telling them apart is the useful skill on this page.

The regulated version, and where it exists

Open banking, in the regulatory sense, means that a licensed third party can be given permission to see your account information or to initiate a payment from your account, through a channel your bank provides for that purpose.

The important features are structural:

You authenticate with your own bank, not with the app. The consent step hands you to your bank's own screen or app. The third party never sees your banking password.

The third party is licensed and listed on a public register. Regulators publish these. Anyone can check a name against one.

The permission is scoped and time-limited, and you can withdraw it, from the app and usually from within your own bank's settings too.

Where it exists varies, and this is the part every page gets wrong by assuming one country. The European Union established the framework through its payment services regulation, requiring banks to provide access to licensed third parties with the customer's consent. The United Kingdom implemented that alongside a competition-authority order that produced its own standards and directory. Several other countries have built consumer data access regimes on different legal foundations. In the United States, the Consumer Financial Protection Bureau has worked on a personal financial data rights rule, and its implementation has been contested; the bureau's own page is the place to check what currently applies.

If you are outside the countries named here, the honest answer is that you need your own national regulator's page. The mechanism may exist under a different name, may exist without a legal mandate, or may not exist at all, and each of those produces a different answer about what protects you.

The unregulated version: screen scraping

The alternative mechanism is older and still in use. The app asks for your actual online banking username and password, logs in as you, and reads the screens.

This works, and it has three consequences.

You have given a third party your banking credentials. Whatever their security is, it is now part of your bank's security.

You may have breached your bank's terms. Many banking agreements say the customer must not share credentials with anyone, and the consequences of that clause after a fraud are worth knowing before you agree rather than after.

Your bank cannot easily distinguish that app from an attacker, because it is logging in the way an attacker would.

Sharing bank credentials with anyone is the behavior that most fraud does its hardest work to produce, which is why our article on remote access scams treats a request for login access as the point where the conversation ends.

The tell, in one line: if the connection screen ever asks you to type your bank password into the app, that is not the regulated route.

What the app can actually do with the permission

This is the reassuring part, and it is worth being precise.

Account information access lets the third party read: balances, transactions, sometimes account details. It is read-only. An information permission does not let anyone move money.

Payment initiation is a separate permission that lets a third party start a payment from your account, and each payment is authorized by you with your bank. It does not give standing access to your money; it lets a specific payment be set up for you to approve.

Neither gives the app your bank password, and neither is a direct debit or a standing authority to take money whenever they like.

The distinction between these two permissions is the one to read for on the consent screen. Most budgeting and accounting tools need only the first.

What you are actually giving up

Not money, and not access. Data.

Your transaction history is a detailed record of your life: where you shop, who you pay, what you subscribe to, your income pattern, your address changes. An information permission hands a copy of that to a company.

The questions that answer whether that is a fair trade are all in the privacy notice, and they are: what will they use it for beyond the service you signed up for, will they share it, how long do they keep it after you disconnect, and what happens to it if the company is sold.

That is a data decision rather than a money decision, and it is a legitimate reason to decline a connection even when the mechanism is sound.

How to withdraw a permission

Two places, and knowing both is the point.

In the app, which is the obvious route and depends on the app being cooperative and still existing.

In your bank, which in many implementations maintains a list of the third parties you have granted access to, with the ability to revoke. Where this exists it is the more reliable route, because it does not depend on the other company.

If you have connected apps you no longer use, that list is worth looking at once. Old permissions on services you have forgotten are the quiet version of this risk.

Five checks before connecting anything

Facts to establish, not advice about what to do with them.

  1. Does the connection hand you to your own bank to authenticate? If it asks for your bank password directly, you now know which mechanism you are in.
  2. Is the company on your regulator's public register, under the name you are looking at?
  3. Which permission is being requested, information or payment initiation?
  4. What does the privacy notice say about sharing and retention?
  5. Can you see and revoke this from inside your bank?

The fraud angle, briefly

Open banking consent screens are a template that fraud copies, because a genuine one asks you to do something that feels unusual. Every habit from our guide to verifying a message that claims to be from your bank applies here: start from the app or website you navigated to yourself, not from a link you were sent, and be suspicious of urgency around a permission request.


A standing note on sources. The regimes named here, the European Union's payment services framework, the United Kingdom's implementation, and the Consumer Financial Protection Bureau's work in the United States, are named so you can find the current text yourself. Scope and status in this area have been actively changing and we have not re-read each page for this article. No figure, limit, date or country-specific requirement is stated above, deliberately.

This is an explainer, not financial advice, and nobody here is a licensed adviser in any country.

Aron Benjamin

Leave a Comment

Scroll to Top