Banks, it’s time to decide what kind of embedded banking player you are

Embedded banking without strategic intent is expensive theatre. Lots of APIs, lots of partnership announcements, lots of pilots, but not much revenue.

And that’s the risk facing corporate banks right now.

‍Embedded banking has become a practical route into the systems where corporate clients already work: ERP platforms, treasury management systems, procurement tools, accounting software, marketplaces and vertical SaaS.

The question is not whether banks should care, but instead what kind of embedded banking player they want to become.

The portal is losing ground to the workflow

Corporate clients don’t want another place to go. They want banking inside the tools they already use to run their business. That means; payments inside ERP, liquidity inside treasury platforms, working capital inside procurement flows, reconciliation inside accounting software, and credit inside marketplaces and vertical SaaS.

Banking's evolution from something clients used to access separately, to a function that appears for them at the point of need creates both opportunities and threats.

If the client relationship sits inside someone else’s workflow, the bank risks becoming the balance sheet in the background - still important but less visible and with less control over the customer experience, data and commercial upside.

Payments are the practical entry point

Most banks start their embedded journey with payments due to the ease with which the can be embedded, compared to the likes of lending or deposits. They are also easier to price and already tied to painful tasks like paying suppliers, collecting from customers, reconciling transactions, seeing cash move and understanding working capital.

A good embedded payments proposition can solve real problems quickly. It can reduce manual work, improve cash visibility, make receivables and payables less painful - particularly to global clients and create data that helps banks understand client behaviour in context.

But payments cannot be the whole strategy.

Once a bank sits inside the payment flow, it can begin to solve higher-value problems around reconciliation, liquidity, cash forecasting and working capital. The bank then earns the right to move from fire and forget transaction execution to greater value added financial intelligence such as insights or suggested next actions.

That’s where the unit economics become more interesting.

Treasury automation is the higher-value play

Corporate clients want real-time visibility over cash, liquidity, receivables, payables and risk. They don’t want yesterday’s view of the business. They don’t want to stitch together data from five bank portals and a million spreadsheets. And they don’t want treasury teams spending their time manually reconciling the past when they should be managing the future.

Embedded banking gives banks a way to sit inside treasury operations rather than outside them.

That means providing cash positioning, liquidity tools, payment initiation, forecasting data and risk insight inside the systems treasury teams already use. It means helping clients act faster because the banking data and controls are present at the point of decision.

This is where corporate banking can become more relevant, not less.

But it requires more than connectivity. Banks need reliable data, clear permissions, strong controls, modern architecture and propositions designed around treasury jobs, not internal product lines.

Embedded lending is moving up the agenda

After payments, lending is the next serious battleground.

Invoice finance, supply-chain finance, revenue-based financing, embedded credit and SME working capital all become more powerful when they are triggered by real workflow data. SMEs gain real-world value with embedded finance. 

A supplier needs finance when an invoice is approved. A marketplace seller needs working capital when demand spikes. A business using vertical SaaS may need credit when the platform can already see trading patterns, revenue and cash flow pressure.

That is a better moment than a cold application journey on a bank website.

Embedded lending lets banks use context to offer finance when the need is visible. Done well, it can improve access, reduce friction and create new revenue. Done badly, it becomes risky product-pushing in a new channel.

The difference is discipline.

Banks need to know which segments they understand well enough, which data they can trust, which risks they can manage directly vs. at arms length, and which partners are worth building around joint product development.

What banks need to decide

A bank can lead with payments. It can become a treasury workflow partner. It can specialise in embedded credit. It can target ERP ecosystems. It can work with marketplaces, procurement networks, payroll platforms, B2B SaaS or vertical software providers.

But it cannot chase everything at once and expect focus to magically appear later.

The stakes are too high.

Client relationships are moving into third-party workflows. Product innovation is increasingly happening where marketplaces, software platforms and financial products meet. Competitors are not just other banks anymore. They are fintechs, platforms, software providers and banks that have already worked out where they want to play.

The winners will be the banks that make clear choices about where they create value, which workflows they want to sit inside, which partners they want to work alongside, and ultimately how they turn embedded banking into commercial growth.

Before building another API, banks need to answer the strategic question: Where do we have the right to win?