Overview
0xmeta uses webhooks to notify you of settlement status changes in real-time. This eliminates the need for polling and provides instant updates when settlements complete.How Webhooks Work
When you initiate a settlement, 0xmeta’s background workers monitor the transaction status and trigger webhooks when the status changes.Webhook Configuration
Webhooks are configured via the Provider integration. When settlement status changes, Provider sends webhooks to the configured endpoint, and 0xmeta processes them.Setting Up Your Webhook Endpoint
Create an endpoint to receive webhook notifications:Webhook Events
TransactionExecutionSuccess
Sent when settlement completes successfully:TransactionExecutionFailure
Sent when settlement fails:Processing Webhooks
Best Practices
1
Respond Immediately
Return 200 OK within 5 seconds to acknowledge receipt
2
Handle Idempotency
Store event IDs to prevent duplicate processing
3
Verify Signatures
Always verify webhook signatures to ensure authenticity
4
Handle Errors Gracefully
Log errors but don’t fail the webhook
Webhook Flow Diagram
Webhook Retry Logic
If your endpoint fails, 0xmeta retries with exponential backoff:| Attempt | Delay |
|---|---|
| 1 | Immediate |
| 2 | 1 minute |
| 3 | 5 minutes |
| 4 | 15 minutes |
| 5 | 30 minutes |
| 6 | 1 hour |
Webhook Security
Use HTTPS
Use HTTPS
Webhook URLs must use HTTPS in production
Verify Signatures
Verify Signatures
Always verify the webhook signature
Validate Payload
Validate Payload
Check that required fields exist
Rate Limiting
Rate Limiting
Implement rate limiting on your webhook endpoint
Testing Webhooks Locally
Use ngrok to expose your local server:Common Webhook Patterns
Update Order Status
Handle Failed Settlements
Monitoring Webhooks
Track webhook delivery success:Webhooks provide real-time updates without polling. Your endpoint will be
notified within seconds of settlement status changes.