The Structural Inflection Point
~4 minStripe processed $1.9 trillion in payment volume in 2025 — approximately 1.6% of global GDP — yet the Collison brothers frame this as only the opening act. In their 2025 Annual Letter, Patrick and John Collison made a declaration that reframes the entire financial infrastructure conversation: "Agents will most likely soon be responsible for most internet transactions."
This is not a speculative forecast from an AI research lab. It is the explicit strategic thesis of the company that processed $1.9T last year, made directly in their primary investor communication. The implication is architectural, not incremental. The payment infrastructure built for checkout flows and human-initiated commerce is categorically miscalibrated for what is coming.
AI agents are transitioning from experimental tools to primary economic actors. When they transact — paying per inference, per API call, per millisecond of compute — they do so at volumes, frequencies, and micro-denominations that have no precedent in human-scale commerce. A single AI research workflow generates dozens of billable micro-events. A million agents running simultaneously generate millions of settlement obligations per second, continuously, with no batch window, no business hours, and no human initiation.
Stripe's own infrastructure response validates the thesis in concrete moves. The Agentic Commerce Protocol (ACP), built in partnership with OpenAI, establishes a standard for agent-to-agent payment interactions — a protocol layer for machine-native commerce. Stripe Tempo, co-developed with crypto firm Paradigm, is a purpose-built blockchain for the settlement layer. The Bridge acquisition — a stablecoin infrastructure company whose volume grew 4× to $400B in 2025 — fills the dollar-denominated programmable rail. These are not product launches. They are the deliberate construction of a new financial operating system, announced publicly.
The regulatory architecture is moving in parallel, creating the legal preconditions for agent commerce at scale. The US GENIUS Act (July 2025) established the first federal framework for payment stablecoins. The EU's MiCA regulation (fully operational December 2024) created a comprehensive crypto-asset regulatory framework. SWIFT ISO 20022 mandatory migration (November 2025) adds structured, programmable data to cross-border payments. These are not isolated regulatory events — they form a coherent infrastructure build-out that is a precondition for, not a response to, agent-scale commerce.
"Agents will most likely soon be responsible for most internet transactions."
— Patrick & John Collison · Stripe Annual Letter 2025 ↗
The 2025 congestion event makes the stakes concrete. A single memecoin frenzy delayed one Bridge settlement by 12 hours and spiked fees 35×. That disruption occurred under today's human-driven transaction load — occasional, bursty, manually triggered. Under agent-scale load — millions of autonomous systems transacting continuously, simultaneously, with no human throttle — that 35× fee spike becomes the baseline, not the exception. The infrastructure designed for the former cannot serve the latter with reliability or cost efficiency.
The scale difference is categorical, not incremental. Stripe's $1.9T TPV represents approximately 1.6% of global GDP — processed at human-initiated frequencies. Agent commerce operates at fundamentally different temporal density. This is not more volume on the same infrastructure. It is a categorically different class of economic activity requiring a categorically different settlement architecture.
Economics of Agent Commerce
~3 minThe conventional framing of the infrastructure gap — "TPS required vs. TPS available" — understates the problem. The real gap is in Economic Event Density (EED): the number of billable micro-events generated per second by AI agent workflows, distinct from raw transaction count. This is an iProDecisions Research original metric, and it reframes both the magnitude of the opportunity and the nature of the infrastructure required to capture it.
AI agents do not generate one transaction per task. They generate dozens of billable micro-events per workflow: per-inference charges, API data retrieval fees, tool-use costs, inter-agent coordination fees, computation billing, and result-validation charges. Traditional payment rails were designed to settle discrete, human-initiated transactions — one checkout, one wire. EED measures something fundamentally different: the continuous, granular, sub-second economic activity of autonomous systems operating at scale.
"Meeting AI demands will likely require a horizontal architecture of multiple, interacting chains."
— Patrick & John Collison · Stripe Annual Letter 2025 ↗
The winning infrastructure will not be the one that processes the most transactions — it will be the one that processes the densest, most granular stream of economic micro-events with programmable compliance logic embedded at the protocol layer. EED is the metric that separates infrastructure designed for the agentic era from infrastructure merely upgraded for it.
The implications of EED extend beyond raw throughput benchmarking. When you model settlement infrastructure requirements through the EED lens, three practical conclusions emerge that the TPS-only framing misses entirely.
First, netting efficiency becomes the primary infrastructure lever before raw TPS. A 100:1 compression ratio at L3 means 23,611 EPS nets to roughly 236 on-chain settlements per second — within range of today's best blockchains. The infrastructure problem is not "how do we get to 1B raw TPS" but "how do we build the off-chain and rollup layers that compress dense agent workloads before they hit L5." This is precisely what Stripe Tempo is designed to do, and why the ACSM's emphasis on L2/L3 is central to the thesis.
Second, the denominational floor matters as much as throughput. A research agent calling an LLM API at $0.0001 per inference generates economic events too small for legacy payment rails to process economically — the per-transaction overhead of ACH or even Stripe's own card infrastructure exceeds the value of the transaction. Agent commerce economics only function at scale when settlement infrastructure can handle sub-cent denominations natively, with essentially zero marginal cost per event. Stablecoin-based rails, state channels, and programmable escrow are the enabling infrastructure for this — not incremental upgrades to existing card networks.
Third, the compliance layer cannot be retrofitted at scale. At 23.6M economic events per second, you cannot run post-transaction AML screening through a human-supervised workflow. Compliance must be embedded at the protocol layer — smart contracts that enforce sanctions lists, spending limits, and counterparty verification at the moment of event generation, not after. This is why L4 Programmable Risk/Compliance is the most strategically underrated layer in the ACSM stack, and why organisations with deep regulatory expertise have a durable moat available to them right now that most infrastructure players are not yet building for.
The ACSM Framework
~5 minThe Agentic Commerce Stack Model (ACSM) is an original iProDecisions Research framework classifying the five infrastructure layers required for AI agent-scale commerce. The critical strategic insight the framework encodes: no single high-TPS network solves the agent commerce problem. The Collisons said it directly — "a horizontal architecture of multiple, interacting chains." The ACSM gives that horizontal architecture a precise, investable structure.
Each layer has distinct market structure dynamics, key performance metrics, competitive moats, and strategic timing considerations. An organization deploying or investing in agent commerce infrastructure must explicitly position within this stack — and understand which layers are winner-take-most versus naturally oligopolistic versus structurally fragmented.
| Layer | Market Structure | Key Metric | 2025 Status | Est. 2030 TAM | Strategic Priority |
|---|---|---|---|---|---|
| L1 — Agent Execution | Winner-take-most | Event density / sec | Forming | ~$180B | Immediate — window open now |
| L2 — Off-Chain Mesh | Oligopolistic | Settlement latency (ms) | Building | ~$95B | 2025–2026 deployment window |
| L3 — Rollup / Netting | Duopolistic | Compression ratio | Early | ~$120B | Critical infrastructure bet |
| L4 — Risk / Compliance | Fragmenting → consolidating | False positive rate | Fragmented | ~$85B | Regulatory catalyst dependent |
| L5 — Finality Anchor | Protocol-level (2–3 dominant) | Finality time (sec) | Contested | ~$170B | Long-term structural position |
| TOTAL ACSM STACK | Horizontal architecture required — no single layer wins alone | ~$650B | Composability is the moat | ||
Five stages from initial evaluation to agent-native commerce at scale. Organisations must progress sequentially — the infrastructure decisions at each stage are path-dependent for years. The ACML maps which ACSM layers become operationally relevant at each stage.
"The ACSM stack is not a prediction about which protocol wins — it is a map of the strategic positions available. The organisations that understand which layer they are competing in, and why, will make better decisions than those optimising for the wrong metric entirely."
Kishor Akshinthala · iProDecisions Research · February 2026
Data Exhibits
~5 min"The question is not whether existing rails can scale incrementally to meet agentic commerce demand. It is whether entirely new settlement architectures can be designed and deployed before winner-take-most dynamics crystallize around incumbents optimized for the wrong paradigm."
Kishor Akshinthala / iProDecisions Research · Issue 01 · February 2026 · Synthesizing: Stripe Annual Letter 2025, Chainspect, BIS CPMI
| Network | Avg TPS (Feb 2026) | Theoretical Max TPS | Gap to 1M TPS | Gap to 1B TPS |
|---|---|---|---|---|
| ICP (Internet Computer) | 1,196 | 209,708 | ~836× | ~836,120× |
| Solana | 1,140 | 65,000 | ~877× | ~877,193× |
| Ethereum (L1) | ~15 | ~15 | ~66,667× | ~66.7M× |
| Visa Network — legacy rail | ~5,600 (annual avg) | ~65,000 | ~179× | ~178,571× |
| Mastercard Network — legacy rail | ~3,200 | ~12,500 | ~313× | ~312,500× |
| Stripe Target (lower bound) | 1,000,000 | Not yet built | Baseline | 1,000× |
| Stripe Target (upper bound) | 1,000,000,000 | Not yet built | 1,000,000× | Baseline |
| Level | Capability | Current Status | Commerce Implication |
|---|---|---|---|
| L1 | Automation — filling out web forms and standard online tasks | Live | Trivial payment actions; no infrastructure strain |
| L2 | Descriptive Search — finding results based on situational descriptions | Agents are here now | Beginning of programmatic commerce at scale |
| L3 | Context Preservation — remembering user preferences and requirements | Emerging | Recurring, preference-driven agent spending patterns |
| L4 | Delegation — performing tasks on behalf of users including commerce | Building | Agent-initiated high-value transactions; liability and identity questions emerge |
| L5 | Anticipation — suggesting and initiating solutions without explicit prompts | Horizon | Fully autonomous economic actor; agent-to-agent commerce without human initiation |
Stakeholder Implications
~4 minThe infrastructure transition from human-scale to agent-scale commerce affects every actor in the financial ecosystem — but with radically different urgency timelines, strategic levers, and risk profiles. The common thread: every infrastructure decision made in 2025–2027 is path-dependent for 10–15 years. Architectural choices made under uncertainty at this moment will constrain or enable competitive positioning through 2035 and beyond.
The Builder Path
~3 minThe stakeholder analysis above addresses the Fortune 500 technology leader, the bank CTO, the cloud infrastructure strategist. But the 836,120× infrastructure gap is also the largest greenfield opportunity in financial infrastructure since the internet. The builders who capture that opportunity are often not the incumbents — they are the 15-person fintech with a technical insight about L3 rollup architecture, or the crypto protocol team that cracks programmable compliance at L4.
Most institutional research on agent commerce focuses on the large-scale deployment question: how does JPMorgan or Stripe position? This section addresses the question that is missing from 95% of research: what does a startup or SME actually do on Monday?
- 01The $650B ACSM stack is too large to attack broadly. Choose the layer where your team's technical edge is sharpest — L2 off-chain mesh, L3 ZK rollup compression, or L4 programmable compliance are the highest-leverage bets for well-capitalized technical teams right now.
- 02Do not build for the Bear Case (100K TPS). The marginal cost of building for Base Case (1M TPS) is small relative to the cost of being structurally constrained if Base materializes. Pessimism and under-engineering are not the same thing.
- 03Regulatory moats are real and available now. Teams that embed GENIUS Act and MiCA compliance as structural protocol features — not retrofitted bolt-ons — will own L4 by 2027. Most incumbents are still treating compliance as a product layer. That is your window.
- 04Composability is your differentiator vs. incumbents. Stripe, AWS, and Visa have throughput advantages. Your moat is the ability to interoperate across layers in a way they structurally cannot. Design for composability from day one, not as an afterthought.
Builder guidance is iProDecisions analytical opinion. No commercial relationship with any vendor or protocol mentioned. All recommendations are general strategic guidance; specific infrastructure decisions require independent technical and legal due diligence.
Scenario Analysis — 2030 Horizon
~4 minThree scenarios through 2030, probability-weighted. The critical cross-scenario insight: even the Bear Case demands infrastructure 83× beyond today's fastest blockchain average. The floor has permanently moved regardless of which future materializes. This is the asymmetric structure of the opportunity: the cost of building for the Base Case (1M TPS) is marginally higher than building for the Bear Case (100K TPS) — but the cost of undershooting is structurally irreversible.
Probability methodology: The 55/30/15 distribution is an analytical estimate reflecting the weight of evidence from current regulatory trajectories (GENIUS Act, MiCA), infrastructure investment signals (Stripe Tempo, OpenAI ACP), and base-rate analysis of analogous infrastructure adoption curves (mobile payments 2010–2018, cloud 2008–2016). Treat as directional confidence levels, not actuarial probabilities.
The regulator's dilemma: Regulatory inaction is not neutral. It defaults toward the Fragmented Scenario. The absence of coherent global frameworks is itself a policy choice with material, quantifiable economic costs measured in GDP foregone — the IMF estimates cross-border payment fragmentation at 0.5% of trade volume per percentage point of friction.
The inaction cost: Every quarter of delay narrows the strategic window. Infrastructure decisions made in 2025–2027 are path-dependent for 10–15 years. The cost of early action is marginal. The cost of late action is structural and likely permanent.
"Even the Bear Case demands infrastructure 83× beyond today's fastest blockchain. The floor has permanently moved regardless of which scenario materializes. Undershooting is no longer the conservative choice — it is the highest-risk choice available."
Kishor Akshinthala · iProDecisions Research · February 2026
Central Thesis & Decision Framework
~5 min"The question is no longer whether existing rails can scale incrementally. It is whether the global financial stack can be re-architected to support autonomous economic activity at planetary scale. The answer will define the competitive landscape of fintech, crypto infrastructure, and cloud-compute marketplaces for the next decade."
Kishor Akshinthala / iProDecisions Research · February 2026 · Synthesizing: Stripe Annual Letter 2025, Chainspect, Mordor Intelligence
Clickable mind map · ACSM readiness calculator · TPS gap modeler · Section explorer · Quick reference for presentations
Rate your organization 1–5 on each ACSM layer dimension. Total score maps to your Agent Commerce Maturity Ladder stage. Be honest — overestimating your stage is the most expensive form of infrastructure planning.
| ACSM Layer | Score 1 — Not Started | Score 3 — In Progress | Score 5 — Production-Grade |
|---|---|---|---|
| L1 Agent Execution | No agents in production. Evaluating Stripe ACP / OpenAI APIs. | Pilot agents in sandbox. ACP API integrated. Payment primitives tested but not at scale. | Agents transacting in production. ACP integrated. Agent identity management operational. EED measured and tracked. |
| L2 Off-Chain Mesh | All settlement on-chain or via legacy batch rails. No off-chain netting. | State channels or payment channels in pilot. Settlement latency benchmarked. Off-chain netting for high-volume workflows only. | Off-chain mesh operational at scale. Settlement latency sub-100ms for agent transactions. Netting ratio measured and optimized. |
| L3 Rollup / Netting | No ZK rollup or batch netting. Each transaction settled individually on L5. | ZK rollup protocol selected. Compression ratio benchmarked. Batch netting tested on non-critical workflows. | ZK rollup operational in production. Compression ratio >100:1. Effective throughput at 1M+ TPS for your agent workload profile. |
| L4 Risk / Compliance | Compliance is a manual, post-transaction process. No smart contract enforcement. No GENIUS Act readiness. | Smart contract AML/KYC in pilot. GENIUS Act compliance assessed. EU MiCA readiness under review. | Programmable compliance operational. False positive rate benchmarked. GENIUS Act + MiCA compliant. Smart contracts enforcing AML/KYC at transaction speed. |
| L5 Finality Anchor | No blockchain finality in production. Legacy batch settlement only. | L5 protocol selected (ICP/Solana/ETH L1). Settlement anchoring in pilot. Finality time benchmarked. | Cryptographic finality operational for all batched L3 settlements. Finality time <5 seconds. Failover protocol defined. |
The eight actions above apply to all organizations — but sequencing differs critically by stage. Stage 1 organizations attempting Stage 4 infrastructure generate the architecture debt that kills agent commerce programs.
Evaluate → Pilot
Deploy
Scale → Native
The Stripe Annual Letter is the clearest institutional signal in 2026 that the transition from human-initiated to machine-initiated commerce is not a speculative future state — it is the active design thesis of the company that processed 1.6% of global GDP last year. Their infrastructure moves (ACP, Tempo, Bridge) are the opening gambit of a decade-long re-architecture. The ACSM framework provides the structural vocabulary for how that re-architecture plays out across five distinct but composable layers.
The most important insight from this analysis is not the 836,120× gap — it is the fact that the gap itself is investable. The total ACSM TAM across all five layers is approximately $650B by 2030. No single company will capture all of it. The organisations that explicitly map their position within the ACSM stack, identify their layer-specific moats, and begin infrastructure decisions in 2025–2027 will define the financial infrastructure of the agentic era.
The asymmetry of the situation bears repeating plainly: infrastructure decisions made in the next 18–24 months will be path-dependent for 10–15 years. The organisations that act in 2025–2027 are not taking a leap of faith — they are responding rationally to the most explicit infrastructure demand signal a major platform company has ever published. The organisations that wait are the ones making the speculative bet.
"The organisations that explicitly map their ACSM position and act in 2025–2027 will define the financial infrastructure of the agentic era. Those that wait are not being conservative — they are making an active, undeclared bet that agent-scale commerce does not materialise in their sector."
Kishor Akshinthala · iProDecisions Research · February 2026
- —iProDecisions is the advisory and thought leadership platform of Kishor Akshinthala — serial founder and cross-disciplinary expert in AI, Blockchain, Cloud infrastructure, and Digital Growth Strategy.
- —This report is part of the iProDecisions Autonomous Enterprise Research Series — six reports mapping the infrastructure, organizational, governance, and market dimensions of the agentic AI transition. Issue 02 — The Agentic Workforce: read now ↗
- —All reports are anchored in validated primary-source data, named proprietary frameworks (ACSM, ACML, Economic Event Density), and actionable strategic intelligence — not secondary aggregation or editorial opinion.
- —Advisory sessions available from $97. Book at iprodecisions.com ↗
Take the ACSM framework and ACML maturity ladder directly into your infrastructure strategy. Kishor works with enterprise leaders, fintech founders, and crypto infrastructure teams on agent commerce positioning — drawing on direct operational experience with 200+ production agents at CAIBots and 25+ years of enterprise financial services.
Steelman Counterarguments & Analytical Limitations
~3 minInstitutional-grade research requires engagement with the strongest objections to its central thesis. Three counterarguments deserve serious consideration before accepting this analysis.
Counterargument 1: The 1B TPS figure may be aspirational, not architectural. The Collison brothers' "1M or even 1B TPS" statement is a single sentence in a CEO letter to stakeholders — not a technical specification or engineering target. Critics reasonably argue that executive-level projections about transformative technology timelines have historically been wrong by 5–10 years (mobile payments, enterprise AI, blockchain enterprise adoption). The rebuttal: The specific infrastructure moves that followed the letter — Stripe Tempo, ACP, Bridge — are not aspirational. They are capital-deployed, team-committed, technically specified infrastructure investments. Aspirational CEO letters do not trigger these moves. Architectural conviction does. Further, our Bear Case (100K TPS, 15% probability) still demands 83× current capacity — even the conservative scenario requires re-architecture.
Counterargument 2: Existing infrastructure may scale faster than modeled. This analysis is anchored to February 2026 TPS benchmarks. Ethereum's Dencun upgrade (March 2024) reduced L2 fees by 10×. Solana's continuous performance improvements are documented. Layer 2 solutions are compressing effective throughput faster than linear extrapolation suggests. If ZK rollup technology matures faster than our scenarios model, the gap closes from both ends — demand grows, but so does supply. The rebuttal: The ACSM framework is explicitly designed for this scenario. Composability across layers — not any single layer's TPS — is the architectural thesis. Even if L5 throughput doubles annually for five years (highly optimistic), the EED calculation in §01½ shows that demand from agent workflows scales faster at Stage 4 adoption. The gap is not closing incrementally; it is being bridged architecturally, exactly as Stripe described.
Counterargument 3: The total ACSM TAM estimates are directional at best. The $650B figure is derived from Mordor Intelligence's fintech TAM apportioned by layer capital intensity — a methodology that is defensible but not auditable from first principles. Different apportionment assumptions yield materially different layer TAMs. The rebuttal: The framework's strategic value does not depend on the precision of the TAM estimates. Whether L1 TAM is $120B or $240B, the directional conclusion — that it is winner-take-most and the window is open now — holds. The TAM estimates are orientation tools, not investment theses. Organizations making infrastructure bets should conduct their own diligence using the ACSM as a structural vocabulary, not as a valuation model.
Scope limitations: This report is anchored primarily in US and EU regulatory context (GENIUS Act, MiCA). Agent commerce dynamics in China — where a parallel and potentially incompatible infrastructure stack is being built — are underrepresented. The Bear Scenario explicitly models geopolitical fracture as the primary risk driver; readers in Asia-Pacific markets should weight this scenario higher than the 15% global probability suggests for their specific contexts.
"The most dangerous assumption in agent commerce infrastructure planning is that 'wait and see' is a neutral position. It is not. It is an active bet on the Bear Case materializing — and even the Bear Case still demands 83× your current infrastructure."
Kishor Akshinthala · iProDecisions Research · Issue 01 · February 2026