Privy
Auth and embedded wallets for apps that want a user onchain without a seed phrase.
- Capture
- Partial: 3 of 6 screens
- Last captured
- Oct 20, 2026
- Flow draft
- 6 screens
Privy is wallet and authentication infrastructure. Public docs describe one user object that can hold email, phone, social, passkey, and external-wallet accounts. Embedded wallets are created inside the app. Privy says secrets are reconstituted in a trusted execution environment, and that users can export a key.
On June 11, 2025, Privy announced that Stripe was acquiring the company. The post said Privy would keep operating as an independent product. Stripe’s docs now describe Privy as the way to onboard users and embed wallets.
The modal a given app shows is a configuration, not a single product screenshot. SMS, a long social list, or an existing OIDC provider can all be turned on or off. Until we capture a declared default, step counts on this page are a reading of the docs.
Who it is for
Teams that want login and an embedded wallet as the product, including apps that already have an auth provider and only need wallets.
Sign-in, as documented
- Email one-time passcode
- SMS, and WhatsApp is mentioned in Privy’s concept docs
- Social and OAuth, including Google, Apple, X, Discord, GitHub, LinkedIn, Telegram, and Farcaster
- Passkeys
- External Ethereum and Solana wallets
- An existing OIDC provider, such as Auth0, Firebase, or Cognito
Wallet model
Embedded wallets for users, plus wallets your own backend controls. User wallets can be pregenerated for an email or phone before that person logs in. Policies can limit what a signer is allowed to do.
Expected flow
Dated frames are screenshots of the vendor’s default UI from the lab capture on Oct 20, 2026. Empty frames are still pending. The sequence itself is still a reading of the public docs.
01Entry in the host app
Privy lab entry. The host control opens the vendor’s default UI.
02Method picker
Privy default UI on the email method. No code has been sent.
03Credential
Privy one-time code screen. The code was not submitted.
No screenshot
04MFA, if the app requires it
Privy recommends a passkey or authenticator app when the primary login is delegated to email, SMS, or a social provider. Not every app turns this on.
Privy test accounts and their one-time codes live in the dashboard under User management → Authentication → Advanced. This run does not read a real inbox. Set PRIVY_TEST_EMAIL and PRIVY_TEST_OTP locally, without committing them, to capture the steps after the code.
No screenshot
05Embedded wallet
Docs say a wallet can be created automatically, on demand, or before first login. We have not timed which of those a default setup does.
No screenshot
06Ready state
The user should land back in the host app with an address. Key export is documented as a later action, not necessarily this screen.
Metrics
Documented rows cite a public page. Pending rows wait for the first capture. A blank is not a zero.
Screens in this draft
6 expected screens
A reading of Privy’s auth docs. The live default may skip MFA or collapse wallet creation into the login.
Sign-in surface
Email, phone, social, passkey, external wallets
Each method is optional per app.
Steps to a wallet
Pending first capture
Counted on a declared default, from the first click to an address on screen.
Fields the user fills
Pending first capture
Codes, checkboxes, and profile prompts. OAuth screens count.
Time to first wallet
Pending first capture
A stopwatch on the happy path. Not a lab claim until we record it.
Context switches
Pending first capture
Email apps, OAuth popups, and anything that leaves the host app.
Pricing snapshot
Developer plans are banded by monthly active users. A MAU is any Privy-authenticated user with a session in the last 30 days. As of Oct 19, 2026, from privy.io/pricing.
| Plan | Price | What the page says |
|---|---|---|
| Developer | Free · 0–499 MAU | Core features, 50,000 signatures, and $1M transaction volume a month, as published. |
| Core | $299 / month · 500–2,499 MAU | The next published band after the free tier. |
| Scale | $499 / month · 2,500–9,999 MAU | The top self-serve band on the pricing page we reviewed. |
| Pay as you go | $2,000 base, then usage | Above 10,000 MAU or 50,000 signatures: $0.05 per extra MAU and $0.01 per extra signature, as published. |
| Enterprise | Custom | Signature pricing described as low as $0.001, plus SLAs and SSO. |
- List prices move. This is a snapshot of the public page, not a quote.
- Hitting a band upgrades the plan. Privy says the new price is billed the following month.
Read this before you quote the page
- Privy.com, the email-popup product, is a different company.
- “75 million accounts” and similar figures are Privy’s own marketing, not a measurement from this site.
Change history
Wallet-first notes open, with empty frames
Five wallet vendors and Didit are on the shelf, with six comparisons. Every screenshot frame says capture pending. Measured rows — steps, fields, time — are blank on purpose. Nothing here was timed.
Stripe announces it is acquiring Privy
Sequoia’s note from the same day said Privy would join Stripe and keep serving the teams already on the product. Stripe’s docs now cover Privy as wallet infrastructure. This is context for the vendor page, not a claim about the login UI.