The finance industry treats all capital the same. Whether a dollar sits in a treasury account for six months or flows through a 48-hour settlement window, most companies manage it with the same tools, the same assumptions, and the same result: it either earns yield at the cost of liquidity, or it stays liquid at the cost of earning nothing.
This is wrong. And it is wrong in a way that costs companies real money.
Treasury reserves and operational capital are fundamentally different. They have different time horizons, different liquidity requirements, different risk profiles, and different buyers within the organization. They need different infrastructure.
The Two Types of Capital
Core question: Money-at-Rest (Treasury): Where should idle capital sit?, Money-in-Motion (Operations): How should active capital move?
Primary buyer: Money-at-Rest (Treasury): CFO, Treasury team, Money-in-Motion (Operations): Payments, Ops, Product teams
Capital state: Money-at-Rest (Treasury): Static reserves, long-term holdings, Money-in-Motion (Operations): Dynamic flows, floats, escrows
Time horizon: Money-at-Rest (Treasury): Weeks to months, Money-in-Motion (Operations): Hours to days
Liquidity need: Money-at-Rest (Treasury): Periodic (quarterly rebalancing), Money-in-Motion (Operations): Instant (sub-30 seconds)
Yield approach: Money-at-Rest (Treasury): Allocate to venues, rebalance periodically, Money-in-Motion (Operations): Earn automatically during idle windows
Risk tolerance: Money-at-Rest (Treasury): Moderate (diversified across venues), Money-in-Motion (Operations): Very low (must not disrupt operations)
Optimization logic: Money-at-Rest (Treasury): Maximize risk-adjusted return, Money-in-Motion (Operations): Maximize yield without impacting operational tempo
Decision frequency: Money-at-Rest (Treasury): Quarterly or monthly, Money-in-Motion (Operations): Continuous, automated
Example: Money-at-Rest (Treasury): $100M reserves split across T-bills and lending, Money-in-Motion (Operations): $10M settlement float earning during 3-day hold
This is not a superficial distinction. These differences determine what infrastructure you need.
Why This Distinction Matters Now
Before stablecoins, operational capital was trapped. It sat in bank accounts earning whatever the bank offered (usually close to nothing). There was no infrastructure to make a 48-hour settlement window productive. The cost of deploying capital for such short periods exceeded any yield it could generate.
Stablecoins changed this. On Solana, a deposit-to-yield-vault transaction takes approximately 400 milliseconds and costs less than $0.01. You can deploy capital for a 3-hour window and profitably capture yield. The infrastructure cost became negligible relative to the yield opportunity.
But the tools did not keep up. Treasury management platforms were built for money-at-rest. They assume:
Periodic rebalancing (weekly, monthly, quarterly)
Multi-day or multi-week deployment horizons
CFO-level oversight and approval
Portfolio-level optimization across asset classes
Using these tools for money-in-motion is like using a cargo ship to deliver a package across town. The vehicle works. It is just wildly wrong for the job.
Where Money-in-Motion Lives
Operational capital that flows through business processes and sits idle during operational windows exists in every stablecoin-touching company:
Payment Settlement Windows
When a customer pays a merchant through a payment processor, the funds do not settle instantly. Depending on the processor and payment method, settlement takes 1-3 days. During that window, the stablecoins sit in the processor's settlement account.
For a processor handling $100M monthly with T+2 settlement, approximately $6.6M sits idle at any given time.
Escrow Holds
Marketplaces hold funds in escrow during fulfillment periods. A seller ships a product; the buyer's payment is held until delivery is confirmed. This can be 3-14 days depending on the marketplace and shipping method.
For a marketplace processing $50M monthly with a 7-day average escrow, approximately $11.5M sits in escrow at any given time.
Prefunding Buffers
Payroll platforms, FX brokers, and payment companies prefund pools for anticipated payouts. These buffers are loaded 24-72 hours before disbursement.
A payroll platform processing 10,000 payments of $5,000 average in weekly batches holds approximately $50M in prefunding buffers at any given time.
FX Conversion Timing
Multi-currency operations hold stablecoins timed to optimal FX conversion windows. A processor converting USDC to local fiat might hold for 4-24 hours waiting for rate optimization or batch processing.
Compliance Holds
Funds paused for compliance review - KYT screening, sanctions checking, Travel Rule verification - sit idle during the review period. This is typically hours, but can extend to days for complex cases.
Exchange Operational Pools
Exchanges maintain hot wallet balances for withdrawals, market-making reserves, and operational buffers. These pools fluctuate but always have a base level of idle capital.
The $50 Billion Blind Spot
A rough market sizing of money-in-motion in stablecoin operations:
Payment processor settlement float: Estimated Global Float: $15-25B, At 7% APY: $1.05-1.75B
Marketplace escrow balances: Estimated Global Float: $5-10B, At 7% APY: $350-700M
Payroll prefunding buffers: Estimated Global Float: $3-5B, At 7% APY: $210-350M
Exchange operational pools: Estimated Global Float: $5-10B, At 7% APY: $350-700M
FX timing and conversion float: Estimated Global Float: $2-5B, At 7% APY: $140-350M
Total estimated: Estimated Global Float: $30-55B, At 7% APY: $2.1-3.85B
These numbers are rough. No one tracks aggregate operational stablecoin float across the industry. But the order of magnitude is clear: tens of billions in operational capital earning zero, with billions in potential yield revenue uncaptured.
The Infrastructure Gap
Three categories of tools exist. None serve money-in-motion correctly.
Treasury Platforms (Kiln, Dfns, Brava)
What they do well: Optimize long-term capital allocation across yield venues. Rebalancing, portfolio management, risk-adjusted returns.
Where they fail for money-in-motion:
Liquidity assumptions are wrong (periodic, not instant)
Time horizons are wrong (weeks/months, not hours/days)
Decision model is wrong (manual/periodic, not automated/continuous)
Buyer is wrong (CFO/Treasury, not Ops/Product)
Using a treasury platform for operational float is like using a mutual fund for your checking account. It works at the wrong speed.
Custody Platforms (Fireblocks, BitGo, Coinbase Custody)
What they do well: Secure keys. Protect assets. Provide institutional-grade custody.
Where they fail for money-in-motion:
Zero yield. Funds are secure but completely unproductive.
No programmability. Custody secures; it does not automate workflows.
No compliance integration. KYT and Travel Rule are separate systems.
Custody is necessary but not sufficient. You need your funds secured AND productive.
DeFi Protocols (Aave, Compound, Drift)
What they do well: Generate yield through lending and liquidity provision.
Where they fail for money-in-motion:
No compliance layer. No KYT, no ring-fencing, no Travel Rule.
Not enterprise-grade. No audit trails, no reporting, no multi-user access controls.
Complexity. Each protocol has unique integration requirements, risk profiles, and mechanics.
Not automated for operational flows. Manual deposit/withdraw per protocol.
Raw DeFi is the engine. But using it directly for enterprise operations is like building a car from an engine, a frame, and some wheels. You need the assembled vehicle.
The Missing Layer
What money-in-motion needs is infrastructure that:
Automates yield deployment during any idle window (no manual intervention)
Provides instant liquidity (sub-30 seconds) so operations are never disrupted
Includes compliance at the infrastructure level (ring-fencing, KYT, Travel Rule)
Works with existing custody (no migration required)
Operates continuously without CFO-level oversight
This is the stablecoin operations layer.
"Yield Is a Property of Correct Operations"
This is the core thesis.
The conventional framing: "Should we add yield to our stablecoin product?" As if yield is a feature to be bolted on, a decision to be made, an optional enhancement.
The operations framing: "Why would any dollar in our operational flows ever sit idle?"
When money moves through well-designed operational infrastructure:
KYT screening happens at entry (clean funds identified)
Clean funds automatically deploy to yield venues during any idle window
Yield accrues for the duration of the window (hours, days, whatever the operational cycle requires)
Funds withdraw instantly when the operational flow needs them
Compliance is maintained throughout
In this model, yield is not a product decision. It is an output of correct infrastructure design. You do not choose to earn yield. You choose not to leave money idle. The yield follows naturally.
This is analogous to how modern cloud infrastructure works. You do not choose to "add scalability." You build on infrastructure (AWS, GCP) that scales by default. Scalability is a property of the architecture, not a feature you add.
Similarly, yield should be a property of stablecoin operations architecture. Every dollar should be productive by default. The question is not "should we earn yield?" but "is our infrastructure designed correctly?"
What Changes in the Next 3-5 Years
Near-term (2026-2027)
Early adopters capture yield on operational float (competitive advantage)
Regulatory frameworks mature (MiCA, GENIUS Act) creating infrastructure requirements
200-500 institutional stablecoins create multi-coin operational complexity
First-mover operations infrastructure becomes embedded in customer workflows
Medium-term (2027-2028)
Yield on operational capital becomes table stakes (competitive parity)
Companies without operational yield lose margin to competitors
Multi-stablecoin orchestration becomes essential
Compliance infrastructure requirements intensify
Long-term (2028-2030)
Agentic commerce creates exponential demand for yield-aware money infrastructure
AI agents managing stablecoin balances at machine speed
Every idle millisecond across every agent balance compounds
Operations layer becomes the most critical infrastructure category
The companies that build on operations infrastructure now have 12-24 months of competitive advantage. After that, it becomes the cost of doing business.
Frequently Asked Questions
Is this relevant if my company only holds stablecoins temporarily?
Yes - "temporarily" is exactly the point. Money-in-motion earns during temporary holds. A 48-hour settlement window on $5M at 7% APY earns approximately $1,918. Across 200+ settlement cycles per year, that compounds into meaningful revenue.
What is the difference between yield-in-transit and treasury yield?
Yield-in-transit accrues during operational windows (hours to days) with instant liquidity requirements. Treasury yield accrues during allocation periods (weeks to months) with periodic liquidity. The infrastructure requirements are different: automated deployment vs periodic rebalancing, instant withdrawal vs scheduled, and ops-team governance vs CFO governance.
Does money-in-motion yield require higher risk tolerance?
Actually the opposite. Money-in-motion infrastructure must be very conservative because operational capital cannot be at risk. Conservative yield strategies (tokenized T-bills, established lending protocols) are standard. The priority is: 1) never disrupt operations, 2) maintain compliance, 3) maximize yield within those constraints.
How do I calculate my operational float?
Map every stablecoin wallet your company operates. For each wallet, measure the average balance over 30 days. Subtract the minimum balance needed for immediate operations. The difference is your yield-eligible operational float. Most companies are surprised by how much idle capital they discover.
Can treasury and operations infrastructure coexist?
Yes - they should. Use treasury tools for your reserves (money-at-rest). Use operations infrastructure for your flows (money-in-motion). The distinction is which capital pool goes to which infrastructure, not choosing one over the other.
What happens during market volatility?
Operations infrastructure operates on stablecoins, not volatile crypto assets. Stablecoin values do not fluctuate (they are pegged to fiat). Yield rates fluctuate with market conditions, but the principal is not at risk from price volatility. During periods of high yield-rate volatility, conservative strategies (T-bill vaults) provide more stable returns.
Yield is a property of correct operations. If your stablecoin balances are sitting idle during operational windows, the infrastructure to make them productive exists. [Learn how RebelFi handles money-in-motion.]
Learn how RebelFi provides stablecoin operations infrastructure for this.
