`deposit.credited`

On-chain deposit confirmed and credited to the member’s available balance

When Emitted

Emitted after Cobo confirms receipt and the credit journal is successfully posted, not merely when an on-chain notification arrives. The balance is already retrievable when you receive the event. ⚠ Only covers on-chain deposits. Deposits reported through POST /v1/deposits do not emit this event: that endpoint is synchronous, and funds are already credited when it returns 201; another event would only echo the response. ⚠ status_version is always 0; deposits have no state machine, only a credited state. ⚠ data.id is our numeric deposit transaction ID and uses a different identifier from dep_<你的 reference> in the GET /v1/deposits list.

This event is not initiated by an API call

Only covers on-chain deposits, triggered by Cobo’s callback. Deposits you report through POST /v1/deposits do not trigger this event; that path does not invoke notifications.

Payload

{
  "event_id": "evt_9d2b6f4013ae4c78b5910c3e7d84a2f1",
  "event_type": "deposit.credited",
  "created_at": "2026-08-12T12:44:03Z",
  "merchant_id": "acme",
  "livemode": true,
  "data": {
    "object": "deposit",
    "id": "184203",
    "external_member_id": "u_88123",
    "status": "credited",
    "status_version": 0
  }
}

Payload Fields

Field	Type	Description
`id`	string	Use this for deduplication. `evt_…` remains unchanged when the same event is redelivered.
`type`	string	Always `deposit.credited`
`created_at`	string	Time the event was created (RFC3339), not its delivery time. It is unchanged on redelivery.
`data.object`	string	Object type; determines which endpoint to query with `data.id`
`data.id`	string	Object ID; use it to retrieve details.
`data.status`	string	Treat unrecognized values as unknown and raise an alert; do not fall back to “processing”
`data.status_version`	number	Monotonically increasing; use it to discard older states that arrive late.

Signature Verification and Deduplication

Verify the signature against the raw request body bytes. Do not parse and reserialize the JSON: your JSON library may change key order or whitespace, which changes the signature and can look like a key configuration error.

// Node · Run before parsing JSON
const raw = await readRawBody(req);            // Buffer / string; do not use parsed req.body
const expect = crypto.createHmac("sha256", WEBHOOK_SECRET).update(raw).digest("hex");
const got = req.headers["z-signature"];        // Format: t=<unix>,v1=<hex>
if (!timingSafeEqual(expect, parseV1(got))) return res.status(400).end();

// Deduplicate using the envelope id, not data.id
if (await seen(JSON.parse(raw).id)) return res.status(200).end();

For the full procedure, including timestamp tolerance and redelivery semantics, see Webhook Guide.