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

# Lock Card

> POST /api/v1/cards/{card_id}/lock - Lock a card

Lock a card through the reviewed public gateway. This is the current public equivalent of older `freeze card` terminology.

## Endpoint

```text theme={null}
POST /api/v1/cards/{card_id}/lock
```

## Path Parameters

<ParamField path="card_id" type="string" required>
  The card identifier returned during card creation or listing.
</ParamField>

## Request Body

This operation accepts an optional JSON body. If you send metadata, keep it stable and auditable. Common examples include:

* `reason`
* `request_id`
* `idempotency_key`

## Example Request

```bash theme={null}
curl -X POST https://api.usezentra.com/api/v1/cards/card_123/lock \
  -H "Authorization: Bearer YOUR_SECRET_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "reason": "suspected_fraud",
    "request_id": "lock_card_123_001"
  }'
```

## Response Notes

* The reviewed public OpenAPI models this as an accepted async-style operation.
* For longer-lived policy changes, use the security settings endpoint as well.

## Next Steps

<CardGroup cols={2}>
  <Card title="Unlock Card" icon="unlock" href="/api-reference/cards/unlock">
    Restore card usage when review is complete
  </Card>

  <Card title="Security Settings" icon="shield" href="/api-reference/cards/security">
    Review broader card controls
  </Card>
</CardGroup>