Crypto deposits

Crypto deposits give a Privy wallet reusable deposit addresses. Users send supported tokens on supported chains to these addresses. Privy then swaps or bridges the funds into one target asset and delivers them to the wallet. With crypto deposits, an app can accept many assets across chains while holding a single stablecoin balance, such as PathUSD on Tempo. Privy orchestrates deposit detection, conversion, and delivery.

​

How crypto deposits work

Every crypto deposit involves three pieces:

1. Your app creates a crypto deposit account for a destination wallet. The request names the assets to accept and the asset to deliver.
2. Privy returns one deposit address for each source chain family, EVM or Solana.
3. A user sends a supported asset to a deposit address.
4. Privy converts the funds and delivers the target asset to the destination wallet.

​

Where deposit addresses live

By default, Privy creates a separate source wallet for the depositing user in each chain family. The source wallet’s address is the deposit address. Privy reuses this wallet for later requests on the same route. Alternatively, the destination wallet can be its own source wallet. The deposit address is then the destination wallet’s own address, and Privy converts funds in place. This only works when the destination is in the same chain family as the deposit. The deposit_address_strategy option controls this choice: Other chain families always use separate source wallets. For example, with an Ethereum destination wallet, Solana deposits still go to a separate Solana source wallet. Learn about deposit address behavior, including what happens when your app changes strategies.

​

SDK support

React requires @privy-io/react-auth, React Native requires @privy-io/expo, and NodeJS requires @privy-io/node. The deposit_address_strategy option requires @privy-io/node 0.35.0 or later. Experimental interfaces may change without a major SDK version bump. Apps on other platforms can integrate with the REST API directly. Each guide includes REST examples. To show a prebuilt deposit UI in React or React Native, use the deposit modal.

​

Supported assets

Crypto deposits support major assets through Privy’s canonical asset aliases, including USDC, USDT, ETH, and SOL. They also support many long-tail assets identified by an EVM token contract address or Solana token mint address. When funds arrive at a deposit address, Privy fetches a quote and forwards the funds to the destination when a liquidity pathway is available. Recognizing an asset or matching it with an all or exclude filter does not guarantee that it can be converted to every destination. To check whether a specific source asset, destination asset, and chain pair is currently supported, request a deposit quote. A successful quote confirms that a route is available at that time and returns its estimated output. Route availability and liquidity can change before a later deposit.

​

Canonical asset aliases

Privy supports the following well-known assets natively on the chains where they are available.

​

Supported chains

Crypto deposit addresses use wallet automations to detect incoming deposits on the following mainnet chains: This table describes deposit detection. Conversion also requires an available liquidity pathway and app-pays gas sponsorship on the source chain. Use the deposit quote API to check a specific source asset, destination asset, and chain pair.

​

Pricing and quotes

Request a deposit quote for current pricing on a specific asset pair, chain pair, and deposit amount. The quote’s estimated output previews the amount delivered after conversion. Deposit quotes are indicative. Creating a reusable address does not lock a price for future deposits. Pricing and liquidity can change before a deposit is converted, so fetch a fresh quote when showing a deposit estimate.

​

Gas and fee sponsorship

Gas sponsorship and swap provider fee sponsorship cover different costs. Configure them separately on the app’s Fee sponsorship page in the Privy Dashboard. Without swap provider fee sponsorship, provider fees are paid from the transferred or swapped amount. Provider fee sponsorship is configured per app and applies to all supported routes, rather than individual users or executions. Sponsorship does not expand supported assets, chains, or routes. Sponsored costs use the account’s shared prepaid credit balance or postpaid billing. Postpaid billing is available on the Enterprise plan. Crypto deposits require app-pays gas sponsorship on every source chain. Source wallets usually hold no native gas token, so Privy pays the gas to move deposits out of them. User-pays mode does not satisfy this requirement. Swap provider fee sponsorship is optional. Without it, conversion or bridging fees can still be deducted from the delivered amount. Follow the crypto deposit setup guide to enable the required settings.

​

Getting started