Open Banking Explained for Product Founders
Building Blocks · 9 min read ·
What open banking is, what it lets a product do with account data and payments, and how to describe it to users without overpromising.
For a long time, your financial data lived inside your bank. If you wanted a budgeting app to see it, you might hand over your bank login and hope for the best. Open banking changed that picture. It lets you, the account holder, give a third party permission to read your data or start a payment, through a secure interface, without sharing your bank password.
For founders, that opens many possibilities and a few responsibilities. This guide explains what open banking is, what a product can do with it, where regulation enters and how to describe it honestly on a launch page. It is general information; rules differ by country and you should take proper advice for your own case.
The idea in plain words
Wikipedia's entry on open banking defines it as a way for financial data to be shared between banks and third-party service providers through application programming interfaces, or APIs. Traditionally banks kept customer data in closed systems. Open banking lets customers share their information securely and electronically with other banks or authorised organisations such as payment providers, lenders and insurers.
The entry also records the debate. Proponents argue it brings transparency and control for account holders and promotes competition and innovation. Opponents argue it can create greater security risks and exposure for consumers. Both views are worth keeping in mind when you design a product: the technology gives users new power and new things to protect.
It notes that the first open banking regulations came from the European Union in 2015 and that many other countries have since adopted their own rules. In the UK, the Open Banking organisation runs a website with news, standards and reports about how the ecosystem is developing, including fraud and usage reports.
The two main things it does
Reading account information
With the customer's consent, an authorised provider can read data such as balances and transactions. Products built on this include budgeting tools, accounting packages that match payments to invoices and services that check affordability for a loan application.
Initiating payments
With consent, an authorised provider can start a payment from the customer's account directly to a recipient, without a card in the middle. This is useful for bill payments, top-ups and checkout flows where the customer approves the payment in their own banking app.
Both can be offered to the user in a clear, step-by-step consent journey: pick your bank, confirm what you are sharing, approve inside your bank's own app.
Who needs to be authorised
In many jurisdictions, accessing account information or initiating payments is a regulated activity. A firm doing so generally needs authorisation or must act under the authorisation of another firm. The detail varies, and whether a given business model needs its own licence is a legal question.
Many small products take a practical route: they use a regulated provider that already has the permissions and offers an interface for developers. The product then sits on top. If you do this, be exact in your wording about who does what. Do not suggest that you are the regulated firm if you are not, and name the provider where required. The UK financial regulator's register lets people check whether a firm is authorised, so claims about regulation are easy to verify, and any false one is easy to catch.
Designing a good consent experience
Open banking depends on informed consent. Your product's job is to make the choice clear.
Say why you want the data. "To show your spending by category" is clear. "To improve your experience" is not.
Ask only for what you need. If you only need balances, do not request transaction history.
Show what happens next. Explain that the user will be sent to their bank, approve there and be returned.
State how long access lasts. Rules may require periodic reconfirmation. Tell users when and how.
Make withdrawal easy. A visible "disconnect" control, with a plain explanation of what happens to stored data.
Never ask for bank passwords. One of the great advantages of the model is that users do not share credentials with you. Say so, and keep to it.
What to say on your launch page
Use calm, precise wording.
Good: "Connect your bank through an authorised provider. You approve access in your bank's own app, we never see your bank password, and you can disconnect at any time."
Avoid:
- "Safe as your bank" (it is not your bank).
- "Instant, guaranteed" payments where bank timings or limits apply.
- Logos of banks without permission, implying a partnership.
- Claims about coverage you cannot support, such as "works with every bank".
Say which banks or regions you support today, and update the list as it changes.
Data protection and security
Account data is personal data, often sensitive in practice. Treat it accordingly.
- Collect only what the product needs.
- Say in your privacy notice what you read, why, how long you keep it and who else sees it.
- Protect it with the controls described elsewhere in this series: access limits, encryption, logging, tested incident plans.
- Choose suppliers carefully. The UK National Cyber Security Centre's supply chain guidance stresses knowing what you depend on suppliers for and how you will respond if one fails. Your open banking provider is such a supplier.
If something goes wrong, tell affected people quickly and plainly.
Common limits and surprises
Product teams discover a few realities after launch.
- Coverage varies. Not every bank or account type is supported equally.
- Connections expire. Users may need to reconnect, so design a gentle prompt.
- Data can be incomplete or delayed. Show "last updated" times and do not over-promise real-time accuracy.
- Bank journeys differ. Some are smooth, some clunky. Test across several banks.
- Fees and pricing from providers affect your costs. Keep your own pricing page current and link to it, rather than typing figures all over the site.
Be honest about these limits in your help pages. People forgive a connection that sometimes needs refreshing if you tell them in advance.
Choosing a provider
When comparing providers, look at coverage of the banks your users have, how they handle consent and reconnection, their security posture and evidence, support quality, developer experience and transparency about costs. Ask for references. Start with a small test. The Fynora Launch developers page lists the free API and MCP server we offer for listings; the same habit of reading developer documentation applies when you evaluate a provider's.
A launch checklist
- You know whether your activity needs authorisation, and have advice in writing.
- Your wording names the regulated provider where appropriate.
- The consent screen explains what is shared, why and for how long.
- Users can disconnect easily.
- Your privacy notice describes the data you read and store.
- You list supported banks honestly and update the list.
- You test the full journey on a phone with several banks.
- Support can answer connection questions.
On this site
The developers page describes how to use the free API for listings, the categories page shows where fintech products sit and the launches page shows how others describe what they do. The contact page is the way to ask about listing a regulated product, and the submit page starts an entry.
Three example products and what they must explain
A budgeting app. Reads balances and transactions to categorise spending. It must explain that it reads but cannot move money, which categories it assigns automatically and that categories can be wrong. A short "how we use your data" note answers most worries.
An invoicing tool. Matches incoming payments to invoices. It must explain which accounts it reads, that it only looks for matching payments and how a user can stop it.
A checkout that pays by bank transfer. Initiates a payment the customer approves in their banking app. It must explain that the customer is redirected, how long confirmation takes and what happens if the payment fails or is abandoned.
In each case the explanation is short, concrete and placed where the user makes the decision, not buried in a policy. The test is whether a user could repeat back what they agreed to.
Keep one eye on change
Open banking frameworks keep evolving: new standards, new responsibilities, changes to how long consent lasts and updates to who sets the rules. The UK organisation's own news pages discuss, for example, plans for a future entity to set standards. Subscribe to your provider's and regulator's updates, review your wording whenever rules change and put a quarterly reminder in your calendar to re-read your own consent screens with fresh eyes.
Explaining it to a non-technical friend
A good final test is to explain the feature to someone who has never heard of APIs. "You pick your bank, your bank asks whether you are happy to share your balance with us, you say yes inside your bank's own app, and you can stop it whenever you like." If that sentence is true of your product, use it. If it is not, find out which part differs and say that instead.
The short version
Open banking lets customers share account data or approve payments through secure interfaces without handing over their bank password. Know whether your activity is regulated, use an authorised provider where that is the right path, design clear consent with easy withdrawal, protect the data, and describe what you do in precise, modest words.
Questions and answers
- What is open banking?
- A way for account holders to let regulated third parties access their bank data or initiate payments through secure APIs, with the customer's consent.
- Do I need to be authorised to use it?
- Accessing account data or initiating payments is typically regulated. Many products work through an authorised provider instead of becoming authorised themselves.
- What should I tell users about it?
- That they choose to connect, what data is read, that they can disconnect, and that you never see their bank password.
- Is open banking the same everywhere?
- No. Rules and standards differ by country and region, so check the current framework where your users are.
- Is it risky for users?
- Proponents say it adds transparency and control; critics point to security and misuse risks. Clear consent and good security practice are essential.