Is Embedded Finance Turning Traditional Banks into Invisible Infrastructure?

The structural question is no longer whether banks will be pushed into the background, but who absorbs the regulatory and operational weight when the customer relationship migrates elsewhere.

The structural reconfiguration

According to projections cited by FinTech Global from The Business Research Company, the global embedded finance market is expected to grow from $94.42bn in 2025 to $115.03bn in 2026, reaching a forecast $250.95bn by 2030. The trajectory is attributed to the expansion of digital commerce ecosystems and platform-based business models, which are increasingly embedding payments, lending, insurance, and savings products into non-financial customer journeys.

George Toumbev, CCO at NatWest Boxed, frames the transition as a two-directional shift. "Banking is shifting towards embedded financial services, but embedded financial services are also shifting towards banking," he told FinTech Global. The early phase, led by fintechs, emphasized speed and product innovation. The current phase, Toumbev argues, is defined by banks contributing regulated infrastructure, operational resilience, and scalability to the embedded layer.

The implication is structural rather than rhetorical. Licensed balance sheets, KYC stacks, and supervisory relationships remain prerequisites for most embedded products. What is being reconfigured is the interface: the customer no longer enters a banking app to originate a loan, open a savings account, or select an insurance plan. The origination surface belongs to the merchant, the SaaS platform, or the marketplace.

Liability and regulatory redistribution

The relocation of the customer interface creates a layered compliance problem. When a lending product is presented inside a checkout flow, the disclosure regime, complaints handling, and conduct risk do not vanish with the bank's logo. They migrate into a multi-party arrangement involving the platform, the bank-as-TSP, and the end user. The bank retains the regulated entity status, but the platform controls the onboarding funnel, the pricing presentation, and the customer experience.

Toumbev's framing of banks combining "regulatory expertise, operational resilience and the ability to scale services" is more than a marketing statement. It is an acknowledgment that the embedded market is splitting into two tiers: licensed institutions providing balance-sheet and compliance infrastructure, and platforms providing distribution and customer data. The intermediaries between them, including API gateways, BaaS providers, and payment processors, are now the load-bearing components of the system. Supervisory frameworks, designed for direct bank-customer relationships, are being asked to govern a chain in which the bank is several contractual layers removed from the user.

The architecture that remains

Other recent developments indicate the shift is already being operationalized. PaymentsJournal reports that Square has expanded its small business suite as part of an embedded finance push, extending the platform's reach into merchant financial workflows. FF News notes that i2c has been named Most Innovative Fintech in Latin America by Global Finance Magazine, a recognition that processing infrastructure providers are being elevated within the regional stack. The Paypers reports that ING Bank Romania has launched RoPay, an instant mobile payment service for business banking customers, activated through QR code scanning from the bank's online platform.

Each of these represents a different node in the same architecture: a processor expanding upstream, a bank simplifying its own payment rails, and a fintech infrastructure provider consolidating its regional position. The pattern is not the displacement of banks. It is the absorption of banking functions into software layers that were previously external to the financial system.

The metrics that matter now are not the headline market projections. They are the supervisory outcomes of the first embedded finance conduct cases, the terms of BaaS and sponsor-bank partnerships as they come under regulatory review, and the liability frameworks that emerge when a platform's UX choices cause customer harm. The structural shift is already underway. The regulatory architecture required to govern it is not.