# (Deprecated) Report a card as lost or stolen (deprecated)

 Please use the POST Replace a card endpoint instead. Read the endpoint summary to learn how to use the endpoint for the lost/stolen use case. Reports the card specified in the request URL as lost or stolen. The card will be immediately blacklisted. Please note the following:  Please note that  cards can only be reported lost or stolen without requesting a replacement.  The  of the card must only be one of the following values: , , , or . Only use this endpoint in the event that the card is lost or stolen or if the card details have been compromised. If a physical card is damaged, please use the  endpoint. You can order a replacement card in the same API call by setting the value of  to . When a card has been reported as lost or stolen, it immediately stops working. This action cannot be undone. If the customer has added their card to Google Pay or Apple Pay, reports it lost or stolen, and requests a replacement at the same time, then the lost/stolen card will continue to work. If the cardholder believes that their card and phone were both compromised, then you should not order them a replacement card in the same API call. Instead, use the  endpoint to order them a new one. For  you must set the value of  to .

Endpoint: POST /v1/cards/{card_account_id}/lost_stolen_incidents
Version: 1.0

## Path parameters:

  - `card_account_id` (string, required)

## Request fields (application/json):

  - `loss_reason` (string, required)
    The customer's reason for reporting the card as lost or stolen.
    Enum: "COUNTERFEIT_PLASTIC", "HOME_INVASION", "LEFT_AT_MERCHANT", "LOST", "MAIL_ORDER", "MAILBOX_THEFT", "MISSING_AT_HOME", "PICK_POCKET", "PREVENTIVE_BLOCK", "SUSPECTED_MERCHANT_FRAUD"

  - `lost_at` (string, required)
    Timestamp from when the card was lost (ISO 8601 format).
    Example: "2020-01-13T09:56:24.000Z"

  - `order_replacement` (boolean)
    Boolean to indicate whether or not to order the customer a replacement card in the same API request. Note that you can set this to  and order the customer a new card in a separate API call, e.g., if they lost a tokenized card.

  - `retain_pin` (boolean)
    (If ordering a replacement card right away) Boolean to indicate whether the new card should retain the same PIN.

## Response 200 fields (application/json):

  - `id` (string)
    ID of the lost/stolen card incident.
    Example: "a2f0129cb1194a688dace3b678a85268"

  - `card_id` (string)
    ID of the card that was lost or stolen.
    Example: "8febdba4912a747808ccc6f95f82aaa4"

  - `loss_reason` (string)
    The customer's reason for reporting the card as lost or stolen.
    Enum: "COUNTERFEIT_PLASTIC", "HOME_INVASION", "LEFT_AT_MERCHANT", "LOST", "MAIL_ORDER", "MAILBOX_THEFT", "MISSING_AT_HOME", "PICK_POCKET", "PREVENTIVE_BLOCK", "SUSPECTED_MERCHANT_FRAUD"

  - `lost_at` (string)
    UTC timestamp from when the customer reported the card as lost or stolen.
    Example: "2023-05-23T12:56:45+00:00"

  - `card_status` (string)
    The current status of the card.
    Enum: "ACTIVE", "ACTIVATION_BLOCKED_BY_SOLARIS", "BLOCKED", "BLOCKED_BY_SOLARIS", "CLOSED", "CLOSED_BY_SOLARIS", "COUNTERFEIT_CARD", "FRAUD", "INACTIVE", "LOST", "NEVER_RECEIVED", "PROCESSING", "STOLEN"

## Response 400 fields (application/json):

  - `id` (string)
    Example: "a95f2aaf-4e0c-4d49-8021-8a16a884ed86"

  - `status` (string)
    Example: "400"

  - `code` (string)
    Example: "build_pagination_headers_failure"

  - `title` (string)
    Example: "Failed to build pagination headers."

  - `detail` (string)
    Example: "Cannot connect to database."

## Response 403 fields (application/json):

  - `id` (string)
    Example: "a95f2aaf-4e0c-4d49-8021-8a16a884ed86"

  - `status` (string)
    Example: "403"

  - `code` (string)
    Example: "unauthorized_action"

  - `title` (string)
    Example: "Unauthorized Action"

  - `detail` (string)
    Example: "Unauthorized action is not allowed."

## Response 404 fields (application/json):

  - `id` (string)
    Example: "a95f2aaf-4e0c-4d49-8021-8a16a884ed86"

  - `status` (string)
    Example: "404"

  - `code` (string)
    Example: "model_not_found"

  - `title` (string)
    Example: "Model Not Found"

  - `detail` (string)
    Example: "Partner configuration for 1333d41bdc314436b9448c24ae42eccpar not found."

## Response 500 fields (application/json):

  - `id` (string)
    Example: "e8915041-9d8c-4d96-9dd1-04e8522ecdbf"

  - `status` (string)
    Example: "500"

  - `code` (string)
    Example: "generic_error"

  - `title` (string)
    Example: "Generic Error"

  - `detail` (string)
    Example: "There was an error."