---
title: "Delete Card"
method: DELETE
path: "/open-api/v3/cards/{id}"
tags: ["Card"]
---

# Delete Card

`DELETE /open-api/v3/cards/{id}`

Deleted cards cannot be restored.
- For prepaid cards, any remaining balance will be automatically transferred to the Infinity Account.
- If a refund is issued after the card has been deleted, the refunded amount will be transferred to the Infinity Account on a T+1 basis.
- For budget cards, any refund that occurs after deletion will continue to be credited back to the original budget.

## Path parameters

- `id` string, required — card id

## Request body

- CardRequest
  - `accountId` string, required — accountId
  - `clientTransactionId` string — User-provided custom transaction ID.

## Response `200`

OK

- CardResponse — card resources
  - `code` string — Return code
  - `message` string — Error message
  - `data` CardResource — Returned data
    - `id` string — Unique identifier of the card
    - `accountId` string — Account ID
    - `status` string — Card status. Values: INACTIVE,CONTROL,ACTIVE,PENDING,FROZEN
    - `currency` string — Currency code
    - `bin` string — Card BIN (Bank Identification Number)
    - `userName` string — User name
    - `createTime` string — Card creation time
    - `cardLastFour` string — Last four digits of the card number
    - `billingAddress` AddressResource — Card address
      - `addressLine1` string — First line of the address
      - `addressLine2` string — Second line of the address
      - `city` string — City
      - `country` string — Country
      - `postalCode` string — Postal code
      - `state` string — State
    - `label` string — Card label
    - `balanceId` string — Balance ID
    - `budgetId` string — Budget ID (Only for Budget Card)
    - `cardholderId` string — Cardholder ID
    - `referenceId` string — A unique identifier assigned by you for each card. This value must be unique per card request and will be used later to query or track the corresponding card.
    - `cardMode` 'PHYSICAL_CARD' | 'VIRTUAL_CARD' — Card mode. Example: VIRTUAL_CARD
    - `transactionLimits` TransactionLimitsResource[] — Limit information
      - `type` string — Type of card spending limit. The quota will reset at 00:00 (GMT+8). Values: DAY,WEEK,MONTH,QUARTER,YEAR,LIFETIME,TRANSACTION,NA
      - `value` string — Card spending limit amount
      - `currency` string — Currency code
    - `cardStatusChangeRecordList` CardStatusChangeRecordResource[] — card status change record list
      - `userId` string — user id
      - `accountId` string — account id
      - `cardId` string — card id
      - `operationTime` string — operation time, millisecond timestamp
      - `beforeStatus` string — before status
      - `afterStatus` string — after status
      - `reasonCode` string — reason code:7001:Created via merchant portal, 7002:Created via API, 1001:Closed via Open API, 1002:Closed via merchant portal, 1003:Closed due to risk policy violation, 1004:Closed by administrator, 1005:Closed due to BIN decommission, 1006:Closed due to account termination, 1007:Automatic deletion upon card expiration, 2001:Activated via Open API, 2002:Activated via merchant portal, 3001:Suspended via Open API, 3002:Suspended via merchant portal, 5001:Restricted by administrator, 6001:Unrestricted by administrator,
      - `reasonMessage` string — reason message
      - `requestUrl` string — request url

## Other responses

- `400` — Bad Request

---

[API](https://skmtc.net/interlace/apis/core-resource.md) · [All operations](https://skmtc.net/interlace/apis/core-resource/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/interlace/core-resource/versions/29c08a4da357/schema)