Commoditization of Agent payment protocols and the upward migration of value
ConfidenceLikelyUpdated2026-08-14Review by2027-08-14Sources5Machine-translatedOriginal (JA)
Wiki route
This entry sits under AI Agent payment protocols overview · a 7-protocol survey. Read it against payments index for peer / contrast context and systems index for the broader system / regulatory boundary.
Key facts
- Stripe 5 stack = Tempo (L1) + Privy (wallet) + USDB / Bridge (stablecoin) + Stripe Checkout (SDK) + 5M+ merchants (traffic) •
- Privy was acquired by Stripe in 2025 , positioned as the default for embedded wallets •
- Coinbase is the contrasting route: Base (L1) + CDP (wallet) + USDC (currency) + Commerce (SDK) •
Mechanism / How it works
After protocol commoditization, take rate cannot be extracted from an open-source standard (one cannot levy an HTTP-protocol fee). Value capture is forced to migrate upward to vertical distribution control points: whoever controls the Embedded Wallet-Driven Fintech Disintermediation · Privy/CDP/Magic/Web3Auth of user login → controls the agent’s default payment path → levies the transaction fee.
The logic of Stripe’s 5-stack full stack:
- L1 chain (Tempo · Stripe + Paradigm) — payment-optimized chain, 7-10 validators, institutional-grade credentials
- L2 / wallet (Privy · acquired by Stripe) — Embedded wallets as fintech's Trojan horse into Web3 (Stripe's five layers), embedded in the checkout of 5M+ Stripe merchants
- Stablecoin (USDB / Bridge · under Stripe) — native settlement currency (see Token strategy for public stablecoin chains)
- SDK (Stripe Checkout / Connect) — zero-code embedding on the merchant side
- Merchant traffic (5M+ merchants) — actual control of end-point distribution
With each layer added, the vertical dominance deepens — the larger the protocol as a public good, the stronger Stripe’s private-good network effect.
Origin & evolution
2024 Stripe acquired Bridge (USDB issuer) → entered the stablecoin layer. 2025.04 Stripe + Paradigm jointly established Tempo (payment L1) → occupied the chain layer. 2025.07 Stripe acquired Privy → occupied the wallet layer. 2025.09 At the AP2 launch, Stripe was not on the 60+ partner roster — Stripe’s strategy is explicitly to “not participate in the protocol-hegemony contest, and only occupy distribution.” After FIDO took over AP2 → became AAIF in mid-2026 年, Stripe’s 5-stack full-stack position became essentially unchallengeable.
Analogy: Visa / Mastercard do not write the ISO 8583 protocol spec either, yet they still capture the bulk of payment value — the protocol is a public good, distribution is a private good (see Protocol-Layer Multi-Line Hedge Strategy).
Related
- Wiki Index
- AI Agent payment protocols overview · a 7-protocol survey
- AI Agent payment 7-protocol layering table
- Five-layer unbundling of central-banking functions
Sources
- Privy “Privy and Stripe: Bringing crypto to everyone” (Stripe’s acquisition of the wallet layer) — https://privy.io/blog/announcing-our-acquisition-by-stripe
- Tempo official website (Stripe + Paradigm’s payment L1 · chain layer) — https://tempo.xyz/
- Coinbase Developer Platform (contrasting route Base + CDP + USDC + Commerce) — https://docs.cdp.coinbase.com/
- Coinbase x402(public-good commoditization of the protocol layer) — https://github.com/coinbase/x402
- Google AP2(contrast in protocol hegemony · Stripe does not participate) — https://github.com/google-agentic-commerce/AP2
Discovery
Keep reading
Read next
- The current state of AI companies' payment methodsSource note: public billing / payment documentation and public AI-company product pages; cross-border payment implications are framework-level synthesis.
- AI-driven trading regulation · Japan FSA / SESC plus global FCA / SEC / ESMA comparison 2026AI-driven trading regulation in 2026 sits on top of the existing algorithmic-trading regulatory perimeter rather than as a separate "AI trading rule." The Japan FSA + SESC (Securities and Ex...
- AP2 adoption landscape · Google closed loop vs the four-protocol warGoogle's combination of 4 root pillars: Google Pay (6 億 mobile wallet users) + Gemini (hundreds of millions of Android/Chrome/Workspace touchpoints) + influence over the W3C VC standard (a c...
Links here
- Agent Payment Protocol four-way comparison matrix 2026 · AP2 / x402 / Skyfire / Nevermined plus ERC-7715 + Lit PKPSelecting an agent payment rail in 2026 is not "pick the best protocol" — it is "compose the layer cake correctly so the merchant accepts, the wallet authorizes, and the regulator does not b...
- Agent Protocol Mainnet Adoption · 2026-05 Production-Readiness SnapshotAs of May 2026, the agent-payment protocol stack has bifurcated sharply between mainnet-shipped infrastructure and testnet / consortium-only specs. The production-live tier is dominated by x...
- AI Agent payment protocols overview · a 7-protocol surveyThe 7 protocols divide labor by layer. The intent layer (where the user expresses "I want to buy Y for X yen") is handled by AP2 / SPT / ACP, which process the mandate's 3-layer trust chain...
- AI Agent payment 7-protocol layering tableThe intent layer answers "what does the user want to do." AP2 defines a 3-layer trust-chain mandate: Intent (user ↦ agent · authorize purchase of X) → Cart (agent ↦ merchant · place the orde...
- Stripe Agent Toolkit · Stripe's First-Party Agent SDK and Its Position vs x402 / Privy / AWS AgentCoreThe Stripe Agent Toolkit, launched in late 2024 and significantly expanded through 2025, is Stripe's first-party SDK for letting AI agents transact through the existing Stripe rails — Issuin...