Skip to main content
The transfer wallet action API sends tokens from a Privy wallet to a destination address. Instead of constructing blockchain transactions from scratch, the transfer action accepts a human-readable asset, amount, chain, and destination address — Privy handles the onchain complexity. The transfer API also natively handles bridging across chains and converting between stablecoins of the same peg. Wallets can execute transfers with a separate source asset/chain and a separate destination asset/chain. images/transfer-splash.png
If your app has gas sponsorship configured, usage of the /transfer endpoint will be gas-sponsored by default. There is no need to specify additional parameters for sponsorship.

​
Supported assets

The transfer API supports transferring all native tokens (ETH, SOL, POL, TRX) and all ERC20/SPL/TRC-20 tokens (including stablecoins). When making a transfer request to the Privy API, you can either specify a well-known asset (e.g. USDC, USDT, USDB, EURC) or you can configure a custom ERC20/SPL (e.g. a custom-issued stablecoin).

​
Well-known assets

Privy supports the following well-known assets natively on the chains where they are available.
For the most up-to-date list of Privy’s well-known assets and the specific chains where they are available, visit the Asset watchlist section of the Privy Dashboard.

​
Custom assets

Privy also supports transfers of custom ERC20/SPL tokens. To configure these assets, visit the Asset watchlist tab of the Wallets page of the Dashboard to configure your asset. Then, simply pass the asset’s address in the source.asset_address parameter of your request to Privy to transfer it.

​
Supported chains

The /transfer API supports the following chains:
To transfer on chains not listed above, use the low-level RPC API to construct and send transactions directly.
Tron transfers are same-chain only. Cross-chain bridging and stablecoin conversions are not supported for Tron. Tron destination addresses must be base58check-encoded (starting with T).

​
Native bridging

Privy’s /transfer API supports natively bridging an asset (e.g. ETH, USDC) across the supported chains listed above. Supported routes include: Native bridging is subject to fees, slippage, and current liquidity conditions.

​
Stablecoin conversions

Privy’s /transfer API also supports converting between stablecoins of the same peg. For instance, the transfer API supports setting different USD stablecoins (USDC, USDT, USDC.e, USDT0) as the source and destination currency. This enables you to hold balance in one stablecoin and payout in the preferred stablecoin or chain of your recipient. Stablecoin conversions is subject to fees, slippage, and current liquidity conditions.
Native bridging and stablecoin conversions is only supported for well-known assets where Privy’s bridging partners can provide sufficient liquidity. To extend these capabilities to a custom asset, please reach out.