Skip to main content
Privy sends webhooks for three kinds of TMMF events:
  • WisdomTree receives an onboarding submission.
  • A wallet registration changes.
  • A fund order changes status.

​
Setup

Subscribe to TMMF events from the Configuration > Webhooks page in the Privy Dashboard.
Webhooks can be tested at no cost in development environments. To enable webhooks in production, upgrade to the Enterprise plan in the Privy Dashboard.
For general webhook setup instructions, payload verification, and retry behavior, see the webhooks overview.

​
Onboarding events

These events confirm that WisdomTree received a submission.
tmmf.kyb.updated
tmmf.kyc.updated has the same payload, with two changes:
  • It has user_id in place of organization_id.
  • Its data has kyc in place of kyb.
In both events, changes is always empty.
These events do not currently fire when the review status changes later, for example to approved. To follow the review, poll the KYB or KYC status.

​
Wallet events

This event tells your app that a wallet’s registration changed.
tmmf.wallet.updated

​
Order events

Privy sends one webhook when it creates an order. It sends a second one when the order reaches a final status. The payload is the order’s wallet action, with its steps.

​
Common patterns

These patterns show how to combine the events with the API.
Listen for tmmf.kyb.updated or tmmf.kyc.updated to know that WisdomTree received a submission. Then poll the review status until it is approved. Then register the user’s wallets. While the status is action_required, show the resubmission reasons to the business.
Listen for wallet_action.tmmf_deposit.succeeded and wallet_action.tmmf_withdraw.succeeded. Then list the wallet’s positions to show the new balance.
A failed order means WisdomTree failed or refunded it after the transfer. Use the get wallet action endpoint with ?include=steps to read the failure_reason and the wisdomtree_settlement step.