Skip to main content
POST
Freeze a card

Overview

Immediately freezes an active card. While frozen:
  • All purchase attempts are declined at the network level
  • The card balance is fully preserved
  • The card can be unfrozen at any time via POST /cards/{id}/unfreeze
This is the recommended first action when a cardholder reports a lost or suspicious card. Freeze first, investigate, then unfreeze if the situation resolves or terminate if confirmed compromised.

Path Parameters

Request Body

This endpoint has no request body.

Example

Success Response (200)

Returns the updated card with status: FROZEN and a non-null frozenAt:

Webhook

A CARD_FROZEN event fires after a successful freeze:
The change is applied at the card issuer before this endpoint returns, so the status you get back is one the network will actually honour. If the issuer refuses, the call returns CARD_STATE_CHANGE_REFUSED and the card keeps its previous status — a card shown as frozen is always a card the issuer is declining, and one shown as active is always one it will authorise.

Error Codes

Authorizations

Authorization
string
header
required

API key from the FYATU CaaS portal. Pass as Authorization: Bearer <key>.

Path Parameters

id
string
required

Response

Card frozen

success
boolean
Example:

true

status
integer
Example:

200

message
string
Example:

"Card retrieved"

data
object

Full card object returned by GET /cards/{id}. Includes live balance, full PAN, CVV, features, and billing address.

meta
object