Overview
Webhooks let your system receive real-time notifications about events happening in CryptoMate — new deposits, card authorizations, withdrawals, and more. Notifications are delivered to an HTTP endpoint you configure in your environment.Webhook payload structure
Every webhook request shares a common envelope and an event-specificdata object.
| Field | Type | Description |
|---|---|---|
operation | string | High-level operation type (e.g. TREASURY, CARDS, VIRTUAL_WALLETS) |
sub_operation | string | Specific activity within the operation |
operation_id | string | Unique identifier for this notification |
status | string | SUCCESS | CANCELLED | FAILED |
reason | string | Failure reason (present when status is FAILED) |
data | object | Event-specific payload; shape varies by event type |
Example
Available events
General
General
- New deposit received
Cards
Cards
- Card transaction approval
- Card transaction declined
- Card transaction clearing pending
- Card transaction clearing failed
- Card transaction cleared
- Card transaction refund
- Card transaction reversal
- Card 3DS challenge
Active Management
Active Management
- Withdraw completed
Setup
To start receiving notifications, configure a webhook endpoint capable of receiving and processing the payloads above.Expose an HTTPS endpoint
Host a publicly reachable HTTPS URL that accepts
POST requests with a JSON body.Register it in CryptoMate
Register the endpoint from the Portal so CryptoMate knows where to deliver events.
Acknowledge quickly
Return a
2xx response as soon as you’ve persisted the event. Do heavier processing asynchronously to avoid timeouts.