Embedded Wallet-Driven Fintech Disintermediation · Privy/CDP/Magic/Web3Auth
ConfidenceCertainUpdated2026-08-14Review by2026-11-12Sources8Machine-translatedOriginal (JA)
Wiki route
This entry sits under fintech index. Read it with Japan Financial Regulation — Legal Framework for Tokens, Crypto Assets, and Payments for adjacent context and Three-Layer Structure of Japan's Stablecoin Regulatory Regime (JPYC, USDC, Project Pax) for the broader system boundary.
[!info] TL;DR Embedded wallets connect familiar email, SMS, or OAuth login flows to in-app wallets, offering an onboarding path that does not require a seed phrase or browser extension. Privy, Coinbase Developer Platform, Magic, and Web3Auth are notable implementation candidates, but key management, supported chains, account abstraction, pricing, and custody boundaries differ by product and plan. Stripe did not disclose the Privy acquisition price, so estimates should not be stated as fact.
Key facts
- Privy announced its agreement to be acquired by Stripe on 11 June 2025. The price was not disclosed; Privy reported more than 75 million accounts and more than 1,000 developer teams at the time. ^[https://privy.io/blog/announcing-our-acquisition-by-stripe]
- Coinbase CDP documents non-custodial user wallets using email, SMS, or social login separately from system wallets controlled through APIs and protected in a TEE. ^[https://docs.cdp.coinbase.com/wallets/non-custodial-wallets/overview]
- Magic documents email OTP, SMS, OAuth, and support for more than 30 blockchains. ^[https://docs.magic.link/embedded-wallets/quickstart/integration]
- Web3Auth publishes social login, MFA, MPC/TSS, and pre-generated-wallet capabilities by plan. ^[https://web3auth.io/pricing.html]
Mechanism / How it works
Published specification comparison of four products (checked 30 July 2026). The table compares only feature boundaries documented by each provider; it omits undisclosed key-share counts, integration line counts, and customer-conversion estimates. ^[https://docs.privy.io/wallets/overview/embedded; https://docs.cdp.coinbase.com/wallets/non-custodial-wallets/overview; https://docs.magic.link/embedded-wallets/quickstart/overview; https://web3auth.io/pricing.html]
| Dimension | Privy (Stripe) | Coinbase CDP | Magic | Web3Auth |
|---|---|---|---|---|
| Published positioning | Stripe company; self-custodial user wallets and developer-controlled wallet fleet | Coinbase non-custodial user and system wallets | Magic embedded-wallet SDK | Torus Labs / Web3Auth Wallet Services |
| Authentication | Email, SMS, OAuth, passkeys, and others | Email, SMS, and social login; API keys for system wallets | Email OTP, SMS, OAuth, and others | Email, SMS, wallets, passkeys, social login, and MFA |
| Key / control boundary | Choice of user-controlled or developer-controlled wallets with policies, MFA, and m-of-n approvals | Non-custodial user wallets; system-wallet keys protected in a TEE | Non-custodial embedded wallets and pre-generated wallets | Self-custodial and MPC/TSS configurations by plan |
| Supported scope | Official docs list EVM/SVM plus Bitcoin, TRON, Stellar, and others | EVM, Solana, and others by product | More than 30 blockchains | Blockchain-agnostic SDK; compatibility must be checked per SDK |
| Selection context | Where Stripe / Privy integration and policy engine are important | Where Coinbase wallet, onramp, paymaster, or x402 integration is important | Where broad client SDKs and authentication UI are important | Where configurable authentication, MFA, and MPC/TSS are important |
UX architecture checklist to verify per deployment (draft):
- Onboarding: verify login providers, seed-phrase display, custody, key export, and recovery for each product and plan. Social login does not by itself imply a TSS backend or seedless recovery.
- Delegated execution / sessions: verify how the wallet implements session keys, spending limits, expiry, revocation, and re-authentication. EIP-7702 delegation and an ERC-7715 permission request are separate layers; neither alone guarantees a prompt-free session after one approval.
- Gas: verify supported chains, tokens, quotas, and fallback for ERC-4337 paymasters, operator sponsorship, or ERC-20 gas payment. Paying gas in USDC is not a common capability of all four products.
- Recovery: verify whether a product uses devices, cloud services, server shares, MPC/TSS, or guardians and where control sits. Do not assume a common “device + cloud + server” split.
- Cross-chain: verify the bridge or messaging provider, finality, fees, failure recovery, and balance presentation for each deployment. Hyperlane / CCIP and a single-balance UX are not automatically included with an embedded-wallet product.
Standards status (30 July 2026): EIP-7702 is Final and writes a persistent delegation indicator to an EOA until it is explicitly cleared or replaced; it is not inherently a temporary upgrade. ERC-7715 is a Draft wallet permission-request interface, not evidence of a uniformly deployed granular-permission layer. For it and ERC-4337, implementation must be verified per wallet, chain, bundler, and paymaster. ^[https://eips.ethereum.org/EIPS/eip-7702] ^[https://eips.ethereum.org/EIPS/eip-7715] ^[https://eips.ethereum.org/EIPS/eip-4337]
Origin & evolution
From 2018 to 2022, browser extensions and seed phrases were the dominant model and the crypto-native boundary was clear. In 2023-2024, embedded wallets and Wallet-as-a-Service expanded from dApps into fintech, gaming, and social products. Stripe completed the Bridge acquisition on 4 February 2025 and announced the Privy acquisition agreement on 11 June 2025. In May 2026, Stripe / Privy and AWS announced AgentCore payments, extending the embedded-wallet use case to agent payments. ^[https://stripe.com/newsroom/news/stripe-completes-bridge-acquisition; https://privy.io/blog/announcing-our-acquisition-by-stripe; https://stripe.com/newsroom/news/aws-stripe-agentcore-privy]
Related
- Wiki Index
- Embedded wallets as fintech's Trojan horse into Web3 (Stripe's five layers)
- Embedded-wallet network effects · the moat is in the integrator, not the wallet itself
- The 2 Payment Tracks of the AI Industry
- Protocol-Layer Multi-Line Hedge Strategy
Sources
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...
- AP2 · Google Agent Payments Protocol overviewAP2 extends the traditional user-merchant two-party payment into a user-agent-merchant three-party structure, introducing 4 core components:
- Coinbase CDP · developer platform · AI agent on-chain wallet infrastructureCDP compresses "Web3 integration" from "months of development + self-built infrastructure" into "minutes of API integration". With a single SDK line, developers can embed an onchain wallet i...
- 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...