Every time someone links a budgeting app to their current account, or pays for something online without typing in a card number, they're using a system that wasn't designed as a convenience feature. Open banking started as a punishment a regulatory remedy aimed squarely at the UK's largest banks and the fact that it turned into one of the most useful pieces of financial infrastructure in the country is almost an accident of good design. It's also become quietly foundational to the wider UK startup ecosystem, powering far more fintech products than most people realise every time they check a balance or approve a payment.
Open banking wasn't dreamed up by a fintech founder pitching a better way to check your balance. It emerged from a UK regulatory intervention into retail banking, introduced in 2018 as a way to break the grip a small number of large banks held over customer data and, by extension, over competition in financial services. The logic was simple: if smaller providers could access the same account data as the big banks with the customer's permission they could build better products and actually compete on service rather than simply benefiting from customer inertia.
That regulatory origin is why open banking looks the way it does today. It isn't one company's app or one bank's feature. It's a standardised set of rules that every participating bank has to follow, enforced through the Financial Conduct Authority, so that a customer's data works the same way regardless of which bank they happen to use. A founder building a product on top of open banking doesn't need a separate integration deal with every bank in the country the standardisation itself is the point, and it's precisely what made rapid fintech experimentation possible in the years that followed.
The mechanics are simpler than the regulation behind them suggests. A customer chooses a service that uses open banking a budgeting app, a lender, a payments provider and is redirected to their own bank's app or website to log in as normal, using whatever security method they'd use anyway. They're then shown exactly what data is being requested and for how long, and have to actively confirm consent before anything is shared. Crucially, login details never leave the bank itself; the third-party service only ever receives the data the customer approved, not the keys to the account.
That consent isn't a one-time event, either. It's revocable a customer can pull access at any point, and the connection stops immediately. This is the part that makes open banking fundamentally different from the old workaround it replaced, where budgeting apps often asked customers to hand over their actual banking password so the app could log in and scrape data on their behalf, with none of the visibility or control built into the current system. That older approach was a genuine security liability disguised as convenience, and open banking was, in large part, a direct response to how widespread and risky it had quietly become.
The most visible use case is personal finance budgeting apps pulling in spending data automatically instead of requiring manual entry. But open banking has grown well beyond that. Lenders increasingly use it to assess affordability by looking at a customer's real transaction history rather than relying solely on a traditional credit score, which matters given that a meaningful share of UK adults struggle to access credit through mainstream scoring alone. For those customers, open banking data can paint a fuller financial picture than a credit file ever could genuine income patterns, real spending discipline, and account behaviour that a static credit score simply doesn't capture.
Payments are the other major frontier. Variable Recurring Payments, a newer capability built on open banking rails, work similarly to a direct debit but with more flexibility a provider can collect different amounts up to a limit the customer sets, with the payment settling instantly rather than following the older direct debit timetable. That flexibility is increasingly showing up in how people pay for utility bills, subscriptions, and even automatic transfers into savings, and it's opening up new product categories for startups that a rigid direct debit system never could have supported.
What began as a compliance requirement aimed at a handful of large banks now has millions of active users in the UK, and the volume of monthly payments and data connections has continued to climb year over year. The regulatory bodies overseeing the system have been explicit that the next phase isn't about proving the model works that phase is largely considered done but about how far it extends into new areas of everyday financial life, from open finance beyond bank accounts to new payment infrastructure built on the same consent-based foundation. For founders watching this space, that expansion signals where the next wave of product opportunity is likely to open up first.
None of this changes what open banking has become for the people using it: a faster, more transparent way to move and understand their own money. But the fact that it began as a competition remedy rather than a customer-first product explains a lot about why it's built the way it is standardised across providers, tightly regulated, and designed around consent rather than convenience as the first priority. The convenience came later, as a byproduct of forcing the big banks to open up.
That's a rare case of financial regulation working out better for the end user than most people who use it every day realise, and it's a useful reminder for founders building in fintech that the most durable products sometimes grow out of rules originally written for an entirely different reason.
This angle first caught my attention through a piece I came across in the Entrepreneur Plus Magazine, which traced open banking back to its origins as a competition remedy rather than a fintech innovation.