Skip to main content
POST
Freeze Card

Overview

Freezes the user’s card, temporarily disabling it and preventing all transaction authorizations. This is a reversible action that allows users to quickly secure their card when they suspect suspicious activity or want to temporarily prevent spending.
Reversible ActionFrozen cards can be reactivated at any time using the POST /v1/card/unfreeze endpoint. No data is lost, and the same card details remain valid.

When to Use

Suspected Fraud

User suspects unauthorized activity on their card and wants to prevent further transactions

Lost Card

Card is temporarily misplaced but not confirmed lost or stolen

Budget Control

User wants to temporarily prevent spending without blocking the card permanently

Travel Preparation

Freeze card before travel and unfreeze when needed at destination

Authentication

This endpoint requires authentication via Bearer token:

Request

Headers

string
required
Your public API client key
boolean
default:false
Set to true to route requests to the US backend environment
string
required
Bearer token for authentication

Request Example

Response

Success Response

boolean
Indicates whether the card was successfully frozenValue: Always true on successful freeze

Error Responses

What Happens When a Card is Frozen?

1

Immediate Effect

The card status changes from ACTIVE to FROZEN instantly. All pending and future transaction authorizations will be declined.
2

Transaction Authorizations

Any transaction attempts will be declined with a “card frozen” or similar message. This includes:
  • Point-of-sale purchases (online and in-store)
  • ATM withdrawals
  • Recurring subscription payments
  • Pre-authorized transactions
3

Historical Data Preserved

All transaction history and card details remain intact. Users can still:
  • View transaction history via GET /v1/card/transactions
  • View card details via POST /v1/card/details/token
  • View card status via GET /v1/card/status
4

Reversible Action

The card can be unfrozen at any time using POST /v1/card/unfreeze, restoring full functionality immediately.

Use Case Examples

Fraud Prevention

Temporary Budget Lock

Lost Card Management

Idempotency

Already Frozen CardsCalling this endpoint on an already frozen card will return a 400 Bad Request error with the message “Card is already frozen”. Check card status first if you’re unsure of the current state.

Important Considerations

Cannot Freeze BLOCKED CardsCards with BLOCKED status cannot be frozen or unfrozen. Blocked cards are permanently disabled and require replacement via POST /v1/card/order.
Subscription PaymentsFreezing a card will cause recurring subscription payments to fail. Inform users that they should unfreeze their card before scheduled subscription renewals or update payment methods for critical services.
Real-Time EffectCard freezing takes effect immediately. There may be a brief delay (typically <1 second) for the status change to propagate to payment processors.

Best Practices

User Confirmation

Status Verification

UI State Management

Testing

Sandbox Testing

In sandbox/test environments, you can freeze and unfreeze cards repeatedly to test your integration:

Monitoring and Analytics

Consider tracking freeze events for insights:
  • POST /v1/card/unfreeze - Unfreeze a frozen card to restore functionality
  • GET /v1/card/status - Check current card status
  • GET /v1/card/transactions - View transaction history (works on frozen cards)
  • POST /v1/card/order - Order a replacement card (if card is blocked)