Banks like HSBC generate roughly $10 million a year from Open Banking, while infrastructure vendors like Plaid scale into hundreds of millions in revenue and Visa acquires Tink for €1.8 billion. That stark contradiction exposes a fundamental truth about the market today. The Open Banking revenue model is broken for the institutions actually hosting the accounts. Although the underlying infrastructure exists and consumer usage is steadily rising, bank earnings barely move in response. The core problem is not adoption alone, but rather a severe lack of pricing power. Because Open Banking turns a historically protected customer relationship into a standardized utility, it strips away the exclusivity that typically drives profit. Utilities simply do not command premium margins unless regulation forces scarcity, and Open Banking was explicitly designed to remove that scarcity.
The Illusion of Conventional Wisdom
Most industry analysts still argue that Open Banking will inevitably become a lucrative new revenue stream for traditional banks. While that view sounds remarkably clean on paper, it completely ignores how the underlying economics actually function in practice. Major institutions like HSBC and Barclays have launched extensive Open Banking initiatives, yet their income lines remain stubbornly thin. Accenture has calculated the average revenue per user for Open Banking services at a mere $1.50 a month, which means the financial return is essentially a rounding error when set against the massive fixed costs of branch networks, compliance mandates, and technology maintenance.
The mainstream bullish case is built on a comforting but flawed premise. The assumption is that if banks expose their data and payment rails, third parties will eagerly pay for access while customers will pay for convenience. However, the actual financial flows point in the exact opposite direction. Market forecasts from Juniper Research, Grand View Research, and Research and Markets cluster between $116 billion by 2026 and $123.7 billion by 2030, projecting compound annual growth rates above 20% through the decade. Those figures describe a market that is undeniably growing, but they do not describe a market that is bank-friendly. Surging payment volume is not the same thing as bank monetization, because overall volume can skyrocket while institutional take rates stay tiny. The massive valuations of Plaid and Tink expose the real center of gravity in this ecosystem. The money flows directly to infrastructure vendors, orchestration platforms, and payment networks, bypassing the retail bank that actually owns the underlying account.
Consultancies like Forrester and McKinsey have also kept the optimism alive by framing the technology as a strategic imperative. Forrester treats API-led financial services as a reliable path to higher customer retention and lower servicing costs, while McKinsey argues that account-to-account payments can successfully pull merchants away from expensive card networks. Both of these claims can be entirely true at the same time and still fail to rescue bank economics. A bank can become highly relevant to a specific payment flow and still be compensated like a basic utility. That is the ultimate trap for traditional financial institutions, as the broader market keeps confusing strategic relevance with actual financial control.
Weighing the Hard Evidence
The empirical evidence against the bullish thesis keeps stacking up across multiple dimensions. McKinsey has noted that only 12% of customers have actually used Open Banking services, which immediately creates a structural problem. Low baseline usage caps potential revenue long before pricing power is even discussed. If almost nine in ten customers never touch the service, the monetization ceiling stays permanently low regardless of the underlying technology.
The UK market itself provides a second critical data point. Open Banking Limited reported more than 11.1 million active users and 31.1 million payments in March 2024. Those are substantial numbers that prove the technical rails are functioning exactly as intended, yet they do not prove bank profitability. System activity and institutional profit are not the same thing. A financial network can process tens of millions of payments and still produce only modest, incremental income for the bank that hosts the originating account.
A third piece of evidence comes directly from the regulator rather than market cheerleaders. The UK Financial Conduct Authority has repeatedly shown through its consumer research that awareness and repeat use remain highly limited, with only a minority of adults reporting direct use of Open Banking tools. This dynamic matters deeply because revenue cannot outrun consumer habit. If users do not return to the ecosystem regularly, the service never builds the necessary frequency that supports meaningful fee income. A low-frequency product simply cannot carry bank earnings in any material way.
The contrast with dedicated payment platforms makes the structural deficit clear. PayPal produces tens of billions in annual revenue, and Stripe recently crossed $1 trillion in annualized payment volume. Those businesses earn their massive valuations by sitting directly in the monetization path and controlling the transaction experience. Open Banking banks do not control that path. In most cases, they serve merely as the underlying plumbing. While plumbing gets used every single day, it rarely gets paid like a platform.
Visible Warning Signs
The warning signs regarding this revenue disconnect are highly visible in both product strategy and corporate financial reporting. First, many legacy banks still treat Open Banking primarily as a compliance layer dressed up as digital innovation, which creates deep internal confusion. Product teams frequently celebrate API launches, developer portals, and pilot partnerships, but very few can point to durable, recurring fee income. If a software program cannot demonstrate direct earnings after several budget cycles, it is not a true business line. It is simply a cost center attached to a press release.
Second, the underlying economics keep getting compressed by market forces. As more banks standardize their APIs, technical differentiation drops to zero. As more third parties aggregate consumer data, the bank loses total control over the customer relationship. On top of that,, as more regulators enforce mandatory access, artificial scarcity falls again. Open Banking is fundamentally being built on open rails, and open rails inherently reward transaction volume rather than exclusivity. That reality serves as a stark warning for any chief financial officer who expects premium pricing from standard access.
Third, the industry is caught in a dangerous timing trap. The longer executives wait for a magical monetization breakthrough, the more obvious the structural problem becomes to outside observers. Revenue is clearly not catching up to usage, which means usage growth often masks fundamentally weak unit economics. Building a larger data pipe does not solve the problem of a narrow profit margin.
Fourth, the product narrative is getting cleaner while the profit story stays remarkably muddy. Banks can now easily showcase API uptime, app installs, and connected accounts on their investor decks. However, none of those metrics answer the one question that actually matters to markets: how much cash does each active user generate after direct costs are subtracted? Until that specific question is answered clearly, Open Banking remains a narrative asset rather than an earnings engine.
Analyzing the Current State
Current Open Banking revenue remains far too small to matter at most large financial institutions. HSBC's Open Banking revenue has been described at around $10 million per year, which is practically invisible when set against the bank's broader global income base. Barclays faces the exact same structural problem. The service may be strategically important for customer retention, data capture, and facilitating payment flows, but it is not meaningfully moving group earnings in any positive direction.
The persistent gap between system activity and actual income is the clearest signal of market failure. Banks can report endless partnerships, developer sign-ups, and payments initiated through account-to-account rails, but that activity still does not produce the kind of recurring fee base that supports a major profit engine. Accenture's calculation of $1.50 in monthly revenue per user sits at the very center of the problem. At that microscopic level, even massive mainstream adoption does not fix the underlying business model because the fundamental math is simply too thin.
Consequently, Open Banking has become a classic case of strategic importance completely divorced from financial substance. That disconnect explains why so much of the bullish language sounds highly persuasive in white papers, yet so little of it ever shows up in audited profit and loss statements.
The current state of the market also explains why annual reports remain so cautious. Banks willingly mention digital participation, account aggregation, and payment initiation in their strategic overviews, but they rarely isolate Open Banking as a separate, distinct income line. That silence is highly revealing. If an API program were actually producing material fees, management teams would highlight it aggressively to analysts. Instead, the financial disclosures stay broad and the unit economics stay hidden. The total lack of line-item detail is itself a glaring signal to the market.
Investor Implications
Institutional investors should immediately treat Open Banking as a disclosure issue rather than a growth story. Banks like HSBC and Barclays can talk endlessly about digital engagement and API activity, but investors need to demand hard evidence of revenue conversion. Goldman Sachs has estimated returns on Open Banking initiatives at roughly 5%, which is exceptionally weak when compared with the heavy capital, compliance, and execution risk involved. Generating a low return on a small base is not a viable corporate strategy. It is a warning that the market may be rewarding narrative over actual cash flow.
Near-term action for analysts is straightforward. Investors should demand explicit line-item reporting on active users, cost per active user, API monetization, and payment initiation income. They should also aggressively test management claims against peers that actually monetize transaction flow. Plaid, despite not being a chartered bank, has scaled into hundreds of millions in annual revenue precisely because it sits inside the transaction journey. Visa and Tink show the exact same pattern of value capture. Financial value accrues to the software layers that control routing, authentication, and payments, not to the institution that merely opens the checking account. Investors who ignore that critical split will keep overpaying for bank-led Open Banking stories.
The necessary next step is strict portfolio discipline. Investors should stop underwriting Open Banking as if it were a standalone earnings driver and start modeling it as a basic support function with minor optional upside. That means directly comparing the capital spent on APIs, partner programs, and security infrastructure with returns from wealth management, credit cards, SME lending, or traditional payments bundles. If HSBC can point to roughly $10 million in Open Banking revenue while still carrying the massive fixed cost of complex infrastructure, the return profile is simply too weak to justify any market enthusiasm. Capital follows cash, not slogans.
A sharper screening mechanism is already available. Investors should ask whether any bank can show Open Banking revenue per active user above $3 a month within the next two reporting cycles. If the answer is no, the market has already been told exactly what the revenue ceiling looks like. That question is simple enough for quarterly earnings calls and hard enough to separate actual substance from corporate spin.
Enterprise Buyer Implications
Enterprise buyers should remain highly skeptical when a bank pitches Open Banking as a unique revenue advantage or a proprietary partnership benefit. Companies like SAP, Oracle, and large corporate treasury teams care primarily about settlement speed, reconciliation quality, and total cost per transaction. They do not care about bank slogans or API portals. If a bank cannot explicitly show lower failure rates, lower fraud rates, or lower operating costs than existing rails, the Open Banking offer is just another expensive integration project. Stripe has successfully turned payment operations into a repeatable commercial product, and Adyen reported net revenue of about €1.9 billion in 2024. Those companies understand a basic rule of B2B commerce: buyers pay for measurable performance, not for basic access alone.
The near-term action for corporate buyers is to force a strict 90-day proof-of-value test before authorizing any wider rollout. The test should directly compare Open Banking payment flows against traditional card rails, ACH, and existing treasury connectors. Procurement teams should track failed payments, time to settlement, manual reconciliation effort, and total cost per transaction. If the Open Banking route does not definitively beat the status quo on at least two of those core measures, the deal should stop immediately. Buyers should also insist on strong exit rights and data portability clauses, because the seller's enthusiasm is never a valid substitute for commercial proof.
Procurement teams should also treat bank-branded Open Banking offers as just one bid among several competitors. A treasury leader at a large retailer or software company should ruthlessly compare a bank offer with Stripe, Adyen, and direct bank connectivity layers. That direct comparison changes bargaining power incredibly fast. If a traditional bank cannot beat a modern payment provider on failed-payment rates, or a treasury platform on reconciliation speed, it should not win the corporate mandate. The market has definitively moved from novelty to utility, and utility gets benchmarked.
Buyers should ask for a single, thorough scorecard before signing any contract. The scorecard should include settlement time in minutes, exception rates, manual reconciliation hours saved, and implementation cost in pounds or euros. If the bank cannot produce that scorecard, the buyer should walk away. Open Banking is far too often sold on theoretical future value, whereas enterprise finance teams require concrete present value.
Product and Engineering Team Implications
Product and engineering teams inside banks should stop treating Open Banking as a standalone income line and start treating it purely as a distribution channel. Revolut passed 40 million customers in 2024, and N26 crossed 8 million. Those figures matter deeply because they show exactly where scale lives in modern finance. Scale lives in rapid customer acquisition, high product frequency, and clear daily use cases. It absolutely does not live in a bank-branded API portal with no paying audience. Product teams at HSBC and Barclays should not chase vanity metrics such as endpoint count or developer sign-ups. Instead, they should chase paid usage and gross margin per transaction.
The near-term action for technical leaders is to cut weak endpoints and price one premium service properly. That means deliberately choosing a single use case with obvious willingness to pay, such as instant account verification, fraud screening, or payment initiation for business clients. It also means measuring gross margin by specific routing path, not by broad product slogan. If a technical team cannot prove that one Open Banking feature creates more financial value than it costs to maintain, it should be retired or folded into a broader paid service. Product teams win by shipping features that customers actually pay for, not by multiplying technical interfaces.
Engineering leaders need a much sharper operating model. Every single Open Banking endpoint should have a specific cost tag, a latency target, and a revenue target. That framework gives teams the necessary discipline to kill dead traffic fast. A route that drives heavy server traffic but zero fee income is not a strategic asset. It is simply technical debt with a corporate logo on it. Teams should also strictly separate regulated access work from monetized product work. If both sit inside one unified roadmap, the mandatory compliance layer will keep starving the pricing layer of necessary resources.
The most practical near-term move is to build one paid use case with a hard service level agreement. Instant verification for SME onboarding is one strong candidate, while payment initiation for business customers is another. Both are easy to measure, easy to price, and easy to compare with legacy rails. If neither can clear a strict margin hurdle inside two quarters, the engineering team should stop expanding the surface area and start shrinking it aggressively.
Strategic Predictions
First prediction: by the end of 2026, direct bank revenue from Open Banking will still account for less than 1% of retail fee income at most large UK banks. The leading indicators for this outcome are already highly visible. API traffic will keep rising much faster than monetized users, while corporate marketing language will shift away from revenue generation toward compliance and retention. Bank boards will keep asking for unit economics because those unit economics will remain fundamentally weak. The service will stay highly useful to consumers, but that usefulness will not translate into meaningful bank profit.
Analysts should watch three specific indicators to confirm that path. The first is the persistent gap between connected users and paying users. The second is the continuation of low ticket sizes, especially in payment initiation flows. The third is the total absence of any separate revenue line in major bank annual reports. If HSBC, Barclays, and similar tier-one banks still avoid clear Open Banking fee disclosure by 2026, the market will have admitted the truth without saying it aloud.
Second prediction: by mid-2027, the financial value pool will shift even further toward infrastructure vendors and payment orchestration players. Tink-style platforms, Plaid-style connectors, and dominant network operators such as Visa and Mastercard will capture the entire commercial middle. The leading indicators here are contract structures rather than press headlines. Watch closely for more paid treasury integrations, more premium API tiers, and more bank partnerships that bundle Open Banking inside much larger payments or data products. That shift represents the market admitting the truth. Open Banking works best as an enabling layer, not as a standalone bank profit engine.
The leading signal for that second shift will be pricing mechanics. If banks begin charging significantly more for fraud checks, verification calls, or premium routing, the market is already conceding that the original free-access model did not pay. If those new fees appear exclusively inside broader platform deals rather than as standalone Open Banking revenue, the capture problem has not changed at all. The real money will still sit with the software layer operating above the bank.
Why should a CFO fund a service that returns only $1.50 per user a month?
Because the number itself tells the entire story. Accenture's $1.50 monthly figure leaves incredibly little room after accounting for compliance, security, developer support, and basic uptime costs. HSBC-style revenue near $10 million a year simply does not offset platform spend at group scale. A CFO should logically treat Open Banking as a thin-margin support rail unless a specific, targeted service shows clear fee capture. The near-term move is to ring-fence all API spending and demand a strict per-user contribution margin report at the very next budget cycle.
Does Open Banking create enough consumer value to justify forced access rules?
Consumer value definitely exists, but consumer value and bank revenue are entirely different things. Open Banking Limited reported 11.1 million active users in March 2024 alongside 31.1 million payments, so the service is undeniably real and functioning. However, the FCA's consumer research still shows limited repeat use. That means the regulatory case is fundamentally about market competition and data portability, not about generating bank profit. Regulators should absolutely keep access rules in place, but they should not expect those rules to magically turn legacy banks into premium platforms. The near-term action is stricter financial disclosure, not looser technical enforcement.
Can premium APIs or fee-based partnerships fix Open Banking monetization?
This is only possible if the bank controls a genuinely scarce asset, and most simply do not. Plaid reached hundreds of millions in annual revenue because it sells broad connectivity at scale, and Visa paid €1.8 billion for Tink because intelligent routing and orchestration have clear, measurable value. A traditional bank cannot simply add a new fee and expect enterprise buyers to accept it blindly. Enterprise clients compare every single routing option against Stripe, Adyen, and legacy rails. If the bank's API is slower, pricier, or harder to integrate, the market will simply route around it.
A CFO or regulator should ask one final, clarifying question: what actually changes if a competitor offers the exact same access at a lower cost? In the Open Banking ecosystem, the answer is usually nothing. That is exactly why premium pricing stays incredibly fragile. The near-term action is to aggressively price only the specific services that save time, reduce fraud, or shorten settlement. Everything else should remain a basic utility.
Related MarketIntel briefing: read Open Banking's Revenue Model Was Broken Before It Launched for a connected view on this market signal.