Embedded wallets as fintech's Trojan horse into Web3 (Stripe's five layers)
ConfidenceLikelyUpdated2026-08-14Review by2027-02-10Sources7Machine-translatedOriginal (JA)
Wiki route
This entry sits under fintech index. Read it with Japan’s financial-regulation framework for tokens, cryptoassets, and payments for adjacent context and the three-layer structure of Japan’s stablecoin regime for the broader system boundary.
[!info] TL;DR Stripe’s public materials show that payments, stablecoin orchestration, embedded wallets, a payments-focused chain, and agent payments can be combined. Stripe reported that more than five million businesses used it directly or through a platform in 2025. It completed the Bridge acquisition in February 2025, acquired Privy in July, and announced Tempo in September; Tempo now describes its mainnet as live. This does not prove that every Stripe business uses wallets, stablecoins, Tempo, and AP2 / x402 as one integrated system. The “five layers” below are an analytical model of functions that could be combined.
Key facts
- Stripe reported that more than five million businesses used it directly or through a platform in 2025. This figure is neither the number of embedded-wallet deployments nor a ceiling on potential deployments.
- Stripe completed its acquisition of Bridge in February 2025. Privy announced the acquisition agreement in June 2025, while Stripe’s annual update records the acquisition in July. Public materials do not support the claim that both companies were acquired simultaneously in June 2025 or that the combined announced price was $2.2 billion.
- Tempo was announced in September 2025 as a payments-first blockchain incubated by Stripe and Paradigm, and its official website now describes mainnet as live.
- Tempo identifies sub-second finality and predictable low fees as design goals, but chain finality is not the same as end-to-end cross-border settlement time. Official materials do not support a universal comparison of “SWIFT in three days for $25” versus “Tempo in five seconds for almost no fee.”
Source note: the four points above use direct disclosures from the Stripe 2025 annual update, Bridge acquisition completion, Privy acquisition agreement, Tempo announcement, and Tempo official site. Do not infer adoption, pricing, or end-to-end settlement figures that these materials do not publish.
Mechanism / How it works
Functions and boundaries established by public information:
| User journey | Function established by public information | Verification boundary |
|---|---|---|
| Login / onboarding | Privy provides embedded wallets, and wallets can be provisioned from Stripe Projects | Wallet-creation conditions, custody, recovery, and consent design depend on each application’s implementation |
| On-ramp / off-ramp | Stripe / Bridge provides fiat and stablecoin orchestration | Supported assets, regions, fees, and settlement differ by product and jurisdiction |
| Cross-border payment | Tempo targets stablecoin payments with sub-second finality and predictable low fees | Chain finality does not include off-ramp processing or delivery to the recipient in an end-to-end time |
| Agent payment | AP2 is a payment-agnostic open protocol, and an A2A x402 extension has also been announced. Stripe describes machine payments including stablecoin micropayments | AP2 / x402 adoption, authorization, assets, merchant acceptance, and fee policy depend on each implementation |
| Payout / revenue distribution | Programmable stablecoin settlement can be embedded | It does not guarantee instant, continuous, or free settlement and depends on compliance, liquidity, and off-ramps |
→ A user experience can hide crypto rails in the backend, but individual product announcements do not establish that users will never notice the chain or that one company automates the entire journey.
Stripe five-layer collapse architecture:
- L5 application / distribution: Checkout, Connect, and more than five million businesses using Stripe directly or through platforms
- L4 wallet interface: Privy embedded wallets and their integration with Stripe Projects
- L3 stablecoin orchestration: Stablecoin infrastructure provided by Bridge. Public materials do not establish a particular “USDB” as the default asset across the stack
- L2 payment chain: Tempo, an independent payments-first blockchain incubated by Stripe / Paradigm
- L1 agent-protocol options: AP2 / x402. Their public specifications may be combined, but this does not mean Stripe owns both protocols or operates all five layers as one system
This classification is an analytical checklist for examining layers from distribution to protocol, not a stack diagram that directly represents product ownership or technical dependencies. The wallet interface matters because it is close to identity, authorization, and recovery, but using Privy alone does not necessarily confer exclusive control over spending data or agent permissions.
Origin & evolution
The public-record milestones are the completion of the Bridge acquisition in February 2025, Privy’s announcement of its acquisition agreement in June and Stripe’s record of the acquisition in July, and Tempo’s announcement in September. They show expansion into adjacent capabilities, but there is no verified public forecast or result showing that 5–10% of Stripe’s more than five million businesses will switch to USDC / Tempo in 2026–2027. Useful leading indicators would instead track wallet provisions, active wallets, stablecoin volume, actual settlement on Tempo, and availability by region using consistent periods and definitions.
Related
- Wiki Index
- Embedded-wallet disintermediation — overview
- Embedded-wallet network effects and the integrated-provider moat
- Protocol hedging — the Stripe pattern
- Two tracks for AI payments
- The bifurcation of onchain finance and crypto culture
Sources
- Stripe 2025 annual update (2026-02-24) — More than five million businesses; public information on Privy / Tempo, stablecoins, and machine payments.
- Stripe completes Bridge acquisition (2025-02-04) — Completion date for the Bridge acquisition.
- Privy acquisition announcement (2025-06-11) — Agreement date and closing conditions.
- Privy is live in Stripe Projects (2025-10-15) — Wallet provisioning from Stripe Projects.
- Introducing Tempo (2025-09-04) / Tempo official site — Incubators, design goals, and current network status.
- Google Cloud: AP2 announcement (2025-09-16) — The payment-agnostic protocol and A2A x402 extension.
Discovery
Keep reading
Read next
- Enterprise IT procurement timing · a buyer-specific verification frameworkProcurement timing should be checked against at least the following buyer-specific events.
- eRupee India pilot status 2026 — retail + wholesale dual track, UPI interoperability, programmable-money use casesThe two tracks launched in 2022-11 and 2022-12. The current RBI FAQ describes three ongoing e₹-W use cases: funds settlement for secondary-market government-securities transactions, inter-ba...
- EU MiCA Implementation Status, July 2026 · ESMA EMT/ART Registers and Restrictions on Non-Compliant StablecoinsUnder the EU Markets in Crypto-Assets Regulation (MiCA, Regulation (EU) 2023/1114), the EMT / ART provisions began to apply on 2024-06-30, the other principal provisions on 2024-12-30, and t...
Links here
- Commoditization of Agent payment protocols and the upward migration of valueAfter 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 distr...
- 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...
- Embedded-wallet custody bankruptcy mechanics · what happens to end-user funds if Privy / Stripe / Coinbase CDP / AWS Bedrock failsEnd-user funds in an embedded wallet are on-chain at an address the user controls jointly with the provider, not on the provider's balance sheet. If Privy, Stripe (the Privy parent), Coinbas...
- Embedded-wallet landscape 2026 · post-consolidation provider mapBy mid-2026 the embedded-wallet category has compressed from a long tail of 20+ SDK vendors into a default-tier duopoly (Privy under Stripe, Coinbase CDP) and a secondary tier (Magic, thirdw...
- Embedded-wallet network effects · the moat is in the integrator, not the wallet itselfThe more integrators there are → the more users can have their wallet "follow me" across dApps → the more new integrators tend to pick the same wallet → the flywheel starts turning.