Privy emits webhooks for custodial wallet events, enabling your app to stay synchronized with wallet state and transaction lifecycle. Custodial wallets support both balance and transaction webhooks.
Webhooks can be tested at no cost in development environments. To enable webhooks in production,
upgrade to the Enterprise plan in the Privy Dashboard.
You can subscribe to transaction status updates via webhooks. For complete details on transaction webhook events, payloads, and setup, see the transaction event webhooks documentation.
You can subscribe to balance change events when funds are deposited or withdrawn via webhooks. For complete details on balance webhook events, payloads, and setup, see the balance event webhooks documentation.
If the deposit is an outcome of orchestration via a known provider (e.g. onramp, a refund from a
failed offramp attempt, or indirect deposit from another crypto wallet), the
wallet.funds_depositedwebhook
payload would include an
additional bridge_metadata field with orchestration details:
Type of the orchestration. fiat_deposit for onramp from fiat, crypto_deposit for deposit
from crypto, and refund for a refund from a failed offramp attempt.