In 2022, I argued that embedded financial services would begin dissolving the boundaries between banks and digital platforms. A few weeks ago I picked the thread back up. This is the deeper read I promised — extended here beyond the LinkedIn version with a closer look at how incumbents and challengers should sequence the work differently.
That shift is now well underway.
But the more consequential story is not boundary erosion — it is margin migration.
The numbers frame the stakes, though the cleanest ones are not close to home. The UK embedded finance market sits at roughly $26 billion in 2026, growing toward $35 billion by 2030. The figure that captures the scale of the shift is American: Bain puts US embedded finance transaction value at $7 trillion in 2026, around a tenth of all US financial transactions. I use that number as a yardstick, not a forecast for here. UK and EU data is thinner. The direction of travel matters more than the decimal point.
Those revenues will not deliver benefits evenly. They will accrue to the organisations that control the value chain.
That is no longer just an industry argument. In its first Emerging Technology Horizon Scan, the FCA describes technology platforms as "dominant intermediaries within the global financial value chain" — and sketches a near future of TradFi with protocol capabilities, where tokenisation, programmable money, and atomic settlement are absorbed into existing institutions rather than replacing them.
When the regulator reaches for the same framing, the question stops being whether this is happening. It becomes whether you are built to capture the value, or whether you provide the rails and someone else collects the fare.
The Economics Are Moving Upstream
For decades, the model was stable:
- Businesses generated transactions.
- Financial institutions monetised the financial layer.
- Interchange, credit spreads, FX margin, float income — these economics largely sat outside the operating business.
Embedded finance is reversing that dynamic.
Platforms such as Shopify and Uber have integrated payments, capital products, and wallet infrastructure directly into their ecosystems. Stripe has made financial capability programmable via APIs. Visa increasingly partners with FinTechs and Banking-as-a-Service (BaaS) providers to issue cards inside apps.
This is not confined to banking and payments. Embedded insurance is growing just as fast, with cover placed directly into the purchase journey — travel, e-commerce, mobility — priced in real time at the point of need.
These firms are not becoming banks or insurers. They are capturing the economics of activity already occurring within their platforms. That distinction matters.
Experience Is the Entry Point — Not the Strategy
Embedded finance is often justified through customer experience improvements such as frictionless checkout, contextual credit, faster payouts, and seamless journeys. All valid.
But experience is the Trojan horse.
The structural outcome is revenue diversification, increased financial liquidity, lower cost-to-serve, enhanced data for underwriting and risk, and higher switching costs.
This is not system functionality deployment. It is operating model redesign.
The Strategic Risk of Enabling Without Capturing
Many organisations already enable financial flows within their ecosystems — but do not monetise them.
- They process payments.
- They facilitate lending partnerships.
- They generate transaction volume.
Yet the financial economics sit elsewhere. With embedded finance revenue streams projected in the hundreds of billions annually this decade, that is not neutral. It is strategic leakage.
The risk is not that embedded finance fails. The risk is that competitors embed it more intelligently — and redesign switching costs in the process.
FinTech Architecture Capture Model
Across a career spanning retail and commercial banking, regulatory change, treasury operations, digital challenger architecture, and large-scale transformation, I have observed that successful embedded finance strategies follow a disciplined architecture.
- Economic Flow Mapping. Identify where financial value already moves through your ecosystem: payments, credit exposure, deposit balances, FX flows, insurance risk transfer. On the UK's first mobile-only challenger, this meant mapping every flow across lending, mortgages, payments, and collections before a single line was monetised. You cannot capture what you have not first located.
- Regulatory & Risk Boundary Definition. Clarify conduct exposure, capital implications, and operational resilience requirements. This is where the BaaS market is now being tested: sponsor banks face materially higher enforcement risk than their non-partner peers, and the Synapse collapse showed how fast a poorly bounded model can fail. The boundary is not paperwork. It is the design.
- Monetisation Architecture Design. Determine which flows to internalise, which to partner, and how capital allocation aligns with return objectives. The leverage here is real. I have seen a £20k feasibility study set the structure for £1.4m of follow-on work. Get the monetisation decision right early and it compounds. Get it wrong and you partner away the economics for good.
- Structural Defensibility Integration. Embed financial capability deeply enough to increase switching costs, data visibility, ecosystem dependency, and lifetime value. Defensibility is not a feature you bolt on. It is built when the customer would lose something real by leaving. The deeper the embed, the higher the cost of walking away.
Incumbents and Challengers Start From Different Places
The four steps above are sequenced the same way regardless of where you start. What changes is the cost of each one.
An incumbent bank usually has the economic flows already — payments, deposits, lending, FX — but they are scattered across legacy product silos that were never built to be mapped as a single value chain. Step one, Economic Flow Mapping, is therefore the expensive step. It is less a discovery exercise than an archaeology project: reconciling product P&Ls, legacy ledgers, and historic vendor contracts to find out what is actually flowing where. Once that map exists, though, steps two and three move faster — the bank already holds the regulatory permissions and balance sheet that a challenger has to build or rent.
A challenger or platform business has the opposite problem. Flow mapping is close to free — there is no legacy estate to untangle, and the data model can be designed for visibility from day one. The expensive step shifts to Regulatory & Risk Boundary Definition: building or sourcing the permissions, capital treatment, and operational resilience that an incumbent already has sitting on its existing licence. This is exactly the BaaS sponsor-bank dynamic — challengers borrowing a regulatory boundary they have not yet earned, at a cost that only becomes visible when something breaks.
The practical implication: don't import a playbook from the other side of that line. Incumbents under pressure to "move like a fintech" often skip flow mapping and go straight to monetisation design, then discover mid-build that two product lines were quietly double-counting the same FX margin. Challengers under pressure to scale often treat the regulatory boundary as a one-off legal sign-off rather than a structural design constraint — which is precisely the failure mode the Synapse collapse exposed. Know which step is expensive for you before you commit budget to the others.
Conclusion
By 2030, the redistribution of financial margin into digital ecosystems will be measurable and material.
The competitive question is no longer whether embedded finance will scale. It already has.
The question is whether your organisation is architected to capture the financial economics embedded in your value chain — or whether it will continue generating economic activity for others to monetise.
That is not a technology decision. It is a strategic one. And it is being made now.