You pay your credit card bill on Monday. The bank says “payment received.” But the money doesn’t actually land until Thursday.
Where is it for those three days?
This is float, and understanding it explains more about how payment systems work than almost anything else.
What float actually is
Float is the time value of money during payment delays. When funds are in transit (debited from one account but not yet credited to another) someone is holding that money. And money held is money that can earn interest.
In a world of near-zero interest rates, this seemed irrelevant. With rates at 4-5%, float is suddenly worth real money again.
The anatomy of a delayed payment
Consider a typical ACH transfer:
- Day 1: You initiate a payment
- Day 1: Your bank debits your account (money leaves you)
- Day 2-3: The payment moves through the ACH network in batch
- Day 3-4: The receiving bank credits the recipient
For those 2-3 days, the money is… somewhere. In practice, it’s often sitting in pooled settlement accounts, earning overnight rates.
Multiply this by millions of transactions and significant dollars accumulate.
Float in different systems
Different payment rails have different float characteristics:
Wire transfers: Same-day settlement, minimal float. This is one reason they’re expensive. Less time to earn on the money.
ACH: 1-3 day settlement. Substantial float, especially for batch processing.
Card payments: Complex. Authorization is instant, but merchant settlement is typically T+1 or T+2. The interchange economics partially reflect this.
Checks: The longest float. Funds might be “available” before the check actually clears, creating risk and opportunity.
Real-time payments (RTP, FedNow): Near-zero float. Settlement is seconds. This changes everything.
Who benefits from float
Float isn’t inherently good or bad. It’s a feature of how systems are designed. But the benefits flow to whoever holds the money during transit.
Historically, this has been:
- Banks processing payments
- Payment networks managing settlement
- Large corporates with treasury operations optimized for payment timing
The incentives are subtle but real. If you earn interest on money in transit, you’re not necessarily motivated to speed up transit.
The corporate treasury angle
Sophisticated companies have known about float forever. Treasury teams optimize payment timing precisely, collecting receivables as fast as possible, delaying payables as long as acceptable.
“Payment terms” aren’t just about cash flow. They’re about who captures the float.
A company that collects in 15 days and pays in 45 days has 30 days of float on every transaction. At scale, this funds significant operations.
What real-time payments change
Systems like India’s UPI, Brazil’s Pix and the US Federal Reserve’s FedNow settle in seconds. The money moves instantly from payer to payee.
This eliminates float.
The implications ripple through the entire system:
- Banks lose a quiet revenue stream
- Corporate treasury strategies need rethinking
- Payment timing becomes less of a competitive lever
- Fraud windows shrink (less time to catch errors)
- Reconciliation simplifies (no ambiguous in-transit states)
Real-time isn’t just faster. It’s a different economic model.
The interest rate connection
Float economics are directly tied to interest rates. When rates were near zero (2010-2021), float was worth almost nothing. A billion dollars earning 0.1% for 3 days is barely a rounding error.
At 5%, that same billion for 3 days is over $400,000 annualized.
The return of meaningful interest rates has made float valuable again, just as real-time payment systems are eliminating it. Timing is everything.
The bottom line
Float is invisible to most people. You don’t see it on statements or in app interfaces. But it shapes how payment systems are built, priced and evolved.
When someone asks why certain payments are slow, float is often part of the answer. Not the whole answer. There’s also batch processing, compliance, legacy infrastructure. But follow the money, literally, and you’ll find that payment delays aren’t always accidents.
They’re often features.