Webhooks
The platform sends webhook notifications via POST requests to your configured endpoint. Webhooks are signed with a Signature Token for security verification.
You can get your Signature Token on the Settings → Tokens page.
Setup
Configure your webhook URL through the dashboard (Settings → Tokens → Webhook URL) or via the Set Webhook URL endpoint.
Signature Verification
Every webhook contains a Signature header generated using HMAC-SHA512 with your Secret Key. Always verify this signature to ensure the webhook is authentic.
How to verify on your side
- Receive the webhook
POSTrequest - Read the
Signatureheader value - Hash the request body using your Secret Key with the
generateWebhookSignaturefunction shown on the right - Compare your computed hash with the
Signatureheader value
We recommend verifying every webhook. For each request, hash the payload using your Secret Key and compare it with the Signature header. This prevents attackers from sending fake webhooks.
Webhook Types
Three categories of webhooks are sent, each with its own payload structure:
- Invoice Webhooks — status updates for invoice payments
- Withdrawal Webhooks — withdrawal processing updates
- Static Address Deposit Webhooks — deposits to static addresses