Block card
Blocks a card. A block is the hard stop - a compromised card, a dispute, an account on hold - while freeze is the soft toggle a cardholder flips. A blocked card declines everything: online, in-store, and ATM. Blocking a frozen card keeps the freeze, so the card returns to FROZEN when the block lifts. Idempotent, and a block placed by Reap is never replaced: if the card already carries a block with blockLiftable: false, that reason stays and the card remains one only Reap support can unblock.
Authorizations
API key as Bearer token
Headers
API version (YYYY-MM-DD)
2025-02-14 "2025-02-14"
Path Parameters
Response
Card resource
Unique card identifier
ID of the account the card belongs to
ID of the user the card belongs to
Card type (VIRTUAL or PHYSICAL)
VIRTUAL, PHYSICAL "VIRTUAL"
Current card status
ACTIVE, FROZEN, BLOCKED, EXPIRED "ACTIVE"
Block reason details (only present when status is BLOCKED)
Whether the current block can be lifted with the unblock endpoint. false for blocks that need Reap support, and for a card that holds no block.
Whether the card is frozen. A block hides a freeze from status, so a card that is BLOCKED with frozen: true returns to FROZEN once the block lifts.
Cardholder name displayed on card
Last 4 digits of the card number. Use reveal endpoint for full details.
3DS challenge verification method
SMS, WEBHOOK "SMS"
Physical lifecycle of the card (production + shipping + activation rollup). Defaults to NOT_ORDERED for newly created physical cards. null for virtual cards, which have no physical lifecycle.
NOT_ORDERED, REQUESTED, IN_PRODUCTION, PRODUCTION_COMPLETED, IN_TRANSIT, OUT_FOR_DELIVERY, DELIVERED, ACTIVATED, CANCELED, DELIVERY_FAILED, EXCEPTION "NOT_ORDERED"
ISO 8601 timestamp of creation
ISO 8601 timestamp of last update