---
title: "Suspend"
method: POST
path: "/issuers/{issuerId}/digitalCards/{digitalCardId}/operations:suspend"
tags: ["Operations"]
---

# Suspend

`POST /issuers/{issuerId}/digitalCards/{digitalCardId}/operations:suspend`

This request is used by the issuer backend to request the suspension of the digital card if the digital card is active.<br/>The result of this operation is synchronous from a TSP point of view (a successful response means that the digital card has been successfully suspended on the TSP itself) but does not guarantee that any update has occurred yet on the device, an optional notification will be sent on successful/unsuccessful completion of the operation on the wallet.

## Request body

- OperationRequest — The following object represent the account
  - `reason` string — The reason why the action is performed.
  - `reasonCode` 'USER_DECISION' | 'ISSUER_DECISION' | 'DEVICE_LOST' | 'DEVICE_STOLEN' | 'CARD_LOST' | 'CARD_STOLEN' | 'FRAUD_DETECTED' — The reason code why the action is performed.<br/>If not provided , default reason code is ISSUER_DECISION

## Response `200`

Successful card suspension request

- OperationStatus — Operation information.
  - `operationId` string — Unique identifier of the operation
  - `status` 'PENDING' | 'SUCCESSFUL' | 'FAILED', required — Status of the operation

## Other responses

- `400` — Bad Request, Invalid request URI or header, or unsupported non-standard parameter
- `401` — The provided Authorization header is missing or invalid
- `403` — Forbidden action, check the state of the linked end user (consumer) or account or digital card
- `404` — Resource not found
- `500` — Internal Server Error

---

[API](https://skmtc.net/thalescloud/apis/d1-oauth-api.md) · [All operations](https://skmtc.net/thalescloud/apis/d1-oauth-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/thalescloud/d1-oauth-api/revisions/96089514858c/schema)