What's the difference between Privy's fiat onramp and Coinbase's onramp? Why wouldn't developers just use Coinbase's solution?
The two are fundamentally differently positioned, which determines their respective customer segments are also completely different. Coinbase Onramp (now Coinbase Commerce): Coinbase's onramp solution is primarily a 'redirect users to Coinbase to complete the purchase' mechanism. After clicking, users typically need to leave the original app, enter Coinbase's environment, login or create a Coinbase account, complete the purchase, then transfer assets back to the original app. This flow has multiple handoffs and interruptions, exposing Coinbase as an independent brand to users, with developers having no control over their users' behavior on Coinbase. Privy × Stripe difference: Privy's entire design logic is 'your brand, your users, Privy's infrastructure working in the background.' From signup to asset purchase, users complete everything within the app developer's interface, unaware that Privy or Stripe is operating behind the scenes. For RWA platforms (e.g., a tokenized real estate investment platform), this difference is especially significant: if users are redirected to Coinbase during RWA token purchase, they may buy other assets directly on Coinbase and forget to return to the original platform. Privy's embedded model keeps users entirely within the RWA platform's ecosystem. Another difference is compliance responsibility allocation: Stripe as Merchant of Record bears KYC and compliance responsibility, letting developers skip needing payment or financial service licenses. Coinbase's model typically makes developers responsible for their users' compliance, or requires using Coinbase's compliance framework while being constrained by its product design.
How did stablecoins reach 70% of wallet balances on Privy's platform? What drove the shift from 25-30% a year ago?
This shift from 25–30% to 70% occurred within 9–12 months, and is one of the most direct market structure shifts Privy has observed in crypto financial infrastructure. Three primary drivers. First, post-GENIUS Act institutional compliance certainty: the 2026 US GENIUS Act provided relatively clear compliance pathways for stablecoin issuance, letting businesses (global payroll platforms, cross-border remittance services, enterprise treasury management) stop treating stablecoins as 'crypto experiments' and start using them as 'production-grade payment rails.' Privy platform global payroll and remittance customers (Deel, Majority, etc.) migrated to stablecoins at scale — this category alone significantly raised stablecoin's balance share. Second, perpetuals and trading platforms shifting to stablecoins: perpetuals platforms like Hyperliquid and DEX aggregators like Jupiter use stablecoins as primary settlement and margin assets. These platforms' large transaction volumes represent a significant portion of Privy's network, and in bear markets or risk-off environments, traders tend to park more funds in stablecoins. Third, indirect RWA Treasury token effects: tokenized short-term Treasuries (BlackRock BUIDL, Ondo OUSG) are statistically in 'other' in Privy's balance accounting, but their primary entry capital is stablecoins — users first obtain stablecoins, then use them to buy RWA tokens. RWA growth indirectly drove stablecoin flow growth. Practical implication for developers: if your app is built on Privy, your user base behaves similarly to Privy's overall platform — most active users ultimately hold stablecoins as their primary position. Offering a one-click stablecoin-to-RWA-token conversion in your app may have lower 'cognitive difficulty' than directly promoting RWA tokens, because users have already accepted the stablecoin holding concept.
Are Privy's embedded wallets 'custodial' or 'non-custodial'? Does this affect RWA asset legal ownership?
This is an important dimension for RWA developers to deeply understand when choosing Privy. Privy's answer: both are supported, and different modes can be applied to different users or different markets on the same platform. Custodial mode: Privy or its authorized partners hold users' private keys; users don't need to manage any passwords or seed phrases. Ramp uses custodial mode — making compliance and user experience easier to control, since developers can restrict or recover user asset access in specific circumstances (e.g., regulatory requirements). For RWA assets, custodial mode lets platforms directly enforce KYC whitelist controls (only allowing KYC-approved addresses to hold RWA tokens) — the compliance prerequisite required by most current RWA token smart contracts. Non-custodial mode: users control their own private keys (through Privy's key management infrastructure, letting users export and self-custody at any time). This gives users more complete asset autonomy and lets assets flow more broadly across DeFi ecosystems (unconstrained by custodians). Platforms requiring high-speed trading like Hyperliquid use non-custodial mode. Impact on RWA legal ownership: regardless of custodial or non-custodial mode, the underlying legal ownership of RWA tokens in Privy wallets depends on the RWA token's own legal structure (SPV equity, trust beneficial interest, or contractual obligation) — not Privy's custody setting. Privy is the wallet layer, not the asset legal structure layer. But custodial mode may make it easier for users to hold RWA tokens under KYC whitelist controls (since the platform can uniformly manage addresses), while in non-custodial mode, whether users can continue holding RWA tokens after transferring to self-controlled addresses depends on whether the RWA protocol's whitelist recognizes that address.
As a developer wanting to build an RWA investment platform, what are the main selection factors comparing Privy to alternatives like Dynamic or Web3Auth?
This is a practical selection question, with several main comparison dimensions. Stripe ecosystem integration depth: after Stripe's acquisition, Privy is natively integrated with Stripe's entire payment stack (Stripe Payments, Bridge stablecoin infrastructure, Stripe Treasury). If your RWA platform needs users to move between traditional banking and DeFi (e.g., ACH deposit → stablecoin → RWA tokens), Privy + Bridge + Stripe is currently the most complete single-vendor solution. Dynamic and Web3Auth don't have comparable native payment infrastructure integration depth. Fiat onramp coverage: Privy's global fiat onramp (Stripe Crypto Onramp for US/EU + aggregator for 100+ countries) is a clear advantage after this update. Dynamic and Web3Auth both require developers to additionally integrate MoonPay, Transak, or similar — increasing integration cost and maintenance complexity. Wallet type flexibility: Dynamic has stronger support for 'letting users connect their existing external wallets (MetaMask, Phantom) into apps' — better for serving users with existing DeFi experience and their own wallets. Privy is better for serving 'starting from zero, crypto-uninitiated' new users — a more important scenario for the RWA ordinary investor market (non-DeFi-native users). Pricing and scale: Privy's pricing model is account-count-based SaaS subscription; unit cost at large user counts is generally lower than a combination of transaction-volume-charged independent onramp providers. But for early-stage teams, Privy's starting cost may be higher than open-source Web3Auth. Compliance focus: if your RWA platform primarily serves institutional investors (requiring KYB, enterprise accounts, custom compliance flows), Privy's current tools are more consumer-app-oriented — may need supplementing with other compliance tools. If primarily serving retail, Privy + Stripe KYC coverage is sufficient for most scenarios.
On July 7, 2026, embedded wallet infrastructure company Privy (acquired by Stripe in 2025) officially launched Global Fiat Onramps — allowing any app built on Privy to let users purchase crypto with a credit card, Apple Pay, Google Pay, or bank account directly inside the app and into their wallet, without integrating any separate third-party payment provider. In the US and EU, this flow is handled by Stripe Crypto Onramp for payment processing, KYC, and compliance; in 100+ other countries, Privy's own global aggregator routes users through the best available local payment provider. This seemingly 'technical' developer tool update has profound structural implications for the RWA ecosystem: it eliminates the last most difficult friction on the path from 'new user starting from zero to holding RWA tokens' — no longer needing to first open an exchange account, buy crypto, and transfer it to a dApp wallet; the entire flow can now happen within a single app from signup to funded position.
Privy is a 'Wallet-as-a-Service' company whose product lets developers embed a crypto wallet into any app with a few lines of code — users can create wallets with email, social login (Google, Apple), or traditional accounts, without downloading MetaMask, memorizing seed phrases, or understanding private key concepts. The wallet feels like a normal account to users, with the underlying crypto mechanics completely invisible to ordinary people. Privy was acquired by Stripe for approximately $230 million in 2025. Current Privy scale: over 120 million global accounts, 2,000+ developer teams, 180+ countries, and over $15 billion in monthly processing volume. Privy users include Hyperliquid (trading platform), Jupiter (Solana DEX aggregator), Deel (global payroll), and Majority (cross-border remittance) — spanning DeFi-native, enterprise payroll, and consumer fintech scenarios.
Stripe's strategic intent in acquiring Privy requires another acquisition to fully understand: Stripe also acquired Bridge (stablecoin infrastructure platform) in early 2026. Privy + Bridge + Stripe's existing payment infrastructure forms a complete chain from 'user onboarding' → 'wallet creation' → 'fiat deposit' → 'stablecoin holding' → 'cross-border payment' — with Stripe controlling every step.
Before this update, a dApp or RWA platform built on Privy that wanted users to buy crypto assets directly in-app needed to independently integrate MoonPay, Transak, or other fiat onramp providers — each with their own SDK, KYC flow, geographic coverage, and fee structures. A platform needing to cover 20 countries might need to integrate 3–5 different onramp providers for acceptable coverage. After this update, developers using Privy need just one API integration. The app developer configures a single 'Destination Wallet,' and Privy automatically routes to the most appropriate payment provider based on user geography (Stripe Crypto Onramp for US and EU; Privy aggregator for 100+ other countries). The user experience: open the app → login or create account (Privy wallet auto-created) → tap 'Fund' → enter credit card info (or Apple Pay) → confirm → crypto assets arrive. This flow can complete in 2–3 minutes without users leaving the app.
Stripe acts as 'Merchant of Record,' bearing the entire KYC flow, sanctions screening, identity verification, fraud protection, and dispute handling — meaning developers integrating Privy don't need to apply for payment licenses, build compliance flows, or maintain KYC systems; these complex compliance burdens are fully transferred to Stripe.
To understand this update's strategic significance, it needs to be placed in the context of Stripe's entire crypto financial infrastructure buildout over the past two years. Stripe Sessions 2026 (April) announced Treasury balances soon backed by Privy's non-custodial wallets for instant cross-border money movement in 150+ markets; Bridge's Open Issuance lets businesses issue their own stablecoins; Stripe Global Payouts can now pay recipients in 160 countries with stablecoins. Privy's global fiat onramp is the final missing piece of this ecosystem: if Bridge solved 'stablecoin cross-border movement,' Privy's fiat onramp solves 'how ordinary users enter this system.' From a competitive perspective, Privy's platform supporting 120M+ accounts and $15B+ monthly processing, combined with Stripe's 8M+ global merchants and existing payment infrastructure, makes this combination far more competitive in the fiat onramp market than standalone providers like MoonPay and Transak — who can only provide fiat onramp services, while Stripe's combination provides end-to-end solutions from merchant payments to user holdings. For centralized exchanges like Coinbase and Kraken, Stripe+Privy is a meaningful threat: it lets third-party apps directly provide seamless 'fiat to crypto' experiences without requiring users to open exchange accounts — weakening centralized exchanges' traditional position as 'the only fiat-to-crypto gateway.'
Privy's fiat onramp impact on the RWA ecosystem can be analyzed across several concrete dimensions. First, RWA platform user acquisition friction drops dramatically. Currently, a new user wanting to purchase BlackRock BUIDL (tokenized Treasury) or Ondo OUSG typically needs: open a Coinbase account (KYC required) → buy USDC → transfer USDC into a DeFi protocol supporting BUIDL/OUSG → purchase RWA tokens. 3–5 steps, potentially 1–2 days (including KYC review). With Privy fiat onramp integration, the theoretical new flow: enter RWA platform → create account with email (Privy auto-creates wallet) → enter credit card to buy USDC → directly buy RWA tokens with USDC. The entire flow potentially compresses to 10–15 minutes. Second, first-entry barriers for non-crypto-native users vanish. In the 'one API from credit card to funded wallet' model, users don't need to know what a wallet is, don't need to manage private keys, don't need to understand gas fees — they just need 'I want to buy this RWA token and I have a credit card.' This expands RWA's potential user base from 'crypto users with DeFi experience' to 'any internet user with a credit card.' This is a structural inflection point in the RWA adoption curve. Third, RWA platform development complexity drops dramatically. A startup building an RWA investment platform previously needed: integrate a KYC provider (Jumio, Persona, etc.), integrate a fiat onramp (MoonPay, etc.), build compliance pipelines, integrate DeFi protocol APIs, and build wallet management systems. Each step has separate contracts and integration costs. Privy combines three of these steps (wallet, KYC via Stripe, fiat onramp) into one, letting developers complete in weeks what previously took months. Fourth, the path combining AI agents and RWA becomes clearer. Stripe Sessions 2026 announced that Privy supports AI agents using programmable wallets for investment and transactions, including trigger-based micropayments and buy/sell/hold crypto use cases. This means an AI agent could in the future operate: sense new funds entering a user account (trigger) → automatically use a Privy wallet to purchase specific RWA tokens (e.g., tokenized Treasuries) → return yield to user account. The entire RWA investment flow can be AI-agentized, with the entry point being a familiar consumer app interface.
The deeper context of this news is a striking structural data shift on the Privy platform: one year ago, stablecoins represented roughly 25–30% of total wallet value across Privy's network; today that share has climbed to approximately 70%. This shift reflects two parallel trends: new fintech (global payroll platforms, cross-border remittance apps, startup treasury management) is migrating en masse to stablecoin rails, while trading platforms and perpetuals exchanges increasingly use stablecoins as settlement media. From an RWA perspective, what does '70% of wallet balances are stablecoins' mean? It means users' mental models have accepted 'I hold dollar-equivalent stable assets on a digital platform' — and tokenized Treasury tokens (BUIDL, OUSG) relative to stablecoins represent the next step: making these 'stationary dollar stablecoins' start generating yield. If fiat onramps bring more users to hold stablecoins, those stablecoins are potential purchasers of RWA Treasury tokens — stablecoin adoption is a prerequisite for RWA adoption, and Privy × Stripe's global fiat onramp is accelerating this prerequisite's maturation. More broadly, Stripe and Privy's founders believe the distinction between fiat and crypto will ultimately become 'meaningless' — not because crypto replaces fiat, but because users in daily operations won't need to perceive this distinction at all. Your salary arrives as stablecoin, your savings are held as tokenized Treasuries, your spending is completed with a Stripe-supported card — the entire system is experientially indistinguishable from a traditional bank account, but the underlying layer is tokenized financial infrastructure. Privy × Stripe's fiat onramp update is a quantifiably concrete step toward this vision.