First-generation stablecoins solved a real problem. They gave crypto markets a stable unit of account and made cross-border value transfer faster and cheaper than legacy systems. But they did this by keeping things simple - a token is a claim on a reserve, and the blockchain moves that claim around. The token itself carries no information about who holds it, why it is being moved, or whether the counterparties on either end are compliant with the rules that govern them.
That architectural limitation is now driving the next wave of stablecoin development, pushed forward by a combination of regulatory pressure and genuine demand from institutional participants who need programmable money to behave more like programmable money.
What regulation actually changed
Between 2024 and 2026, three significant regulatory frameworks came into effect in parallel. The GENIUS Act in the United States established a federal licensing structure for stablecoin issuers and set reserve and disclosure requirements that moved stablecoins closer to regulated financial instruments. Europe's MiCA regulation did something similar at the EU level, creating a unified licensing regime for crypto asset issuers across member states. Thailand built one of the more detailed crypto frameworks in Southeast Asia, with explicit provisions for programmable payment infrastructure.
The common thread across all three is a shift away from treating stablecoins as a separate asset class and toward treating them as a form of digital money that needs to interoperate with existing financial regulation. That shift in framing has direct technical implications.
From static tokens to programmable assets
The distinction that matters here is between a static token and what practitioners are increasingly calling a dynamic asset. A static token represents a claim - it has a value and can be transferred, but it carries no embedded logic about who can hold it or under what conditions it can move. A dynamic asset embeds compliance logic directly into the token or into the infrastructure through which it moves.
The practical difference shows up clearly in a cross-border payment scenario. When a tokenized bank deposit moves from a US institution to a Thai institution under the new regulatory frameworks, the token can query the receiving institution's compliance status in real time before the transaction settles. The Thai institution's system checks whether the transaction meets its regulatory requirements and either approves or blocks it. If approved, the currency conversion and settlement happen in a single atomic transaction - both legs settle or neither does, eliminating settlement risk.
This is not a conceptual model. Regulatory sandboxes in Thailand and several other jurisdictions are actively testing this infrastructure. The Bank for International Settlements and a consortium of central banks have been developing the underlying standards for how these systems interoperate across borders.
Why tokenized bank deposits change the picture
One of the more significant developments in this period is JPMorgan's tokenized deposit product, which sits in a different regulatory category than stablecoins issued by non-bank entities. A tokenized deposit is not a claim on a reserve held by a payment company - it is actual bank money, sitting on a blockchain, with the same FDIC protections and regulatory treatment as a conventional deposit.
That distinction matters for institutional adoption. Corporations, asset managers, and financial institutions operating under their own regulatory obligations cannot easily use instruments that exist in ambiguous legal categories. Tokenized deposits from regulated banks remove that ambiguity, which is why they are attracting more serious enterprise interest than earlier stablecoin products.
What programmable money actually enables
The use cases that become possible with programmable, compliant money go well beyond faster cross-border payments. Conditional payment logic can tie settlement to external events - a container crossing a border, a delivery being confirmed, a performance milestone being hit. Treasury management can be automated based on predefined rules without requiring manual intervention at each step. Payment flows between AI agents can happen at machine speed without human oversight for each transaction.
None of these require users to interact with crypto infrastructure directly. The blockchain layer becomes settlement infrastructure - it handles finality and eliminates counterparty risk, but it sits beneath the application layer where users and businesses actually operate.
Where this is heading
The separation between crypto markets and traditional financial markets is narrowing, driven less by ideology and more by practical convergence. Regulated institutions need programmable settlement infrastructure. The most mature programmable settlement infrastructure is blockchain-based. The regulatory frameworks being built now are designed to make those two things compatible rather than mutually exclusive.
The result is a system where the distinction between a stablecoin and a digital bank deposit becomes less meaningful over time, and where compliance is embedded in the asset rather than managed entirely through the intermediaries that handle it.
For developers and infrastructure teams building in this space, the relevant shift is in what the money layer is expected to do. Settlement infrastructure is no longer passive - it is expected to carry context, enforce rules, and interoperate across jurisdictions in real time. That is a substantially more complex engineering problem than moving static tokens around, and the teams that understand it have an advantage as institutional adoption accelerates.