For banks, the continued expansion of embedded finance presents a structural shift. As financial services become less visible to end users, the operational demands placed on financial institutions increase significantly.
Payments are increasingly initiated through platforms and marketplaces that customers do not instinctively directly associate with banking services. Yet, behind these experiences sit regulated institutions responsible for ensuring transactions are executed securely and in line with evolving regulatory requirements.
Go deeper with GlobalData
Access deeper industry intelligence
Experience unmatched clarity with a single platform that combines unique data, AI, and human expertise.
While the customer relationship may shift to third parties, accountability does not. Financial institutions remain responsible for transaction execution and compliance. Though straightforward from the customer perspective, a payment initiated within a logistics platform, marketplace, or enterprise software application introduces a complex set of operational requirements. Responsibility for managing those requirements remains with the institution providing the underlying infrastructure.
With global digital payment transaction value set to reach £28.32 trillion in 2026, this distinction is increasingly significant for banks.
As financial products move into third-party environments, banks must support growing volumes of activity beyond their own channels whilst maintaining the resilience and oversight expected of regulated institutions. The ability to support embedded services now depends on technology foundations such as ISO 20022 processing and cloud-native architectures, enabling real-time execution and interoperability at scale.
Where accountability ultimately sits
As embedded finance expands, banks are increasingly delivering financial services through channels they do not own. The customer interface sits with the platform; the financial product and the associated responsibility remain with the bank. This requires institutions to manage risk, liquidity, and compliance across a growing network of third-party environments, increasing operational complexity as embedded volumes grow.
In this context, the strength of a bank’s underlying payments architecture becomes a decisive differentiator. Where systems limit performance or restrict functionality, adoption slows and the business case weakens. Over time, this constrains the bank’s ability to support new use cases, as platforms prioritise partners that can deliver at scale. By contrast, institutions with modern infrastructure can support a broader range of embedded services and are better positioned to participate in emerging ecosystems.
Operating across continuous payment flows
Unlike traditional banking channels, embedded finance does not operate within predefined processing windows. Payments can be initiated at any time across multiple platforms, creating expectations of always-on service availability.
Banks must support secure access to payments functionality and data through external applications whilst maintaining operational resilience at all times. Liquidity must be managed in real time across rails, rather than within defined processing windows. Decision-making must also keep pace in real time. Fraud and risk analysis, along with transaction and customer analytics, need to be applied as payments move, not after the event. This also increases the need for automated workflows that can manage exceptions, validations, and controls without manual intervention.
AI will increasingly act as a control layer for this shift by enabling faster, more contextual decision-making across transactions, counterparties, and environments. Standards such as ISO 20022 further strengthen this capability by enabling richer, more structured data to be used across systems. Because that data is not tied to a single environment, it can be applied more consistently as banks scale embedded use cases.
Infrastructure is influencing partner selection
As platforms become more selective, infrastructure capability is emerging as a primary factor in partner choice. Maintaining influence in the partner-bank relationship depends on whether the financial institution can meet the performance and scale expected by its partners.
Banks that can support a wider range of embedded use cases through unified, scalable platforms, rather than fragmented systems, can capture fees beyond basic processing. They can participate in more complex payment flows and support services that require real-time data, decisioning, and orchestration across multiple rails.
This also requires flexibility in how systems are deployed and scaled. Multi-cloud approaches can support this by allowing banks to distribute workloads, maintain resilience, and adapt as embedded demand grows across platforms and regions.
Competing in an embedded ecosystem
The ability to support complex payment activity at scale will become a defining differentiator as embedded finance continues to mature. Banks that can manage growing transaction volumes across multiple channels whilst maintaining operational resilience will be better placed to participate in emerging platform ecosystems.
Success will depend on more than processing payments quickly. Financial institutions that can combine real-time execution with flexible infrastructure across payment systems will be able to support a broader range of embedded services and strengthen relationships with platform partners. As expectations around availability and integration continue to evolve, these capabilities will play a greater role in determining which institutions expand their presence within embedded finance and which remain focused on narrower processing functions.
Nadish Lad, MD, Global Head of Product and Strategic Business at Volante Technologies
