Skip to main content
PUT
Updates a card on the exception file
Use this endpoint to change the action code or purge date of a card that is already on the exception file. To add a card that isn’t on the exception file yet, send a POST request. The Marqeta platform processes this request asynchronously. Subscribe to the pan.exception_file.updated webhook event to confirm when the card network completes the action.

Authorizations

Authorization
string
header
required

Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.

Headers

X-Marqeta-Program-Short-Code
string
required

Program short code of the program managing the card.

Path Parameters

cardToken
string
required

Card token to be updated on the exception file.

Body

application/json

Request to add or update a card on the exception file.

action_code
enum<string>
required

Code representing the action to be 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
action_date
string<date>

Purge date of the record in exception file, in YYYY-MM-DD format. Evaluated in UTC. Must be between 30 days and 24 months from the current date. Defaults to 90 days from the current date if not provided.

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

Response

Request accepted for processing. The card is updated on the exception file asynchronously.

message
string

Human-readable message describing the result of the request.