# Order a PIN Reprint
source: https://developer.mastercard.com/mastercard-processing-core/documentation/use-cases/pin-management/order-pin-reprint/index.md

## Overview {#overview}

This use case describes the process when a cardholder forgets a PIN for the current physical card and requests to send a PIN mailer by post.

## Sequence diagram {#sequence-diagram}

Diagram order-pin-reprint

### Explanation {#explanation}

1. The cardholder requests to receive a PIN by post.
2. The mobile application or e-banking service sends the request to the issuer server to order a PIN reprint.
3. The issuer server sends a `POST` request to the `/cards/{card_contract_id}/plastics` endpoint by passing the `REPRINT` value in the `reissueType` field in the request body.
4. The API sends a response to the server confirming that a PIN reprint has been requested.
5. The issuer server sends a response to the mobile application or e-banking service confirming that a PIN reprint has been requested.
6. The mobile application or e-banking service notifies the cardholder that the PIN reprint has been ordered.
7. The CMS generates an encrypted personalization file and uploads it to the SFTP. Note: Refer to [personalization process](https://developer.mastercard.com/mastercard-processing-core/documentation/guides/issuing-card/index.md#personalization-process) for more information.
8. The personalization bureau downloads the personalization file from the Mastercard Processing SFTP.
9. The personalization bureau generates PIN reprint based on the personalization file.
10. The PIN reprint is delivered to the cardholder.

Refer to [Sandbox testing](https://developer.mastercard.com/mastercard-processing-core/documentation/sandbox-testing/pin-management/order-pin-reprint/index.md) for information on how to execute the use case in the Sandbox environment.

## Endpoint {#endpoint}


API Reference: `POST /cards/{card_contract_id}/plastics`