---
tags: [recover]
---

| Background                                                                                                                                                                                                                                                                                                                                                                                                               |
| :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Before starting this tutorial, make sure you understand the following topics from the [Quick start](doc:quick-start) section:<ul style={{ marginTop: "-5px", marginBottom: "-5px" }}><li>[Sandbox environments](doc:sandbox-environments) (especially about testing).</li><li>[Authentication](doc:authentication) (about authenticating using your API user and when you need a login versus a one-time-use token).</li></ul> |

Merchants can enable or disable retries for one or more transactions by using Nexio's [Decline recovery](doc:decline-recovery-overview) feature when a transaction is declined. Transactions that are scheduled for a retry can be canceled through the [Enable or disable retries for a single transaction](ref:enableordisableretriesforasingletransaction) endpoint, [Enable or disable retries for multiple transactions](ref:enableordisableretriesformultipletransactions) endpoint, or through the Nexio Dashboard in the [Decline Recovery report](https://dashboard.nexiopaysandbox.com/reports/recoveries).

Using these tools to cancel transaction retries can be helpful for <Glossary>merchant</Glossary>s who want to cancel further retries before reaching a maximum retry limit.

Canceling transaction retries can also be helpful when a customer cancels a subscription while their payment is scheduled for a retry. The merchant can then disable retries for that subscription transaction to avoid paying future refunds.

# Cancel a retry for a single transaction

To cancel a retry for a single transaction, send a `PUT` request to the [Enable or disable retries for a single transaction](ref:enableordisableretriesforasingletransaction) endpoint. Include the following parameters in your request:

* `id` - The retry ID. Get this value from the DECLINE\_RECOVERY webhook event type (as `retryId`). Or, get the value by sending a `GET` request to the [View recoveries](ref:viewrecoverystatus) endpoint (as `id`).
* `isEnabledForRecovery` - Set the value of this parameter to `false` to cancel retries for the transaction.

```shell Example Request
curl --request PUT \
--url https://api.nexiopaysandbox.com/recovery/v3/enable \
--header 'Authorization: Basic [Base64_encoded_login]' \
--header 'Content-Type: application/json' \
--data '{
          "id": 4753537,
          "isEnabledForRecovery": false
        }'

{
  "id": 4753537,
  "isEnabledForRecovery": false,
  "success": true
}

curl --request PUT \
--url https://api.nexiopaysandbox.com/recovery/v3/bulkEnable \
--header 'Authorization: Basic anNtaXRoQG5leC5pbzpTYWdpbmF3MTEh' \
--header 'Content-Type: application/json' \
--data '{
           "retries": [
             {
               "id": 4753555,
               "isEnabledForRecovery": false
             },
             {
               "id": 4753556,
               "isEnabledForRecovery": false
             }
         ]
       }'

{
  "retries": [
    {
      "id": 4753555,
      "isEnabledForRecovery": false,
      "success": true
    },
    {
      "id": 4753556,
      "isEnabledForRecovery": false,
      "success": true
    }
  ]
}