The following functionality exists for wallets reconstituted server-side. More on Privy architecture here

Privy emits webhooks whenever a server wallet sends or receives a registered asset. This helps your application stay in sync with the assets in your server wallets, and easily track deposits and withdrawals.

To set up deposit and/or withdrawal webhooks, follow the guide below.

Webhooks is currently a scale feature. To use webhooks, please upgrade your account in the Privy Dashboard.

Deposit webhooks are available for EVM chains only. Solana support is coming soon

​
Setup a webhooks URL

To start, go to the Webhooks page for your app in the Privy Dashboard and provide a destination URL for receiving webhooks.

Then, enable the 'wallet.funds_deposited' and/or 'wallet.funds_withdrawn' events. You can next configure which assets Privy should emit 'wallet.funds_deposited' and/or 'wallet.funds_withdrawn' events for.

Privy will emit a signed webhook to this URL whenever your server wallets sends/receives a transaction for a registered asset, and will retry delivery if the endpoint does not successfully respond to the original webhook. Privy’s webhook system operates on a at least once delivery basis, and redundant requests can be identified via the idempotency_key field.

​
Configure assets to track

Once you’ve enabled the 'wallet.funds_deposited' and/or 'wallet.funds_withdrawn' events, you can then configure which assets you’d like to track via the Privy Dashboard.

Privy supports webhooks for native tokens (e.g. ETH, SOL) on EVM and Solana, ERC20 tokens on EVM, and SPL tokens on Solana.

​
Native tokens

To configure webhooks for native token transactions, simply select the Native token asset type and provide the CAIP-2 chain ID for the network on which to track the native token.

​
ERC20 tokens

To configure webhooks for ERC20 token transfers, simply select the ERC20 token asset type and provide:

  • the contract address for the ERC20 token
  • the CAIP-2 chain ID for the network on which to track the ERC20 token

​
SPL tokens

To configure webhooks for SPL token transfers, simply select the SPL token asset type and provide:

  • the mint address for the SPL token
  • the CAIP-2 chain ID for the network on which to track the SPL token

​
Payload

When a server wallet receives a transaction for a registered asset, Privy will emit a webhooks payload with the following fields:

​
Example

Below is a sample webhooks payload that Privy might send on a deposit of .05 ETH on Base into a server wallet.

{
  "type": "wallet.deposit_received",
  "wallet_id": "cm4db8x9t000ccn87pctvcg9j",
  "asset": {
    "type": "native-token",
    "address": null
  },
  "amount": "500000000000000",
  "transaction_hash": "0x2446f1fd773fbb9f080e674b60c6a033c7ed7427b8b9413cf28a2a4a6da9b56c",
  "sender": "0x59D3eB21Dd06A211C89d1caBE252676e2F3F2218",
  "recipient": "0x59D3eB21Dd06A211C89d1caBE252676e2F3F2218",
  "caip2": "eip155:8453",
  "block": {
    "number": 22000002
  },
  "idempotency_key": "enriched_transaction_v2_0x9fb07e26c4e1913ce3c06602db2c1e216fd6134b40a03def699ea04ca67c7088_20"
}