Skip to main content

​
Which wallet receives a crypto deposit?

By default, Privy creates a new deposit wallet for the depositing user in each source chain family. Its address is the deposit address, and the create response returns its ID as wallet_id. Privy reuses this wallet for later requests on the same route while it stays eligible. It appears in the user’s linked accounts as an embedded wallet. If the user had no embedded wallet in that chain family, it becomes their primary one. A wallet automation converts deposits and delivers them to the destination wallet. The default dedicated strategy never uses the destination wallet or repurposes the user’s other wallets. With prefer_destination or require_destination, the destination wallet, such as the user’s primary embedded wallet, can be the deposit wallet.

​
How can users recover funds from a deposit wallet?

If your app meets the Privy Home prerequisites, users can see deposit wallets and their balances there. If your app also allows key export, users can export the private key and move funds with another wallet. Exporting a deposit wallet stops Privy from converting deposits sent to it. By default, later requests use a new deposit wallet, and useDepositFunds shows its address the next time it opens.