Card Status Changes

Emitted when a card is frozen, unfrozen, reported lost or closed.

Event Types

Event	When Emitted
`card.status.updated`	Card status changed: freeze / unfreeze / activate / close / manufacturing and shipping progress

Delivery Contract

We send a POST request with application/json to your configured endpoint, with a 10-second timeout.
Any 2xx response acknowledges receipt. Non-2xx responses and timeouts trigger retries with backoff.
Four request headers: content-type · z-signature · z-event-id · z-event-type。
Deduplicate by z-event-id — the same event may be delivered more than once.

Event payloads contain only IDs and status

There are no amounts, asset codes, card number fragments or risk-control reasons. This is a security boundary: the webhook endpoint is your service, whose transport and storage we cannot guarantee. The GET /v1/<resource>/{id} endpoint applies API key, scope and on-behalf-of checks. Fetch details using data.id; do not use webhook payloads as the source of amounts for your ledger.

Event Details

card.status.updated Card status changed: freeze / unfreeze / activate / close / manufacturing and shipping progress

When Emitted

Emitted when the upstream card status differs from our record and we synchronize it. One event covers all status changes. The event body does not specify the resulting state; use data.id, the card ID, to retrieve status from GET /v1/cards/crd_<id>. ⚠ Before 2026-08-13 this event contained the internal member ID, forcing callers to list all of the member’s cards and compare them individually, which could not identify the changed card for a multiple-card member. This is fixed. ⚠ Freeze and unfreeze each have a transitional state (freezing / unfreezing), not a terminal state. Top-ups fail during those transitions. Do not assume the card is available after receiving one event. ⚠ The same card can produce two consecutive events (freezing → frozen). Always merge forward by status_version; otherwise an out-of-order arrival can regress the card to a transitional state.

Payload

{
  "event_id": "evt_ca730f5b8e214d6790ab3c1e57f4d028",
  "event_type": "card.status.updated",
  "created_at": "2026-08-12T16:40:11Z",
  "merchant_id": "acme",
  "livemode": true,
  "data": {
    "object": "card",
    "id": "e70b3d41-5a28-4c96-91f0-6b2a8c05d7e3",
    "external_member_id": "u_88123",
    "status": "updated",
    "status_version": 3
  }
}

Signature Verification

The signature verification procedure is the same for all events. See Webhook Overview; use the Signature Debugger to compare signing strings character by character.