For the last decade, banking has moved through successive waves of reinvention—APIs, embedded finance, real-time payments—and now into stablecoins, tokenized deposits, and broader digital asset infrastructure.
But Sam Boboev, a fintech analyst focused on banking infrastructure and payments systems, argues the industry is misreading the pattern. In conversation with us, and through his ongoing Fintech Wrap-Up Medium commentary series, he frames these shifts not as discrete innovation cycles but as a continuous stress test on the same underlying banking architecture—each wave exposing friction in legacy cores, settlement layers, and cross-institution interoperability.
APIs revealed integration gaps. Embedded finance increased reliance on intermediaries. Real-time payments exposed liquidity and settlement constraints. Digital assets are now pushing into custody, programmability, and regulatory boundaries.
What emerges from Boboev’s view is less a story of sequential disruption than of cumulative pressure: a system repeatedly revealing its structural limits under increasingly real-time, composable financial demands.
Question: Everyone in banking today seems focused on stablecoins and tokenized deposits. But you’ve argued the real story isn’t actually there. What do you mean?
Sam: The focus on stablecoins is understandable, but slightly misplaced.
They’re not the disruption. They’re the symptom. What’s actually happening is more structural: banking systems designed for a batch-based world are being forced to operate in a continuous-time financial environment. Stablecoins simply make that mismatch visible in a way that’s hard to ignore.
Question: So why call them a symptom rather than the disruption?
Sam: Because the pressure didn’t start with them.
It’s been building for years across multiple “innovation waves” in financial services—real-time payments, embedded finance, tokenized assets.
Each looked like a product evolution. But structurally, they all point to the same constraint: legacy banking infrastructure assumes delay is normal.
So what we’ve been calling innovation is often just repeated stress against the same architectural boundary.
Question: So you see this less as a series of trends and more as a single transition?
Sam: Exactly.
The industry tends to describe fintech as phases: embedded finance, then real-time payments, then digital assets. But structurally, it’s more accurate to see a single transition underway—from batch-time finance to continuous-time finance.
In a batch system, everything revolves around pause points: settlement windows, reconciliation cycles, operational cutoffs. In a continuous system, those pauses disappear.
And most of the complexity we see today comes from trying to simulate continuity on top of systems that were never designed for it.
Question: Real-time payments are often cited as a success story. Do you see it differently?
Sam: I see it as an early stress signal.
It forced banks to operate at speeds and consistency levels their underlying systems weren’t built for.
But more importantly, it exposed weaknesses in adjacent functions—liquidity management, reconciliation, fraud detection—because those areas still assumed batch processing.
So real-time payments didn’t complete modernization. It revealed how incomplete modernization actually was.
Question: Where do stablecoins change the equation further?
Sam: Stablecoins remove the remaining structural assumptions that banking still relies on—things like operating hours, centralized settlement points, and jurisdictional sequencing.
Money no longer moves in discrete windows. It moves continuously, across networks that don’t align neatly with traditional banking boundaries. That shifts the core problem.
It’s no longer about making transactions faster. It’s about whether your underlying architecture can operate without interruption.
Question: That brings us to 24/7 infrastructure. Why is that such a difficult shift?
Sam: Because banking infrastructure was never designed for permanence. It was designed with downtime as a feature, not a flaw.
Overnight batch processing, maintenance windows, settlement cutoffs—these weren’t inefficiencies. They were structural mechanisms for managing operational risk.
A 24/7 system removes those buffers. And once you remove the buffers, you expose everything that time was previously absorbing.
Question: What are banking leaders most likely underestimating right now?
Sam: Not individual technologies.
The mistake is treating this as a portfolio of separate initiatives—payments modernization, digital assets, AI transformation, treasury upgrades. They’re not separate.
They’re all expressions of the same underlying shift in operating conditions. The constraint is architectural, not product-based. And once you see it that way, the framing changes completely.
It’s no longer “which innovation wins?” It becomes: which systems can survive continuous operation without being rebuilt from the ground up?
That is the real question banks are now facing. Read Sam Boboev’s Deep Dive: The Emergence of the Bank Operating System
