Z Zise Developers 简体中文

card.topup.credited

Card top-up funds have actually reached the card

When Emitted

Two flows emit this event with the same meaning: the money is on the card or in its shared limit pool. · A separate top-up after issuance: 201 from POST /v1/cards/{id}/topups only acknowledges the order. This event confirms receipt. data.id is the top-up order ID. · Initial top-up during issuance: virtual cards are funded when issuance settles; physical cards are funded after activation. Here data.id is first:<申请单 uuid>, without a ctp_ row. Retrieve the card itself through card.application.approved for the same issuance. Only enable spending limits and available credit after this event; enabling them earlier would make a limit available before its funds arrive.

Payload

{
  "event_id": "evt_71fd0c9e46a34b18b52d7f038ea6c145",
  "event_type": "card.topup.credited",
  "created_at": "2026-08-12T17:12:48Z",
  "merchant_id": "acme",
  "livemode": true,
  "data": {
    "object": "card_topup",
    "id": "3a90c7e4-1f68-4b02-95dc-7e41b0a2d963",
    "external_member_id": "u_88123",
    "status": "credited",
    "status_version": 2
  }
}

Payload Fields

FieldTypeDescription
idstringUse this for deduplication. evt_… remains unchanged when the same event is redelivered.
typestringAlways card.topup.credited
created_atstringTime the event was created (RFC3339), not its delivery time. It is unchanged on redelivery.
data.objectstringObject type; determines which endpoint to query with data.id
data.idstringObject ID; use it to retrieve details.
data.statusstringTreat unrecognized values as unknown and raise an alert; do not fall back to “processing”
data.status_versionnumberMonotonically 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.