---
title: "Update Card Status"
method: POST
path: "/v1/issuing/cards/{id}/status"
tags: ["Card Lifecycle"]
---

# Update Card Status

`POST /v1/issuing/cards/{id}/status`

Change a card's status, applicable to `SINGLE` and `SHARE` mode cards. 

 The final status change of the card shall be subject to webhooks notification.

## Path parameters

- `id` string, uuid, required

## Headers

- `x-on-behalf-of` string
- `x-idempotency-key` string, uuid

## Request body

- CardUpdateStatusRequest
  - `card_status` 'ACTIVE' | 'FROZEN' | 'CANCELLED', required — Card status enum. See the Card lifecycle and statuses guide for more information. * `ACTIVE` - The request to create the card was successful and the card is ready to use. * `FROZEN` - All incoming authorization requests will be declined. the card can be reactivated to accept new authorizations. * `CANCELLED` - The card cannot be reactivated from this state, all incoming authorization requests will be permanently declined.
  - `update_reason` string — The reason for updating card status.

## Response `200`

Card update successfully.

- CardStatusResponse
  - `card_id` string, required — Unique identifier for the card.
  - `card_order_id` string, required — ID of the card order.
  - `order_status` 'PENDING' | 'PROCESSING' | 'SUCCESS' | 'FAILED', required — This field will contain the status of the request after processing. * `PENDING` -The initial status of the order request. * `PROCESSING` - If this status shall be subject to webhooks notification. * `SUCCESS` - The final status of the order request is successful. * `FAILED` - The final status of the order request is failed.
  - `update_reason` string — The reason for updating card status.

---

[API](https://skmtc.dev/uqpay/apis/authentication-api.md) · [All operations](https://skmtc.dev/uqpay/apis/authentication-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/uqpay/authentication-api/revisions/cef532a10777/schema)