# Restore Risk Control Original Values
source: https://developer.mastercard.com/mastercard-processing-fraud/documentation/use-cases/restore-risk-ctrl-orig-values/index.md

## Overview {#overview}

This use case describes how an issuer's fraud and risk management team decides to restore risk control default values configured during the onboarding using their internal fraud and risk management platform.

## Sequence diagram {#sequence-diagram}

Diagram restore-risk-ctrl-orig-values

### Explanation {#explanation}

1. The fraud and risk team decides to reset risk control's counters usage through their internal back-office system. The back-office system sends the request to the server to change the parameters of a specified risk control for a card generating suspicious activities.
2. The server sends a PUT request to the `/contracts/{contract_id}/risk-controls/{risk_control_code}/original-values` endpoint. Note: For the standard product, the server must put the `cardContractId` value in place of the `contract_id` in the path. Possible values for the `risk_control_code` parameter are defined during the onboarding process.
3. The API sends a response to the server confirming that the risk control has been redefined.
4. The server sends a response to the back-office system notifying that the risk control parameters have been modified.

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

## Endpoint {#endpoint}


API Reference: `PUT /contracts/{contract_id}/risk-controls/{risk_control_code}/original-values`