---
title: "Delete"
method: POST
path: "/issuers/{issuerId}/consumers/{consumerId}/operations:delete"
tags: ["Operations"]
---

# Delete

`POST /issuers/{issuerId}/consumers/{consumerId}/operations:delete`

This request is used by the issuer backend to delete an end user (consumer).<br/>The action cascades to delete all the accounts, cards and digital cards associated with the end user.<br/><b>Note:</b> The deletion of the end user cannot be reversed. If the same end user is willing to reuse the solution, we will require a new end user registration with a new consumerId.

## Request body

- ReasonBody
  - `reason` string — The reason why the action is performed. This a free text field in case the Issuer wants to send details, that will be returned in the operations list.
  - `reasonCode` 'USER_DECISION' | 'ISSUER_DECISION' — The reason why the action has been performed. If not provided, default reason code is ISSUER_DECISION.

## Response `200`

End user was deleted successfully.

- OperationStatusSuccessful — Operation result information.
  - `operationId` string — Unique identifier of the operation
  - `status` 'SUCCESSFUL' — Status of the operation

## Other responses

- `400` — Bad Request, Invalid request URI or header, or unsupported nonstandard parameter
- `401` — The provided Authorization header is missing or invalid
- `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)