Skip to main content
The exception file record object represents a card on the exception file. The Marqeta platform returns this object when you retrieve a card from the exception file. For guidance on choosing an action code and purge date, see Exception File Management.
​
card_token
string

Unique identifier of the card on the exception file.

Example:

"6a2b8c4e-1f3d-4a5b-9c7e-2d4f6a8b0c1e"

​
program_short_code
string

Program short code of the program managing the card.

Example:

"sqc9"

​
network
enum<string>

Card network associated with the card.

Available options:
VISA
Example:

"VISA"

​
action_code
enum<string>

Code representing the action that was taken on the card.

  • CLOS - Card terminated / closed account
  • LCPU - Lost card
  • SCPU - Stolen card
  • INVA - Invalid / not found account
  • PUWF - Fraud pickup (non-specific)
  • PUNF - Pickup (no fraud)
  • EXPC - Expired card (authorization only; declines with response code 54)
  • DNTH - General block (authorization only; declines with response code 05)
Available options:
CLOS,
LCPU,
SCPU,
INVA,
PUWF,
PUNF,
EXPC,
DNTH
Example:

"CLOS"

​
action_type
enum<string>

Type of action recorded for the card on the exception file.

Available options:
ADD,
UPDATE,
DELETE
Example:

"ADD"

​
action_date
string<date>

Purge date of the record in the exception file, in YYYY-MM-DD format (UTC).

Pattern: ^\d{4}-\d{2}-\d{2}$
Example:

"2027-01-15"

​
source
enum<string>

Origin of the exception file record.

Available options:
API,
AUTO_ADD
Example:

"API"

​
created_at
string<date-time>

Date and time when the record was created, in UTC.

Example:

"2026-10-17T14:32:08Z"

​
last_modified_at
string<date-time>

Date and time when the record was last modified, in UTC.

Example:

"2026-10-17T14:32:08Z"