# Card reissuing

Similar to your embossing configuration, you need to personalize the card reissuing configuration and process for your brand as every brand has different reissue reasons and associated costs. After setting up your [card program](https://developers.pismo.io/pismo-docs/docs/program-types), meet with your Pismo representative to configure this.

You can call the following card API endpoints to view your reissuing configuration and reissue a card:

* [Get card reissue reasons](https://developers.pismo.io/pismo-docs/reference/get-v1-card-reissue-reasons)—Issuer-defined card reissue reasons and actions
* [Reissue card](https://developers.pismo.io/pismo-docs/reference/post-v1-card-reissue)—Reissue a card. Reissuing a physical card initiates the embossing process.

# Transferring PIN, tokens,  and PAN when a card is reissued

When creating or reissuing a Pismo card, a new PAN and PIN are generated randomly. For a new card's PIN to be the same as the old card's, you **must** manually change the new card's password to the old card's password.

**To transfer a card's password (PIN):**

1. Call [Get card password](https://developers.pismo.io/pismo-docs/reference/get-v2-card-password) to get the old card's password.
2. Call [Change card password ](https://developers.pismo.io/pismo-docs/reference/put-v2-card-password)to update the new card's password to the old card's password.

**To transfer a card's tokens:**

1. Call [Reissue card](https://developers.pismo.io/pismo-docs/reference/post-v1-card-reissue)  and set the `update_tokens` parameter to `true`.
2. Alternatively, reissue the card and then call [Transfer card tokens ](https://developers.pismo.io/pismo-docs/reference/transfertokens).

There currently is no way to transfer a card's PAN to a reissued card.

# Card reissue scenarios and statuses

**Scenario 1 - physical**:

1. Card created (`CREATED`) and activated (`NORMAL`)
2. Card reissued with `must_block` = `true`(`CANCELLED`). (The reissue reason object contains the `must_block` field).
3. New card created (`CREATED`) and activated (`NORMAL`)

**Scenario 2 - physical**:

1. Card created (`CREATED`) and activated (`NORMAL`)
2. Card reissued with `must_block` = `false`(`REISSUED`)
3. New card created (`CREATED`) and activated (`NORMAL`)
4. Old card cancelled (`REISSUED`,`NORMAL`, `BLOCKED`, `PENDING`, or `WARNING`) > (`CANCELLED`)

**Scenario 3 - physical**:

1. Card created (`CREATED`), activated (`NORMAL`), and blocked (`BLOCKED`)
2. Card reissued with `must_block` = `false`, card remains with the same status (`BLOCKED`)
3. New card created (`CREATED`) and activated (`NORMAL`)
4. Old card canceled (`REISSUED`, `NORMAL`, `BLOCKED`, `PENDING`, or `WARNING`) > (`CANCELED`)

**Scenario 4 - virtual**:

1. Card created and activated automatically (`NORMAL`)
2. Card reissued with `must_block = true` or `must_block` = `false`(`CANCELLED`). (The `must_block` flag is a field in the reissue reason object.)
3. New card created (`CREATED`) and activated (`NORMAL`)

**Scenario 5 - physical**:

1. Card created (`CREATED`) and activated (`NORMAL`)
2. Card in some final status (for example, `THEFT`)
3. Card reissued
4. New card created (`CREATED`) and activated (`NORMAL`)
5. Old card stays with the same status (`THEFT`)

**Scenario 6 - physical:**

1. Card created (`CREATED`)
2. Card reissued with `must_block` = `true` or `must_block` = `false` (`CANCELED`). (The `must_block` flag is a field in the reissue reason object.) .
3. New card created (`CREATED`) and activated `(NORMAL`) .
4. Old card stays with the same status (`CANCELED`).

**Note:** For reissued cards that remain in the same status, the card update event is not sent, i.e., scenarios 3, 5 and 6.

> 📘 Reissuing card to a noname card
>
> You can use the [Associate noname card with customer ](https://developers.pismo.io/pismo-docs/reference/post-v2-card-bind)endpoint to reissue a card to a noname card as long as that noname card has not previously been associated and still has an `UNBOUND` status.

# Card reissue reasons

You can create your own reasons for reissuing a card. Each reason has a `reason_id`field identifier that you can pass when calling the [Reissue card](https://developers.pismo.io/pismo-docs/reference/post-v1-card-reissue)  endpoint. You can configure your initial reasons as part of the beginning setup process with your Pismo representative. To get your organization's reasons, call [Get card reissue reasons](https://developers.pismo.io/pismo-docs/reference/get-v1-card-reissue-reasons).

To create a reason for reissuing a card [open a JIRA ticket](https://developers.pismo.io/pismo-docs/docs/opening-a-service-desk-ticket)  with **type** = **Settings** and submit the following fields:

* **organization ID**—Your organization/tenant ID.
* **reason**—Reason description.
* **type**—Issuer defined reissue reason enum value. For example, `FRAUD`.
* **must\_block**—Is the card canceled at reissue time or can it transact until the new card is activated?
* **must\_charge**—Is reissue charged? This field is for information only—only issuers can make debit entries to a customer's account.
* **cost**—Reissue cost value. This field is for information only—only issuers can make debit entries to a customer's account.

# Mastercard automatic card reissue updates

This service is offered in partnership with **Mastercard** to simplify a customer's life.  When a new customer card number is issued, it is automatically updated on the various websites, applications, and digital services where the customer already has a record with the old card.