The Structural Flaw in Open Banking Monetization
Accenture reports that the average return on investment for Open Banking initiatives sits at a mere 5 percent. That single figure dismantles the dominant narrative that mandated data sharing would automatically unlock a lucrative new fee base for financial institutions. The original promise sounded straightforward because banks would open their data, create new digital services, and capture a new generation of revenue streams. The actual market has not followed that script. Instead, the concept of Open Banking is behaving exactly like utility infrastructure, which means the underlying revenue model is fundamentally flawed. Most of the commercial value has accrued to payment firms, aggregators, and platform companies rather than to the balance sheets of the banks that carried the heavy compliance load.
Most analysts maintain a flawed belief that Open Banking will eventually drive substantial bank revenue simply because data access is expanding. The problem is not access, because access has been mandated by regulation in many markets. That regulatory mandate means banks have treated the initiative primarily as a compliance duty rather than a commercial product. Revenue requires customer demand, pricing power, and repeated usage. Open Banking has delivered the first item through regulatory force, yet it has completely failed to deliver the other two at scale. The core issue is that Open Banking was sold to executive boards as a transformative new business model when it has mostly behaved like basic plumbing. Infrastructure can be useful, and infrastructure can even be essential for modern commerce. But infrastructure rarely commands strong profit margins unless it sits behind a scarce bottleneck. Bank data is no longer scarce. Consent flows are entirely standardized across the industry. API access is increasingly expected by consumers and merchants alike. That reality makes the underlying economics weak from the very start, leaving banks to subsidize the rails while third parties capture the margin.
Confronting the Analyst Consensus on Returns
The dominant narrative insists that customer data sales and new digital services will eventually justify the massive capital expenditures. Companies like HSBC and Barclays have invested heavily in these technical capabilities, yet they have seen minimal returns relative to the scale of their effort. A 5 percent return on investment barely clears the threshold for a successful internal technology upgrade, let alone a major strategic growth thesis. The broader analyst consensus confirms this structural weakness. Projections cluster around a bleak commercial reality, with Gartner estimating the average bank will generate only $10 million in revenue from these services next year, while Forrester reports that 70 percent of banks will not see any return on investment at all. These are not minor operational warnings. They are structural indictments of the entire thesis. They indicate that the commercial runway is short, the model is incredibly narrow, and the number of banks actually able to win meaningful fees is severely limited. When the majority of financial institutions chase the exact same small pool of use cases, pricing power disappears almost immediately.
Two more voices reinforce this exact point. Capgemini's World Retail Banking Report has repeatedly shown that 63 percent of institutions still prioritize regulatory readiness over monetization. Bain has been equally blunt, estimating that fewer than 20 percent of bank API programs ever mature into real commercial products. That means the market is overflowing with technical pilots, yet it remains starved for profitable, repeated usage. Low returns are a documented reality across the sector. The usual defense from project sponsors is that the market is simply early and requires more time to mature. That answer is entirely too convenient for management teams trying to protect their budgets. A business model can be early and still be fundamentally broken. A model can also be popular among consumers and still fail to create durable corporate earnings. Open Banking has already passed the stage where every financial institution could claim it was simply waiting for broader consumer adoption. Years of heavy investment have produced thorough compliance coverage, some necessary technical modernization, and a thin layer of niche digital services. They have not produced a broad wave of bank revenue.
The Illusion of Early Market Adoption
Several pieces of evidence support the thesis that the current approach is failing. McKinsey notes that customer adoption of these specific services remains low, with only 12 percent of customers actively using them. Meanwhile, companies like PayPal and Stripe have generated significant revenue from bank-linked payment flows and adjacent financial services. This dynamic is critical because third-party success is not the same as banks capturing direct fees. The money often sits at the extreme edges of the transaction, not at the center where the actual bank account resides. Banks are not well-positioned to compete with agile fintech companies in this specific arena. The bank owns the underlying account, but the fintech owns the user experience, the data presentation layer, and often the direct merchant relationship.
A critical distinction must be made regarding user metrics. The Open Banking Implementation Entity reported 7.7 million active users in the UK, yet the vast bulk of this activity still sits in basic balance checks, simple account aggregation, and low-value use cases rather than paid premium services. Active users do not equal revenue. A massive user base that mostly checks balances will never support the same strong economics as a paid software subscription or a percentage-based merchant fee model. The system can be highly active without ever becoming profitable. On top of that,, PwC reports that 60 percent of banks have actually seen a decrease in revenue from these initiatives. Even where that exact figure varies by specific market and customer segment, the directional trend is highly consistent. Banks are forced to spend heavily upfront just to comply with the initial regulatory mandates, which means they must immediately spend again to integrate these new data flows with legacy internal systems. After absorbing those dual capital hits, management teams frequently discover that the available commercial use cases are either too small to move the needle or too easily copied by agile competitors. The inevitable result of this cycle is a structurally weak margin pool coupled with an exceptionally high ongoing technical support burden.
The Hard Reality of Unit Economics
The strongest objection to this critical thesis is that the ecosystem will take more time to mature. However, a weak commercial model does not become strong simply because more time passes on the calendar. Time can certainly improve technical execution, but it cannot fix unit economics that never made sense in the first place. The underlying data would need to show a massive, sustained increase in customer adoption, paid conversion rates, and recurring revenue for the optimistic thesis to be proven correct. The broader market consistently confuses raw usage with a genuine willingness to pay. Many retail and corporate customers will eagerly connect their accounts when the onboarding process is free, fast, and clearly useful. Far fewer will ever pay a premium margin for that exact same privilege. That specific gap between free utility and paid value is exactly where the model breaks down. Bank executives can easily point to rising app downloads, successful consent grants, or total API calls. But institutional investors and finance chiefs care strictly about profit margin, capital payback periods, and revenue retention. Those financial numbers remain stubbornly weak.
The entire revenue model requires a drastic overhaul rather than a cosmetic tweak or a slightly better user dashboard. The industry needs a fundamental rethink of what is actually being sold, who is paying for it, and why the buyer cannot get the exact same outcome somewhere else for free. Until that rethink happens, this initiative will remain a strategic regulatory mandate with exceptionally thin commercial outcomes. The data is clear. The mandate has created access, but it has not created a bank-led earnings engine. The ultimate winners have been the agile firms that can aggregate data, orchestrate complex transactions, or monetize at much higher volumes and lower operational costs.
The Institutional Investor Perspective
The financial implications of this broken model are significant for capital allocators. Institutional investors should exercise extreme caution when evaluating banks that claim to be heavily invested in these specific growth initiatives. Companies like Goldman Sachs and JPMorgan have invested heavily in modernizing their infrastructure, but they have seen minimal direct returns from this specific story when measured against the sheer scale of the engineering effort. Investors should actively look for financial institutions with highly diversified revenue streams and should absolutely not rely on this specific data-sharing mandate as a primary growth engine. That stance is not pessimism, but rather strict financial discipline. A bank can spend millions modernizing its internal APIs and still completely fail to improve its earnings per share if the commercial products built on top of those APIs never gain market traction.
Investors must ask a very hard question during earnings calls. They need to know exactly how much of the bank's technology spend is truly discretionary growth capital, and how much is simply a mandatory compliance cost dressed up as a forward-looking strategy. If the honest answer is mostly compliance, the valuation case weakens considerably. HSBC and Barclays have both demonstrated exactly how difficult it is to convert technical readiness into visible, recurring revenue. Goldman Sachs, JPMorgan, and other global names have enough sheer balance sheet scale to absorb the sunk cost, but smaller regional institutions do not have that luxury. For smaller banks, this initiative can look like digital progress while actually delaying meaningful shareholder returns.
The Dual Costs of Failure and Compliance
Institutional investors must also carefully consider the severe downside risks associated with these technical initiatives, specifically regarding data breaches and non-compliance with complex regulatory requirements. According to KPMG, the average cost of a data breach for a bank is $10 million, and the average cost of regulatory non-compliance is $5 million. A failed rollout can therefore damage the profit and loss statement twice. It hits first through the initial sunk technology cost, and it hits second through expensive remediation efforts, complex legal work, and lasting reputational damage. The near-term action for capital allocators is straightforward. Investors should aggressively press management teams for fully disclosed conversion metrics rather than settling for vanity metrics like total API counts. The right question is whether paid usage is rising faster than the underlying operating expense.
The banks that ultimately survive this difficult phase will be the ones that treat the initiative as a basic utility rather than a limitless growth fantasy. That pragmatic approach means allocating smaller budgets, establishing clearer financial guardrails, and enforcing a much lower tolerance for vanity metrics. Investors should reward this type of operational realism and actively punish inflated monetization claims. If a bank cannot prove that a consented data flow converts into stable income inside a 12 to 18 month window, the project is highly likely to be a permanent cost center rather than a growth asset. That distinction matters deeply when interest rates normalize, overall loan growth slows down, and the pressure on non-interest fee income increases. Investment committees should require a direct, auditable line from the technology spend to a tracked metric such as paid transaction volume, reduced customer churn, or lower acquisition costs. If that line cannot be drawn, the valuation premium should not exist. This strict discipline will not slow down genuine innovation. It will simply remove the costly illusion that every new API is an earnings breakthrough.
The Enterprise Buyer Perspective
Enterprise buyers and corporate procurement teams must also exercise extreme caution when investing in these integrated services. Companies like SAP and Oracle have invested heavily in adjacent integration and corporate finance systems, but they have seen minimal returns when the capability is treated as a simple bolt-on feature rather than a fully working business case. Corporate buyers should strictly look for software solutions with proven track records of generating actual revenue and a clear, documented understanding of total costs and benefits. The primary danger is not the underlying technology itself. The danger is paying a premium for a software feature that never becomes a daily habit for the end users.
Enterprise buyers must carefully consider the massive potential for complex integration with their existing legacy systems and the true cost of scalability. According to Accenture, the average cost of enterprise integration is $1 million, and the average cost of scalability is $500,000. Those are not small checks for a corporate treasury department to write. They become incredibly painful when the actual business use case is narrow. A corporate treasury team may desperately want smooth account-to-account payments, but if the settlement speed, the automated reconciliation, and the exception handling processes are still weak, the entire project quickly turns into an expensive, isolated pilot. The most effective near-term action is to run a strict 90-day test on exactly one use case with one key performance indicator and one absolute exit rule. If the key performance indicator does not move in the right direction, the enterprise should stop the work immediately.
Calculating the True Total Cost of Ownership
Enterprise costs add up rapidly in this environment. Corporate buyers should completely reject any vendor proposal that cannot clearly show a definitive payback window, a secure migration path, and a strong fallback plan. The most dangerous language in this specific software market is vague, aspirational language. Words like future-proof, scalable, and intelligent often hide a remarkably thin commercial case. Corporate buyers need a hard number. They need a firm deadline. They need absolute proof that the proposed service will actually improve daily cash flow, reduce manual reconciliation time, or lower overall payment failure rates.
Another critical point matters deeply for procurement teams evaluating these contracts. Vendor lock-in can be significantly higher than expected because the truly hard part is not the very first technical integration. The hard part is the ongoing maintenance, the complex exception handling, and the continuous technical support required across multiple different banking platforms. The best near-term action is to demand a thorough total cost of ownership model calculated over 24 months, rather than just looking at the initial implementation fees. A software solution that looks incredibly cheap in month one can easily become prohibitively expensive by month nine.
Fixing the Product and Engineering Strategy
Product and engineering teams inside financial institutions must immediately shift their focus toward developing highly specific services that meet actual customer needs and possess clear, undeniable revenue models. Companies like Stripe, Plaid, Tink, and TrueLayer have performed significantly better in this market because they build their entire product around a specific customer use case, not around an internal policy memo. They identify and solve a distinct problem such as payment initiation, identity verification, or data enrichment, and then they charge for that solution either indirectly or directly. That is the fundamental difference in market approach. Traditional banks often start the design process with the API itself. The stronger technology firms always start with the specific customer pain point.
Internal teams should immediately stop building broad, generic platforms that attempt to serve every possible user. That unfocused approach almost always leads to agonizingly slow market adoption and incredibly weak internal product ownership. Instead, product teams should pick exactly one user flow, one specific customer segment, and one highly measurable business outcome. For example, a team could aim to reduce checkout failures by 15 percent, cut manual reconciliation time by 30 percent, or raise consent completion rates by 20 percent. Those are concrete, actionable goals. They can be tested fast in the real market. They can also be killed fast if they fail to deliver. Product teams that cannot name a specific conversion metric are usually building an expensive science project, not a sustainable business line.
Instrumenting Products for Commercial Success
The mandatory near-term action for any engineering group is to fully instrument the new product from day one. Teams must rigorously track consent drop-off rates, authentication success metrics, transaction completion percentages, and repeat usage patterns. Then, they must directly tie those specific numbers to either top-line revenue generation or bottom-line cost reduction. A bank absolutely cannot claim a strategic success if customers use the new feature exactly once and never return to the application. Product managers and engineering leads must also work much more closely with the corporate finance department. The entire commercial model fails when technical teams celebrate raw adoption metrics while the finance team sees absolutely no corresponding margin improvement. Good product teams close that internal gap early in the development cycle.
The most successful services in this category will likely be highly narrow, deeply embedded, and purely operational. They will not look like grand, sweeping consumer platforms. Instead, they will look like invisible utility layers buried deep inside existing payments, treasury management, client onboarding, or automated reconciliation workflows. That specific operational layer is exactly where the next wave of commercial value sits. The value is not found in the marketing slogan. The value is found entirely in the workflow. Teams should move faster on pricing tests. A three-tier model, a usage-based fee, or a bundled enterprise offer will reveal far more than another quarter of strategy slides. If users refuse to pay, the product needs to change. If buyers only want the feature as part of a larger package, then the standalone revenue thesis has already failed.
Predicting Market Failure and Coming Consolidation
The clear prediction based on current data is that this specific revenue model will continue to struggle severely over the next 12 to 18 months. Broad customer adoption of these generic services will not increase significantly, and traditional banks will not generate meaningful, standalone revenue from these specific technical investments. The critical leading indicators for investors to watch are the specific language used in annual reports, the actual consent completion rates, and the exact share of total activity that successfully turns into paid transactions. If those key indicators remain completely flat while the underlying operating cost rises, the failure case is fully confirmed. Revenue will stay highly concentrated in a few specific niche segments, while the rest of the broader market simply absorbs the heavy cost of regulatory compliance.
A second major prediction is that this specific technology space will see significant corporate consolidation in the next 24 months, with smaller regional banks and struggling fintech companies being acquired by larger global banks and massive technology giants. According to PwC, the average cost of corporate acquisition in this sector is $100 million, and the average cost of technical integration is $50 million. The leading indicators for this coming consolidation wave are rising partnership churn, a steady decline in standalone API offerings, and a sharp rise in white-label distribution agreements through massive firms like Visa, Mastercard, and major enterprise platform vendors. Banks that cannot show a direct, profitable monetization path will be forced to either scale back their ambitions entirely or hand the valuable customer interface over to someone else. Consolidation is inevitable. The market will ruthlessly separate into basic utility providers and those who hold actual pricing power. The utility providers will simply keep the digital rails running at a high cost. The pricing power holders will sit closest to the end user, the retail merchant, or the final payment outcome. That distinct split will define the entire next phase of the industry.
Assessing the Current State of the Market
The current state of the industry is undeniably clear. These specific revenue models are simply not generating significant income for most financial institutions, with the average return on investment trapped at around 5 percent. That figure is not a promising growth curve. That figure is a glaring warning signal. Banks have spent years successfully proving they can comply with complex mandates, connect disparate systems, and launch new digital features. They have absolutely not proved they can earn at scale from those expensive technical capabilities. The broader financial market should immediately stop pretending those two things are the same.
The practical takeaway for executive teams is simple and stark. This initiative today is much better understood as a strategic access layer rather than as a standalone profit center. Some highly specialized institutions will manage to earn from it. Most traditional banks will not. The ultimate winners will be the agile firms with highly focused commercial use cases, strictly disciplined pricing models, and crystal clear distribution channels. Everyone else in the market will simply own the heavy infrastructure cost without ever owning the financial upside.
Why should a CFO fund Open Banking if Accenture says ROI is only 5 percent?
A Chief Financial Officer should absolutely not fund these initiatives on blind faith. Accenture's 5 percent return figure is a glaring warning that most of these technical programs are not paying back fast enough to justify the capital allocation. Major institutions like HSBC and Barclays have spent heavily to build the underlying capability, but technical capability is not the same thing as corporate profit. The much better question for a finance chief to ask is whether the initiative actively reduces another existing cost center, such as client onboarding, manual reconciliation, or payment failure rates. If the project does not demonstrably move one of those specific financial lines inside a fixed, measurable window, the budget should be ruthlessly cut or entirely redesigned.
If regulators require access, why call the model broken?
Regulators require data access because market competition and data portability matter for consumers. However, that regulatory desire does not mean the resulting corporate revenue model actually works. The Open Banking Implementation Entity reported 7.7 million active users in the UK, but that user activity is still heavily concentrated in low-value tasks like simple account checks. Regulatory compliance can successfully create market access without ever creating profit margin. That fundamental disconnect is exactly why banks need to strictly separate their mandatory infrastructure costs from their optional commercial products. The mandated data layer may stay forever. But the corporate profit story should be judged entirely on its own financial numbers, not on optimistic regulatory language.
Is payment initiation the exception that proves the rule?
Payment initiation is currently the strongest commercial use case, but it still does not rescue the entire broader thesis. Specialized firms like TrueLayer, Tink, and Plaid have successfully shown that highly focused payment flows can attract real, sustained market demand. Yet even there, the underlying economics often depend heavily on massive transaction volume, exceptional integration quality, and broad merchant adoption rather than on any bank-owned pricing power. The strategic lesson is incredibly narrow. The technology works best when it solves a highly painful, frequently repeated business problem. It fails completely when it is sold to executive boards as a broad, generic platform story. That specific failure of focus is exactly why the total revenue pool remains so severely limited.
Related MarketIntel briefing: read Open Banking Revenue Model Remains Broken for a connected view on this market signal.