> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fyatu.com/llms.txt
> Use this file to discover all available pages before exploring further.

# CARD_TERMINATED

> Fired when a card is permanently terminated — either manually via the API or automatically after a single-use card settles its first transaction.

Fires after a card is permanently terminated. Termination is irreversible — the card cannot be reactivated.

There are two termination paths:

* **Manual** — triggered by a `POST /cards/{id}/terminate` API call or via the portal. The `reason` field is absent.
* **Automatic (single-use)** — triggered by the system after a single-use card's first transaction clears. The `reason` field is `SINGLE_USE_EXHAUSTED`.

## Event Type

```
CARD_TERMINATED
```

## Payload

### Manual termination

```json theme={null}
{
  "event":       "CARD_TERMINATED",
  "eventId":     "evt_01HXY123456ABCDEF",
  "businessId":  "BUS1A2B3C4D5E6F",
  "environment": "LIVE",
  "timestamp":   "2026-05-22T10:00:00Z",
  "data": {
    "cardId":       "crd_01HXYZ5555ABCDEF1111",
    "cardholderId": "chl_01HXYZ1234ABCDEF5678",
    "cardType":     "VIRTUAL",
    "status":       "TERMINATED"
  }
}
```

### Single-use auto-termination

```json theme={null}
{
  "event":       "CARD_TERMINATED",
  "eventId":     "evt_01HXY123456ABCDEF",
  "businessId":  "BUS1A2B3C4D5E6F",
  "environment": "LIVE",
  "timestamp":   "2026-05-22T10:00:02Z",
  "data": {
    "cardId":       "crd_01HXYZ5555ABCDEF1111",
    "cardholderId": "chl_01HXYZ1234ABCDEF5678",
    "cardType":     "VIRTUAL",
    "status":       "TERMINATED",
    "reason":       "SINGLE_USE_EXHAUSTED"
  }
}
```

## Payload Fields

| Field          | Type   | Description                                                                                   |
| -------------- | ------ | --------------------------------------------------------------------------------------------- |
| `cardId`       | string | The terminated card ID                                                                        |
| `cardholderId` | string | The cardholder the card belonged to                                                           |
| `cardType`     | string | `VIRTUAL` or `PHYSICAL`                                                                       |
| `status`       | string | Always `TERMINATED`                                                                           |
| `reason`       | string | `SINGLE_USE_EXHAUSTED` for automatic single-use terminations. Absent for manual terminations. |

## Common Use Cases

* Remove the card from the cardholder's active card list in your UI
* Log the termination for audit trail purposes
* On `reason: SINGLE_USE_EXHAUSTED` — mark the single-use card as consumed in your system

For the full event group documentation see [Card Events](/v3.20/webhooks/events/card-events).

<RequestExample>
  ```json Manual termination theme={null}
  {
    "event":       "CARD_TERMINATED",
    "eventId":     "evt_01HXY123456ABCDEF",
    "businessId":  "BUS1A2B3C4D5E6F",
    "environment": "LIVE",
    "timestamp":   "2026-05-22T10:00:00Z",
    "data": {
      "cardId":       "crd_01HXYZ5555ABCDEF1111",
      "cardholderId": "chl_01HXYZ1234ABCDEF5678",
      "cardType":     "VIRTUAL",
      "status":       "TERMINATED"
    }
  }
  ```

  ```json Single-use auto-termination theme={null}
  {
    "event":       "CARD_TERMINATED",
    "eventId":     "evt_01HXY123456ABCDEF",
    "businessId":  "BUS1A2B3C4D5E6F",
    "environment": "LIVE",
    "timestamp":   "2026-05-22T10:00:02Z",
    "data": {
      "cardId":       "crd_01HXYZ5555ABCDEF1111",
      "cardholderId": "chl_01HXYZ1234ABCDEF5678",
      "cardType":     "VIRTUAL",
      "status":       "TERMINATED",
      "reason":       "SINGLE_USE_EXHAUSTED"
    }
  }
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  {}
  ```
</ResponseExample>


## OpenAPI

````yaml v3.20/openapi.json webhook CARD_TERMINATED
openapi: 3.1.0
info:
  title: FYATU CaaS API v3.20
  description: >-
    FYATU Cards-as-a-Service API — API key authentication, Cardholder
    lifecycle, Card issuance, Transactions, Webhooks, and Programs.
  version: 3.20.0
  contact:
    name: FYATU Support
    url: https://fyatu.com
    email: support@fyatu.com
servers:
  - url: https://api.fyatu.com/api/v3.20
    description: >-
      FYATU CaaS API — the environment (LIVE or SANDBOX) is determined by the
      API key, not the URL
security:
  - BearerAuth: []
tags:
  - name: Meta
    description: Liveness, account info, and supported event types
  - name: Account
    description: Account-level balance and funding status
  - name: Programs
    description: Read card program configuration
  - name: Cardholders
    description: Create and manage cardholder profiles
  - name: Cards
    description: Issue, fund, freeze, and terminate virtual cards
  - name: Transactions
    description: Read-only card transaction history
  - name: Webhooks
    description: Manage webhook endpoints for real-time event delivery
  - name: Products
    description: Read card product configurations
paths: {}
components:
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      description: >-
        API key from the FYATU CaaS portal. Pass as `Authorization: Bearer
        <key>`.

````