 is a powerful authentication and key management platform to securely onboard, activate, and manage your users at scale. 

With just nine minutes of setup, Privy gives you out-of-the-box support for:

A variety of login methods, including email, phone, wallets, and social

Customizable UIs to progressively onboard your users

Self-custodial embedded wallets and powerful connectors for external wallets

native funding and bridging, full customization, account abstraction, delegated actions

 wallets are self-custodial wallets provisioned for a wallet experience that is directly embedded in your application. Embedded wallets do not require a separate wallet client, like a browser extension or a mobile app, and can be accessed directly from your product. Privy embedded wallets are fully self-custodial, so neither Privy nor integrating applications ever access embedded wallet private keys.

 wallets are managed by a third-party client, such as MetaMask or Rainbow. All browser extension wallets, hardware wallets, and mobile app wallets fall into this category.

Onboarding users with Privy

From there, you can get API keys and start your integration in the dashboard. You can choose which login methods, chains, wallet types, and plugins to enable!

Create an account

Privy offers multiple SDKs to easily onboard users to web3, including

 for managing your application. We find that starting with the React Auth SDK is easiest!

pnpm install @privy-io/react-auth@latest


 by selecting your app and then clicking Login Methods in the side bar. Select the account types you'd like users to be able to login with. By default, Privy enables wallet and email logins for new apps; you can update this setting now or later. For more information on how to enable social logins, check out the 

 for select your desired app, navigate to the 

 tab, find the API keys section. Get your 

The app ID serves as an API key used to initialize the Privy React SDK. This value can be safely exposed in a client-side environment, and you can 

 component and wrap your app with it. Set the 

 field to the app ID you got from the Dashboard in step 3.

 component or page that will use the Privy React SDK. It is generally recommended to render it as close to the root of your application as possible.

you can now use the Privy SDK throughout your components and pages via the 

Install the Privy SDK

With Privy, your app can prompt users for permission to take certain actions on their behalf. In this setup, your users can delegate permissions for your app to take allowlisted actions on their behalf, such as signing certain messages or sending certain transactions. These are 

Just request access to this feature in the Dashboard under plugins! 

Delegated actions enable you to build certain automated workflows, for instance:

buying a collectible when it becomes available on an open marketplace

triggering recurring onchain transactions for subscriptions and 

At a high-level, setting up delegated actions for your app involves two steps:

 within the Privy Dashboard, when enabling delegated actions, generate a P-256 asymmetric keypair to ensure that the TEE only ever executes requests originating from your app's servers. This step is optional, but 

: within your client (web or native mobile app), prompt the user to delegate certain permissions over their wallet to your app.

To generate an authorization keypair, in the 

 setting. This will enable delegated actions for your app.

From here, you can generate a P-256 authorization keypair. Your server will use this private key to sign request payloads to Privy's delegated actions API.

Copy the private key from the console and save it securely in a secrets manager or similar. Privy never sees this private key and cannot help you recover it. 

This means rotating the private key for your app in the case of key loss will require all users to consent to wallet delegation again.

To use delegated actions, your user must first grant consent to your app to take actions on their behalf. 

To prompt users to grant consent, follow 

Once a user has consented to delegated actions for their wallet, your app can take certain actions with the user's wallet. Follow 

If you have any feedback on this feature, reach out to us! You can read more about the TEE architecture we used to build delegated actions 

Use Delegated Actions

You can now use Privy to create a simple and smooth onboarding experience for your app! Once you’re able to log users in, you can start requesting signatures and transactions from wallets. Don’t forget to upgrade your application to Production when you’re ready!

 are programmable, onchain accounts that incorporate the features of 

. With just a few lines of code, you can create smart wallets for your users to sponsor gas payments, send batched transactions, and more.

 their wallets with a variety of assets, including a network's native currency (e.g. ETH), USDC, and other ERC20 tokens. 

If the external wallet does not have sufficient funds on the configured chain, but has funds on other networks, Privy will prompt the user to instead 

Cross-app wallets enable teams to bring one of crypto's most powerful features—interoperability—to mainstream audiences. 

 can easily integrate your cross-app wallet into an existing Rainbowkit or wagmi-based connector library with just a few lines of code.

If there are any features you need access to, just request access in the Dashboard or email us at 