Embedded Wallets

Privy embedded wallets are the simplest way to have users transact onchain. Privy’s key management system uses key splitting (Shamir’s secret sharing) to ensure your users have full custody of their wallets without needing to manage their secret keys. Neither Privy nor your application ever sees the user's keys; secrets are only ever reconstituted on the user's device when signing messages or transactions.

Users can manage their embedded wallet seamlessly with their account; they never need to handle any unnecessary technical complexity. Your application can even pregenerate wallets for an account, like an email address or phone number, before the user logs in. Users can also export the key for their embedded wallet, providing an escape hatch to leave Privy at any time.

Your application can easily guide users to use their wallet; Privy comes with simple abstractions to prompt users to fund, transact, and sign with their wallet. The wallet UIs are highly-customizable, allowing your application to communicate relevant context to the user or even abstract away the fact that a wallet is being used under the hood.

As Privy is always cross chain, your application can provision wallets on Solana and all EVM compatible chains.

Using wallets across apps

Privy embedded wallets are portable and can be used by any app––even apps not using Privy. Privy’s cross application wallet system supports interoperability with simple user experiences accessible to everyone, and seamlessly integrates with other Privy integrations and wallet connector solutions like RainbowKit and wagmi.

Sample cross app wallet flow

Smart wallets

Privy can also provision smart wallets for your users, supercharging your application experience with gas sponsorship, permissions, and more. Configuring smart wallets with Privy is simple on the smart wallet dashboard; just enter your wallet provider and API key and Privy handles the rest.

Funding

Users can easily onramp funds into their wallets with Privy’s native funding flows. Users can purchase crypto with fiat using Privy’s native onramp integrations, or transfer funds from another wallet, even if the wallet is on another network.

Sample funding flow

Delegated actions

Privy enables your application to request permissions from users to transact on their behalf. Once a user grants your application permission, your application can transact with their wallet from the server, even when the user themselves is offline. Privy’s architecture guarantees that your server will never see the wallet's secret key. Instead, the key is secured by Shamir’s secret sharing and all signing takes place in a trusted execution environment that only your application can request.

Sample delegated actions flow

Key import and key export

Users can export the key for their embedded wallet, providing an escape hatch to leave Privy at any time. Just as Privy enables you to import keys to create embedded wallets, users can export their wallet at any time with a simple call to the SDK. This means your user can always back up their wallet via third-party systems if they want to and your application is never locked into Privy as a vendor.