### Operation Status Updates
**Please note that webhooks are triggered exclusively for operations of the type closed references. Operations involving open references do not currently support automated status updates via webhook.**
- `paid`
  - **Event**: `webhook.paid.success`
  - **Purpose**: Notify when cash operation was paid.
  - **Payload**: `{"event": "webhook.paid.success", "operation_id": 123, "external_user_id": "USER123456", "type": "cash_in", "amount": 500, "reference": "10511175512161627448", "status": "paid", "processed_at": "2025-01-15T10:30:00Z"}`
- `expired`
  - **Event**: `webhook.expired.success`
  - **Purpose**: Notify when cash operation expired.
  - **Payload**: `{"event": "webhook.expired.success", "operation_id": 123, "external_user_id": "USER123456", "type": "cash_in", "amount": 500, "reference": "10511175512161627448", "status": "expired", "processed_at": "2025-01-15T10:30:00Z"}`
- `reversed`
  - **Event**: `webhook.reversed.success`
  - **Purpose**: Notify when cash operation was reversed.
  - **Payload**: `{"event": "webhook.reversed.success", "operation_id": 123, "external_user_id": "USER123456", "type": "cash_in", "amount": 500, "reference": "10511175512161627448", "status": "reversed", "processed_at": "2025-01-15T10:30:00Z"}`

All webhook requests include signature headers for verification:
- `X-Webhook-Timestamp`: Unix timestamp
- `X-Webhook-Signature`: HMAC-SHA256 signature

