Deposit state change

Sent when a fiat deposit into a subaccount changes state. status is one of pending, complete, or failed. Stablecoins sent to a subaccount’s blockchain deposit address are reported by custody.transfer instead.

WEBHOOK mintDeposits

Example

{
  "subscriptionId": "00000000-0000-4000-8000-000000000002",
  "notificationId": "11111111-1111-4111-8111-111111111112",
  "notificationType": "mint.deposits",
  "notification": {
    "id": "00000000-0000-4000-8000-000000000014",
    "source": {
      "type": "bank_account",
      "id": "src_001"
    },
    "destination": {
      "type": "wallet",
      "id": "1000000001"
    },
    "amount": {
      "amount": "200.00",
      "currency": "USD"
    },
    "fromAmount": {
      "amount": "200.00",
      "currency": "USD"
    },
    "fees": {
      "amount": "0.00",
      "currency": "USD"
    },
    "status": "complete",
    "trackingRef": "track-002",
    "createDate": "2026-08-25T19:28:00.000Z",
    "updateDate": "2026-08-25T19:28:30.000Z"
  },
  "timestamp": "2026-08-25T19:40:00.000000000Z",
  "version": 2
}

Body

application/json

The envelope every v2 webhook notification arrives in. The product-specific fields live in notification.

subscriptionId · string<uuid> · required

ID of the webhook subscription that produced this notification.

notificationId · string<uuid> · required

Unique ID for this event. Stable across retries of the same delivery, so use it to deduplicate.

notificationType · enum<string> · required

The type of notification.

Available options: mint.deposits

notification · any · required

The event payload. The schema of this object depends on notificationType.

timestamp · string<date-time> · required

When the notification was produced.

version · integer · required

The version of the notification schema. Always 2.

Response

200

Webhook received successfully