# Replace a card

Issues a replacement for the card specified in the request URL. Specify the appropriate  in your request to trigger the right replacement process:    a card expiring soon:    a damaged card (physical card only): ,  (Deprecated)   Report a card as  and request a replacement (physical cards only): , , , ,    Please note the following:  For the  or  flows:   The new card will have the same card number, but it will have a new CVV and expiry date. Once you make this request, the card's status will change to , then  or  depending on the card's status prior to ordering. The value of the  property on the card resource will change to . The customer can still use the old card until they activate the new one. Once they do so, the old one will no longer be authorized and the value of  will change to .  For the  flow:   The new card will have a different card number. The old card will stop working immediately upon acceptance of the API request. This action cannot be undone.  Accepted card statuses:  : ,   and : , , ,   Please note that on  a given card can only be replaced once.

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

## Path parameters:

  - `card_account_id` (string, required)

## Request fields (application/json):

  - `line_1` (string)
    The name to print on the new card. For Replace flow only.
    Example: "JOHN/DOE"

  - `line_2` (string)
    Additional optional embossing line. For Replace flow only.
    Example: "TEST GMBH"

  - `reason` (string)
    The reason why the customer is requesting a replacement card.
    Enum: "CARDHOLDER_REQUEST", "COUNTERFEIT_PLASTIC", "DEFECTIVE_CARD", "EXPIRES_SOON", "LOST", "ONLINE_TRANSACTION_FRAUD", "PREVENTIVE_BLOCK", "STOLEN", "SUSPECTED_MERCHANT_FRAUD"

  - `reference` (string)
    Randomly generated UUID that acts as an idempotency key.
    Example: "7dc5377e-b90b-3401-b9a5-5dd094893e28"

  - `retain_pin` (boolean)
    Indicates whether or not the new card should use the same PIN as the old one. For Replace and Reissue flows, default is true. For Lost/Stolen, default is false.
    Example: true

  - `reported_at` (string)
    For Lost/Stolen flow only. Timestamp from when the card was reported (ISO 8601 format).
    Example: "2020-01-13T09:56:24.000Z"

## Response 200 fields (application/json):

  - `id` (string)
    ID of the card.
    Example: "2b890724292e287935420a2ca13ae7f9mcrd"

  - `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."