---
title: "Card order status change"
method: POST
path: "cards#card-order-status-change"
tags: ["webhook-event", "card-order"]
---

# Card order status change

`POST cards#card-order-status-change` (webhook)

This event is triggered every time a card order status is updated. Statuses depend on the type of card (virtual/physical). Additional statuses related to delivery exist for physical cards.

* Event type: `cards#card-order-status-change`
* Profile level subscriptions: Not Supported
* Application level subscriptions: Supported

**Available card order statuses**:

The initial card order status is `PLACED` or `REQUIREMENTS_FULFILLED` depending on the requirement fulfillment state. The possible values are:
- `PLACED`: The card order is created. The card will be generated once it has fulfilled all the requirements.
- `REQUIREMENTS_FULFILLED`: The card order has fulfilled all the requirements and the card should be generated in a short while.
- `CARD_DETAILS_CREATED`: The card has been generated.
- `PRODUCED`: The physical card has been produced and is waiting to be picked up by delivery vendor (physical card only).
- `COMPLETED`: The card has been activated and is ready to use. The card order is completed.
- `CANCELLED`: The card order has been cancelled. This can happen if you contact Wise Support to cancel a card order.
- `RETURNED`: Delivery failed. The physical card has been returned and will be blocked (physical card only).

{% img
  src="/images/diagrams/card-order-status-flow.png"
  alt="Create card order statuses transition diagram"
/%}

Events may not be delivered in the order they occurred. Use `data.occurred_at` to reconcile the order.
See the [Event ordering guide](/guides/developer/webhooks/event-ordering) for details.

See the [Webhooks guide](/guides/developer/webhooks) for setup instructions, signature verification, and best practices.

## Headers

- `X-Signature-SHA256` string
- `X-Delivery-Id` string, uuid
- `X-Test-Notification` boolean

## Payload

- union
  - V40010
    - `schema_version` '4.0.0' — Version of the event schema. Determined by the `schema_version` on your [webhook subscription](/api-reference/webhook).
    - `subscription_id` string, uuid — ID of the webhook subscription that triggered this event.
    - `event_type` string — Event type identifier
    - `sent_at` string, date-time — Timestamp when the event was sent.
    - `data` object
      - `resource` object
        - `profile_id` integer — ID of the profile that owns the card.
        - `type` string — Webhook notification of type 'card'.
        - `client_id` string — API `client_id`
        - `card_token` string, nullable — Unique identifier of the card.
        - `card_program` string — The card program associated with this card order. A card program is how Wise refers to all the cards you will be issuing with us, grouped by product type and issuing country.
      - `order_id` string — Card order ID associated with the status change.
      - `order_status` 'PLACED' | 'REQUIREMENTS_FULFILLED' | 'CARD_DETAILS_CREATED' | 'PRODUCED' | 'COMPLETED' | 'CANCELLED' | 'RETURNED' — Updated card order status
      - `delivery_vendor` string, nullable — Delivery vendor used to dispatch the order (physical card only).
      - `occurred_at` string, date-time — When the card order status change occurred.
  - V20010
    - `schema_version` '2.0.0' — Version of the event schema. Determined by the `schema_version` on your [webhook subscription](/api-reference/webhook).
    - `subscription_id` string, uuid — ID of the webhook subscription that triggered this event.
    - `event_type` string — Event type identifier
    - `sent_at` string, date-time — Timestamp when the event was sent.
    - `data` object
      - `resource` object
        - `profile_id` integer — ID of the profile that owns the card.
        - `type` string — Webhook notification of type 'card'.
        - `client_id` string — API `client_id`
        - `card_token` string, nullable — Unique identifier of the card.
        - `card_program` string — The card program associated with this card order. A card program is how Wise refers to all the cards you will be issuing with us, grouped by product type and issuing country.
      - `order_id` string — Card order ID associated with the status change.
      - `order_status` 'PLACED' | 'REQUIREMENTS_FULFILLED' | 'CARD_DETAILS_CREATED' | 'PRODUCED' | 'COMPLETED' | 'CANCELLED' | 'RETURNED' — Updated card order status
      - `delivery_vendor` string, nullable — Delivery vendor used to dispatch the order (physical card only).
      - `occurred_at` string, date-time — When the card order status change occurred.

## Acknowledgement `200`

Return any `2xx` status to acknowledge receipt of the event.

- object
  - `status` string

---

[API](https://skmtc.net/wise/apis/platform-api.md) · [All operations](https://skmtc.net/wise/apis/platform-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/wise/platform-api/revisions/4907a1d269ab/schema)