A guide for commercial banking and treasury leaders at US regional banks. Treasury teams want a real-time view of the asset position across every account and every rail, one instruction surface, and an honest answer on stablecoins. Six requests, remarkably stable for two years.
US regional banks have been listening hard to their mid-market commercial customers, and the message back is consistent. Treasury teams want a real-time view of the asset position across every account and every rail: fiat and regulated stablecoins in one place, not a cash position that stops at the currency the bank happens to hold. They want one instruction surface for every rail the bank supports, and they want the bank to appear as an API endpoint inside the ERP and treasury workstation they already run, not as a file to download. They want an honest answer on stablecoins ahead of the regulatory date, controls that run while the payment is moving rather than in a file the next morning, and forecasting built on data that is current rather than reconciled overnight. Six requests, remarkably stable for two years. The gap is not in the listening. It is in the infrastructure that would make the answers deliverable.
For two years now, every US regional bank with a serious commercial franchise has been running the same conversation with its largest mid-market treasurers, and we have been in a fair number of the rooms where it happens. What has changed is that the treasurer can now name the gap precisely, score competing banks against it, and act on the score.
Deloitte’s 2024 Global Corporate Treasury Survey puts visibility into cash and financial risk exposures at the top challenge for treasury executives.1Crisil Coalition Greenwich reported in 2025 that one-third of US middle-market companies were thinking about switching banks; its 2026 outlook adds the stakes, with lead banks capturing the large majority of a client’s business.2 The same commercial risk, from opposite ends.
This is the gap XYB’s Commercial Treasury Solution (CTS) was built to close. It runs on the AFI Platform, our banking orchestrator, which deploys alongside a bank’s existing core rather than replacing it. The architecture is event-native: every debit and credit is emitted as an event at settlement, and position, payment status, controls, and forecasting all read from the same stream. That single property is what makes all six answerable together rather than one at a time. Below are the six requests, and what each one demands of the substrate underneath.
The most consistent request we hear, close to verbatim across conversations: “I want to log in to one place and see everything I hold, across every account, updated in real time.”
We call that the asset position rather than the cash position, and the distinction is deliberate. We support fiat and regulated stablecoins on the same substrate, so the position has to carry both. A term that says cash quietly assumes it does not.
What the treasurer gets instead is a portal-of-portals problem: several banks, each with its own web experience, refresh cadence, and end-of-day file format.
The demand is not for a better dashboard; it is for the ability to act on the asset position. The 2025 AFP Liquidity Survey found nearly 90% of organizations would select real-time money market funds, and 73% real-time investment sweeps, if their investment policies allowed. AFP’s conclusion is an infrastructure one: real-time liquidity depends on rails capable of instant transfers, capabilities it describes as not yet fully developed.3
CTS answers this structurally. Every debit and credit is emitted as an event the moment it settles, on the AFI Platform’s event-native architecture built on Apache Kafka and Apache Iceberg, with balances exposed through APIs and live event streams rather than a nightly extract. Most real-time claims in commercial banking still resolve to a polling job against a batch core. Treasurers can tell the difference within a week of using the product.
The American payments stack has more rails than at any point in its history: ACH and Same Day ACH, FedNow, RTP, Fedwire, CHIPS, push-to-card, and, under the GENIUS Act, supervised USD payment stablecoins.
The rails are no longer marginal, and corporate money is what is moving the numbers. When The Clearing House raised the RTP transaction limit to $10 million on 9 February 2025, average payment size went from $842 in January to over $4,000 within five months, and quarterly value stepped up accordingly: $481 billion in the second quarter of 2025, a 195% increase over the prior quarter. It has kept climbing since: $576 billion across 142 million transactions in the second quarter of 2026, with over 1,280 participating institutions. The Clearing House attributes the higher-value growth to corporate treasury use: cash concentration, portfolio rebalancing, and large payments to suppliers.4 On the FedNow side, the Federal Reserve passed 1,400 participating institutions in two years, and its own research found around two-thirds of businesses would use instant payments if their primary financial institution offered them.5
The engineering problem is not any single rail. It is that cost, settlement timing, return behavior, fraud exposure, and reporting format differ across all of them, and the orchestration substrate has to reason across the whole set at instruction time. Optimizing that choice is the bank’s job, not the treasurer’s.
CTS exposes one instruction surface. Routing logic sits in configurable workflows on the AFI Platform, so a new rail or routing rule is a configuration change, not a release, and payment lifecycle events publish to the same stream that drives the asset position: status observable end to end, not inferred from a return file.
The mid-market treasury team is almost certainly running NetSuite, SAP S/4HANA, Microsoft Dynamics, or Workday for the general ledger, and Kyriba, Trovata, GTreasury, or HighRadius (and equivalents) for the treasury workstation, with a tax and AP layer on top. It does not want to download an MT940 file and reconcile by hand. It wants the bank to show up as an endpoint inside the systems the team already operates.
PwC’s 2025 Global Treasury Survey found that 65% of organizations plan to expand their use of APIs specifically to enable real-time integration across ERPs, treasury management systems, and banking networks, while only 57% use a treasury management system at all and roughly a third still run manual processes somewhere in the workflow.6
The bank that shows up as a well-documented API inside that stack is the bank whose data the customer builds on. CTS exposes an API surface shaped around treasury workflows rather than around the bank’s internal ledger geometry, with synchronous APIs for instruction and asynchronous event streams for state. Balances, status changes, returns, and exceptions arrive as events rather than as a file the customer has to fetch and parse.
The mid-market treasurer has started expecting the bank itself to be programmable. The bank that can be is the bank that keeps the relationship.
The GENIUS Act gives supervised institutions a regulated path to hold and move USD-denominated payment stablecoins for corporate clients: effective 18 January 2027, or 120 days after the primary federal regulators finalize implementing rules, whichever is earlier. Those rules are late: the statutory one-year rulemaking deadline passed in July 2026 with the principal OCC, FDIC, NCUA, and Treasury packages still in proposal form, and any final rule issued after roughly 20 September 2026 can no longer pull the date forward. January 2027 is therefore the planning date, and the interval between knowing the requirements and having to meet them is compressing, not expanding.11
The question mid-market treasurers put to their banks is not whether the bank has a crypto strategy. It is whether the bank will have an answer before the customer needs one.
Here the honest data matters more than the enthusiastic version. The 2026 AFP Liquidity Survey found stablecoins and tokenized products sitting on the periphery for most treasury teams despite high awareness, with AFP’s Director of Treasury Practice noting that teams need to build knowledge now so they can decide once the rules are finalized.7McKinsey’s analysis with Artemis Analytics sizes actual stablecoin payment activity in 2025 at roughly $390 billion, about 0.02% of global payment volumes, with business-to-business flows the largest single component at roughly $226 billion.8
Read together, those two findings describe a readiness problem rather than a demand problem. A bank that starts building when the first corporate client asks will be starting eighteen months late.
CTS runs stablecoin orchestration on the same event-native substrate as fiat, with the AFI Platform’s multi-currency ledger treating regulated stablecoins as a currency type rather than a bolted-on module: ACH, RTP, FedNow, wire, and a regulated stablecoin transfer move through one instruction surface into one position. The bank turns it on when its risk posture and the regulatory calendar say so, without re-architecting.
Nacha’s Risk Management Framework Phase 2 (in force since 19 June 2026, operationally 22 June, a federal-holiday adjustment) eliminates the volume threshold: credit monitoring applies to all receiving institutions regardless of ACH receipt volume, and fraud monitoring extends to the originators and third-party senders that fell outside Phase 1.9California’s Digital Financial Assets Law: In force since 1 July 2026. The GENIUS Act regime: Effective 18 January 2027.
Two in Force. One Dated. Each assumes monitoring that runs while the payment is moving rather than in a file the following morning.
This is where a batch core becomes the binding constraint, and the failure mode is commercial rather than regulatory. A rule update lands, the core cannot accommodate it on the published timeline, the workaround degrades the customer experience, and a competitor takes the relationship at renewal.
CTS treats sanctions screening, fraud scoring, approval policy, and audit as policy that runs inline against the event stream, configured in the console and versioned like any other workflow, not as a downstream reconciliation job or a manual approval queue. The bank remains the party that complies; the platform supports it with the data lineage, event-level auditability, and immutable transaction history that evidencing compliance depends on. The AFI Platform is SOC 2 Type II attested; the substrate-level detail is in Security at the Infrastructure Level.
Forecasting is the perennial bottom-of-the-list complaint, and it is a data problem before it is a modeling problem. AFP’s Treasury Benchmarking Survey finds that more than 60% of treasury professionals name cash or liquidity forecasting as the most challenging task they face.10Deloitte’s 2024 survey reaches the same place from the other direction: cash positioning maturity still lags even as treasurers rank forecasting a priority.1
The treasurers we talk to describe a more specific problem than inaccuracy: the forecast is wrong because the data feeding it is stale, fragmented, and arrives in batches. No model fixes a stale input. When the asset position is event-native, with debits and credits emitted as they occur, categorization applied inline, and counterparty metadata attached at settlement, the forecast has something current to consume. CTS exposes that stream to the bank’s analytics and the customer’s treasury workstation; the forecast improves because the data underneath it did.
None of these six demands is new. What is new is that the treasurer can name them, score banks against them, and switch when the score is poor. The question is no longer whether to invest in commercial treasury; it is whether the investment can answer all six on one substrate, on a timeline the customer will tolerate.
XYB’s Commercial Treasury Solution is built for that answer. See, Move, Govern, and Reconcile ship together on the AFI Platform, deploy alongside existing systems with no replacement program required, and answer all six demands on one substrate. CTS starts with Faster Payables, the entry point that addresses the most acute mid-market pain, and expands from there. First production value in 10 weeks.
The treasurers have been clear. The next move belongs to the bank.
About XYB. XYB is the company creating Adaptive Financial Infrastructure (AFI), the new category for banking orchestration: unifying systems, people, and processes. The AFI Platform, the banking orchestrator, is the event-native substrate enabling financial institutions to adopt agentic AI, real-time payments, and decentralized finance without replacing what already works.
See how the Commercial Treasury Solution deploys alongside the existing core, or talk it through with the team.