What is a treasury payment stack?

It is the set of systems a corporate treasury uses to see cash and move it: the ERP where obligations originate, the treasury management system that plans and controls, connectivity to banks (SWIFT, host-to-host files, or APIs), often a payment hub that standardizes formats and approvals, FX platforms for currency execution, and the banks and payment rails underneath that actually settle the money.

What is the difference between a payment hub and a settlement layer?

A payment hub standardizes how instructions leave the company: one format, one approval workflow, one channel to many banks. It improves control over sending. A settlement layer sits below that, changing how the money itself moves: routing each payment across whichever rail fits it and enforcing policy in the settlement process. A hub tidies the instruction; a settlement layer changes the journey.

Where do treasury stacks fall short today?

At the boundaries. Visibility typically ends at the bank's edge: once a cross-border payment enters the correspondent chain, the stack sees a debit and then silence. Liquidity keeps banking hours even though the business does not, so weekends and holidays strand cash. And each layer reconciles against the others, because instructions, confirmations, and settlement all live in separate systems.

Is the treasury stack consolidating?

The direction of travel is fewer seams. TMS vendors have absorbed payment-hub and connectivity functions, banks expose APIs that bypass file-based channels, and real-time treasury has moved from conference slogan to roadmap item. The remaining seam, and the hardest one, is settlement itself, which is why a layer that spans rails, rather than another module on top, is the newest entrant in the diagram.

Treasury

The treasury payment stack in 2026

The layers of a corporate treasury payment stack in 2026: TMS, bank connectivity, payment hubs, FX platforms, and the settlement layer emerging underneath them.

Ask a treasurer to draw their payment stack and you get a tower: the ERP at the top where obligations are born, systems of control in the middle, banks at the bottom where money actually moves. Every layer exists because the one below it left a gap. Understanding the tower, and where it still leaks, is the fastest way to understand what is changing under it in 2026.

The layers, top to bottom

The ERP. Invoices, payroll, intercompany obligations: payments originate here as business events. The ERP knows why money should move, but has no opinion about how.

The treasury management system. The TMS is the control tower: cash positioning, forecasting, exposure management, payment approval. Market platforms in this layer, Kyriba or SAP’s treasury modules among them, decide what should happen to cash. Execution still belongs to the layers below.

Bank connectivity. Instructions have to reach banks somehow: SWIFT connectivity through service bureaus or direct membership, host-to-host file channels negotiated bank by bank, and increasingly bank APIs. This layer is plumbing, and its diversity is the tax every multinational pays: each bank connection has its own formats, cut-offs, and quirks.

The payment hub. Companies with many banks and many ERPs insert a hub to standardize the chaos: one internal payment format, one approval and fraud-control workflow, one pipe out to all banks. Hubs improved control substantially. They did not change what happens after the instruction leaves.

FX platforms. Currency execution runs through multi-dealer platforms and bank portals, usually disconnected from the payment flow they exist to serve, which is why FX and the payment it funds so often reconcile as separate events.

Banks and rails. At the bottom, the actual movement: domestic rails, and for cross-border flows the correspondent chain, with SWIFT gpi tracking payments across it. This is the layer every other layer was built to manage, and it is where the stack’s guarantees end.

Where the gaps live

Visibility stops at the bank’s edge. The stack can tell you an instruction was approved, formatted, and sent. Once the payment enters the correspondent chain, the TMS sees a debit and then a gap until a statement arrives. Tracking has improved the view; the FSB’s 2025 progress report still found wholesale payments beating their one-business-day target while the one-hour goal remains out of reach for much of the market. The stack manages the sending of payments. Nobody in the tower owns the journey.

Liquidity keeps banking hours. Every layer of the stack sleeps when banks do. Cash needed on Saturday in another currency was positioned on Thursday, which is pre-funding by another name, and the reason just-in-time liquidity remains aspirational on exactly the corridors where buffers are most expensive.

Everything reconciles against everything. Instruction, confirmation, FX fill, bank statement, ERP entry: five records of one economic event, matched after the fact. The cost lives in exception queues and month-end close, and it exists because the stack’s layers communicate by message rather than by shared settlement.

The consolidation, and the missing layer

The 2026 stack is consolidating from both ends. TMS vendors absorbed hubs and connectivity; banks published APIs; real-time data replaced the overnight statement in the corridors that support it. Fewer seams, better views of the same underlying journey.

What consolidation on top cannot fix is the journey itself. That is a settlement problem, and it is why the newest layer in the diagram sits at the bottom rather than the top: a settlement layer that spans rails, fiat, stablecoin, and tokenized deposit, presenting one integration upward to the stack the treasurer already runs, and choosing the rail per payment underneath. The distinction from the hub matters: orchestration of instructions is not orchestration of settlement, and the second is where the days, the buffers, and the reconciliation burden actually come from.

Where Frame fits

Frame is the settlement layer for global finance: one integration to orchestrate payments at scale across fiat rails, stablecoins, and tokenized deposits, with compliance enforced on every transaction and settlement in seconds instead of days.

In the stack drawn above, Frame occupies the settlement slot without displacing the layers a treasury has already built: it works as an overlay on existing bank rails, no stablecoin required, and the ERP, TMS, and hub keep their jobs. What changes is the bottom of the tower. Settlement in minutes replaces the visibility gap with an observable journey, Frame’s Rules Engine enforces each payment’s governing policy inside settlement, and every settled transaction produces verifiable evidence that its conditions were met, which is the reconciliation record the rest of the stack has been approximating from messages. Frame serves banks and financial institutions, payment providers and processors, exchanges and trading venues, SaaS and ERP platforms, and enterprises.

See how a rail-neutral settlement layer works: the Frame Blueprint.

Common questions

What is a treasury payment stack?: It is the set of systems a corporate treasury uses to see cash and move it: the ERP where obligations originate, the treasury management system that plans and controls, connectivity to banks (SWIFT, host-to-host files, or APIs), often a payment hub that standardizes formats and approvals, FX platforms for currency execution, and the banks and payment rails underneath that actually settle the money.
What is the difference between a payment hub and a settlement layer?: A payment hub standardizes how instructions leave the company: one format, one approval workflow, one channel to many banks. It improves control over sending. A settlement layer sits below that, changing how the money itself moves: routing each payment across whichever rail fits it and enforcing policy in the settlement process. A hub tidies the instruction; a settlement layer changes the journey.
Where do treasury stacks fall short today?: At the boundaries. Visibility typically ends at the bank's edge: once a cross-border payment enters the correspondent chain, the stack sees a debit and then silence. Liquidity keeps banking hours even though the business does not, so weekends and holidays strand cash. And each layer reconciles against the others, because instructions, confirmations, and settlement all live in separate systems.
Is the treasury stack consolidating?: The direction of travel is fewer seams. TMS vendors have absorbed payment-hub and connectivity functions, banks expose APIs that bypass file-based channels, and real-time treasury has moved from conference slogan to roadmap item. The remaining seam, and the hardest one, is settlement itself, which is why a layer that spans rails, rather than another module on top, is the newest entrant in the diagram.

Sources

Last reviewed 2026-07-16