# Card state change

Notification that a card has changed state. The following events trigger a notification:
- Activate a physical card.
- Remove a managed card.
- Report a physical card as lost.
- Report a physical card as stolen.
- Mark a virtual card as compromised.
- Card has expired.
- Block a managed card.
- Unblock a managed card.
- Update card renewal type.

Please note that since a card can have multiple blocks, an unblock event (for which a notification is sent) may not always result in the card state being updated to Active.

Endpoint: POST /managed_cards/state_change/watch
Version: v2

## Header parameters:

  - `call-ref` (string)
    A call reference generated by the caller and unique to the caller to provide correlation between the caller and system with a maximum length of 255

  - `published-timestamp` (integer, required)
    The timestamp, expressed in Epoch timestamp using millisecond precision, when this event was published.

  - `signature-v2` (string, required)
    The signature to verify the authenticity of this request.  This is the base64 hash (HmacSHA256) of the call-ref + payload + published-timestamp using your API key.

  - `signature` (string, required)
    The signature to verify the authenticity of this request.  This is the base64 hash (HmacSHA256) of the published-timestamp using your API key.

## Request fields (application/json):

  - `id` (object, required)

  - `id.type` (string, required)
    Enum: "managed_cards", "managed_accounts"

  - `timestamp` (string, required)
    The timestamp of the state change, using epoch timestamp with millisecond precision.

  - `eventType` (string, required)
    Enum: "ACTIVATED", "BLOCKED", "UNBLOCKED", "DESTROYED"

  - `state` (object)

  - `state.state` (string)
    The state of the instrument indicating what it can and cannot do as follows:
  - ACTIVE: The instrument is in an active state and can be used in transactions.
  - BLOCKED: The instrument is temporarily blocked and cannot be used. Any funds on the instrument are also frozen. The blockedReason provides more information as to why it was blocked.
  - DESTROYED: The instrument has been permanently destroyed. The destroyReason provides more information as to why it was destroyed.
  - NOT_ENABLED: The instrument is not enabled for use, since the linked user has not completed all necessary verification steps.
    Enum: "ACTIVE", "BLOCKED", "DESTROYED", "NOT_ENABLED"

  - `state.blockedReason` (string)
    The reason why the instrument has been blocked:
  - USER: The root, or an authorised user, of the identity owning the instrument has temporarily blocked the instrument.
  - SYSTEM: The platform or an administrator of the platform has temporarily blocked the instrument.
  - LOST: The instrument has been blocked because it was marked as lost.
    Enum: "USER", "SYSTEM", "LOST"

  - `state.destroyedReason` (string)
    The reason why the instrument has been destroyed:
  - SYSTEM: The platform or an administrator of the platform has destroyed the instrument.
  - USER: The root, or an authorised user, of the identity owning the instrument has destroyed the instrument.
  - LOST: The instrument was automatically destroyed as it was marked as lost.
  - STOLEN: The instrument was automatically destroyed as it was marked as stolen.
  - EXPIRED: The instrument was automatically destroyed as it expired.
  - COMPROMISED: The instrument was automatically destroyed as it was marked as compromised.
    Enum: "SYSTEM", "USER", "LOST", "STOLEN", "EXPIRED", "COMPROMISED"

  - `cardType` (string, required)
    Enum: "VIRTUAL", "PHYSICAL"

  - `renewalType` (string, required)
    Indicates how the card will be handled once it is close to expiring.
  - RENEW: The card will be automatically renewed, keeping the same card number but with a new expiry date and CVV.
  - NO_RENEW: Once the expiry date is reached, the card is destroyed.
    Enum: "RENEW", "NO_RENEW"


## Response 204 fields