Skip to content
← Tools / Skills
ToolStripe/10 trustVerified

Privy

Embedded crypto wallets and auth — Web2 logins, non-custodial wallets underneath.

Acquired — still operating

Acquired by Stripe (June 2025); operates as an independent product.

Visit official site →

About

Privy lets developers embed non-custodial crypto wallets directly inside their apps. Users sign in with familiar methods — email, OAuth, passkeys — and get a wallet created in the background, no seed phrases, no MetaMask detour. Private keys are managed through Privy's infrastructure with export options, so users can always take self-custody later. The product also covers the auth layer itself, making it a two-for-one: onboarding plus wallet infra.

In June 2025 Stripe acquired Privy (following its $1.1B Bridge acquisition), and Privy continues to operate as an independent product inside Stripe's crypto stack — co-founder Henri Stern now runs stablecoins and crypto across Stripe. Recent moves show the direction: an October 2026 Ripple partnership brought programmable XRP Ledger wallets (XRP, RLUSD) to Privy apps, with explicit support for AI agents transacting via the x402 payment protocol. Customers at acquisition included OpenSea, Blackbird, and Toku.

For developers the value is removing the single biggest drop-off in crypto UX — wallet setup. The cost is custody trust: you're delegating key management to a third party (albeit one now backed by Stripe), and the wallet feature set follows Privy's roadmap, not yours.

What it can do

  • Embedded non-custodial wallets created from email, OAuth, or passkey logins
  • Programmable wallet creation and transaction signing via API/SDK
  • Private key and seed-phrase export for user self-custody
  • Multi-chain support including EVM chains, Solana, and XRP Ledger
  • Server wallets for AI agents and automated x402 payments
  • Auth primitives: login methods, MFA, session management

Setup

  1. Create an app in the Privy dashboard and get your app ID.
  2. Install the SDK (npm install @privy-io/react-auth).
  3. Wrap your app in PrivyProvider with your app ID and login methods.
  4. Use the useWallets / usePrivy hooks to create wallets and sign transactions.

Prerequisites

A Privy app ID; a React/Next.js (or React Native/Expo) frontend. Server-side operations need the Privy authorization private key.

Use cases

authweb3walletsdeveloper-toolsapi

Works with

Trust score — 7/10

/10 trustVerified

Scored 7/10 (verified tier, metrics-v1). Evidence: Closed SaaS, no public repo; adoption estimated from customer base at acquisition (OpenSea, Blackbird, Toku) and Stripe backing (thinner evidence); Acquired by Stripe June 2025 — verified via multiple 2025/2026 reports; operates independently; Henri Stern now runs crypto across Stripe; Oct 2026 Ripple/XRPL partnership and x402 agent-payment support verified via current press. Manual review: embedded-wallet UX claims verified against docs; key-management trust is delegated to a third party by design — flagged, not a defect. License: Closed SaaS (Stripe).

How the trust score is built

Full methodology →
Adoption · stars/downloads, log-scaled vs peers
7.0/10
Maintenance · recency, releases, issue load
8.0/10
Openness · license + docs
5.0/10
Manual review · sanity read + red-flag check
8.0/10
  • · Closed SaaS, no public repo; adoption estimated from customer base at acquisition (OpenSea, Blackbird, Toku) and Stripe backing (thinner evidence)
  • · Acquired by Stripe June 2025 — verified via multiple 2025/2026 reports; operates independently; Henri Stern now runs crypto across Stripe
  • · Oct 2026 Ripple/XRPL partnership and x402 agent-payment support verified via current press
  • · manual review: embedded-wallet UX claims verified against docs; key-management trust is delegated to a third party by design — flagged, not a defect

Sources

Every fact above was checked against these sources. Where a claim comes from the provider and couldn't be independently verified, the text says so.