Sign in
Cards servicing

(Deprecated) Report a card as lost or stolen

Note: This endpoint is 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.<br><br> Reports the card specified in the request URL as lost or stolen. The card will be immediately blacklisted. Please note the following: <ul> <li>Please note that virtual cards can only be reported lost or stolen without requesting a replacement.</li> <li> The status of the card must only be one of the following values: ACTIVE, INACTIVE, BLOCKED, or BLOCKED_BY_SOLARIS.</li> <li>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 POST Replace a card endpoint.</li> <li>You can order a replacement card in the same API call by setting the value of order_replacement to true.</li> <li>When a card has been reported as lost or stolen, it immediately stops working. This action cannot be undone.</li> <li>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 POST Create a card endpoint to order them a new one.</li> <li>For sandbox testing, you must set the value of lost_at to 2021-06-03T18:31:09+00:00.</li></ul>

post/v1/cards/{card_account_id}/lost_stolen_incidents

Path parameters

card_account_idstring required

Request body

loss_reason'COUNTERFEIT_PLASTIC' | 'HOME_INVASION' | 'LEFT_AT_MERCHANT' | 'LOST' | 'MAIL_ORDER' | 'MAILBOX_THEFT' | 'MISSING_AT_HOME' | 'PICK_POCKET' | 'PREVENTIVE_BLOCK' | 'SUSPECTED_MERCHANT_FRAUD' required

The customer's reason for reporting the card as lost or stolen.

lost_atstring date-time required

Timestamp from when the card was lost (ISO 8601 format).

order_replacementboolean

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 false and order the customer a new card in a separate API call, e.g., if they lost a tokenized card.

retain_pinboolean

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

Example request

{
  "loss_reason": "HOME_INVASION",
  "lost_at": "2020-01-13T09:56:24.000Z",
  "order_replacement": false,
  "retain_pin": false
}

Response

Successful result of the operation

idstring

ID of the lost/stolen card incident.

card_idstring

ID of the card that was lost or stolen.

loss_reason'COUNTERFEIT_PLASTIC' | 'HOME_INVASION' | 'LEFT_AT_MERCHANT' | 'LOST' | 'MAIL_ORDER' | 'MAILBOX_THEFT' | 'MISSING_AT_HOME' | 'PICK_POCKET' | 'PREVENTIVE_BLOCK' | 'SUSPECTED_MERCHANT_FRAUD'

The customer's reason for reporting the card as lost or stolen.

lost_atstring

UTC timestamp from when the customer reported the card as lost or stolen.

card_status'ACTIVE' | 'ACTIVATION_BLOCKED_BY_SOLARIS' | 'BLOCKED' | 'BLOCKED_BY_SOLARIS' | 'CLOSED' | 'CLOSED_BY_SOLARIS' | 'COUNTERFEIT_CARD' | 'FRAUD' | 'INACTIVE' | 'LOST' | 'NEVER_RECEIVED' | 'PROCESSING' | 'STOLEN'

The current status of the card.

Example response

[
  {
    "id": "a2f0129cb1194a688dace3b678a85268",
    "card_id": "8febdba4912a747808ccc6f95f82aaa4",
    "loss_reason": "MAILBOX_THEFT",
    "lost_at": "2023-05-23T12:56:45+00:00"
  }
]