---
title: "Disable A Salvage Transaction"
description: "Permanently disable an existing salvage transaction."
type: "mcp_operation"
company: "RevCent"
operation_id: "DisableSalvageTransaction"
canonical: "https://revcent.com/documentation/markdown/mcp/operation/DisableSalvageTransaction.md"
api_schema: "https://revcent.com/documentation/files/api/operation/DisableSalvageTransaction.json"
---

# RevCent MCP Guide: `DisableSalvageTransaction`

AI/MCP-focused guide for permanently disabling a RevCent Salvage Transaction.

---

## Related Documentation

| Guide | Link | Why It Matters |
|---|---|---|
| Salvage Transaction ecosystem overview | `https://revcent.com/documentation/markdown/ecosystem/item/SalvageTransaction.md` | Explains the business purpose, lifecycle, relationships, processing, disabling, and reporting context of Salvage Transactions. |
| Salvage Transaction MCP overview | `https://revcent.com/documentation/markdown/mcp/operation/OverviewSalvageTransaction.md` | Explains how Salvage Transactions are created and how retrieval, processing, disabling, automation, and reporting fit together. |
| GetSalvageTransaction | `https://revcent.com/documentation/markdown/mcp/operation/GetSalvageTransaction.md` | Retrieve and inspect the exact Salvage Transaction before taking a permanent action. |
| ProcessSalvageTransaction | `https://revcent.com/documentation/markdown/mcp/operation/ProcessSalvageTransaction.md` | Explains the recovery operation that becomes unavailable after disabling. |
| BigQueryRunQuery | `https://revcent.com/documentation/markdown/mcp/operation/BigQueryRunQuery.md` | Use for Salvage Transaction reporting, metrics, aggregation, and analysis. |

---

## Operation Summary

Operation:

```text
DisableSalvageTransaction
```

Purpose:

```text
Permanently disable an existing Salvage Transaction so it can no longer be processed.
```

This operation is irreversible. A disabled Salvage Transaction cannot be processed and cannot be re-enabled.

---

## When to Use

Use `DisableSalvageTransaction` only when the business has made a final decision that no future recovery attempt should be allowed for the specific Salvage Transaction.

Examples include:

- the business has intentionally written off the recoverable balance,
- the payment method has a hard decline or do-not-retry result and policy requires permanently ending recovery,
- fraud, dispute, legal, compliance, or customer-service review requires recovery to stop,
- the customer has revoked authorization for further recovery attempts,
- the item should be permanently excluded from manual, AI, or external processing workflows.

---

## When Not to Use

Do not disable a Salvage Transaction when:

- the business only wants to pause or delay recovery,
- the item still needs investigation,
- a later retry may still be appropriate,
- the target ID has not been verified,
- the user has not explicitly confirmed the permanent action,
- the request is only to inspect, report on, or analyze Salvage Transactions.

Use `GetSalvageTransaction` for inspection and `BigQueryRunQuery` for reporting. A delayed-retry policy should wait and re-check the item rather than permanently disabling it.

---

## Input Schema

| Field | Type | Required | Description |
|---|---:|---:|---|
| `salvage_transaction_id` | string | Yes | Exact 20-character Salvage Transaction ID to disable. |

The operation accepts no request-body properties. Do not invent or submit fields such as `disabled`, `enabled`, `reason`, or `status`.

Example MCP input:

```json
{
  "salvage_transaction_id": "XXXXXXXXXXXXXXXXXXXX"
}
```

---

## Required Confirmation Workflow

Recommended workflow:

```text
GetSalvageTransaction
    ↓
Verify the exact record, customer, source, amount, and recovery context
    ↓
Determine that recovery must end permanently
    ↓
Explain that disabling prevents all future processing and cannot be reversed
    ↓
Obtain explicit confirmation for this exact Salvage Transaction
    ↓
DisableSalvageTransaction
    ↓
Treat the successful operation result as authoritative
```

Immediately before execution, confirmation should be specific:

```text
Confirm that you want to permanently disable Salvage Transaction XXXXXXXXXXXXXXXXXXXX. It will no longer be processable and cannot be re-enabled.
```

General approval to “manage,” “review,” or “stop retries for now” is not sufficient authorization for permanent disabling.

---

## Preflight Checklist

Before calling `DisableSalvageTransaction`, verify:

- the exact 20-character Salvage Transaction ID,
- the record was retrieved from an authoritative RevCent result,
- the customer and related payment context are correct,
- the amount and source of the recoverable balance are understood,
- no approved recovery workflow still intends to process the item,
- the business reason for permanent disabling is known,
- the user understands that the operation cannot be reversed,
- explicit confirmation was obtained immediately before execution,
- the MCP client has permission `salvage_transaction:disable`.

---

## Output Schema

A successful response can include:

| Field | Description |
|---|---|
| `api_call_id` | ID of the RevCent API call. |
| `api_call_unix` | Unix timestamp when the API call was initiated. |
| `code` | API response code. `1` indicates success. |
| `salvage_transaction_id` | ID of the Salvage Transaction that was disabled. |
| `result` | Result message, such as `Salvage transaction disabled.` |

Do not report success unless the operation returns a successful response.

---

## Effect on Processing

After successful disabling:

- `ProcessSalvageTransaction` cannot process the disabled item,
- manual processing cannot recover it,
- AI/MCP recovery workflows must not attempt it,
- external recovery systems must not attempt it,
- the item cannot be re-enabled.

Automation should persist the successful disable outcome in its own workflow state so it does not continue scheduled retries for the same Salvage Transaction.

---

## AI and Automation Guardrails

AI/MCP clients must not infer permanent-disable intent merely from:

- a decline,
- a failed recovery attempt,
- a hard-decline classification,
- a customer complaint,
- an inactive retry workflow,
- an item being old,
- the absence of a planned retry date.

Those facts may justify recommending review, but the permanent operation still requires explicit authorization. Automated disabling is appropriate only when the business has deliberately configured a rule that clearly authorizes this irreversible action.

---

## Customer-Facing Verification Warning

If a customer-facing AI flow can request this action, verify that the visitor is authorized for the related customer and payment context. Do not permanently disable a recovery item based only on a visitor-provided Salvage Transaction ID, name, email, phone number, or order reference.

Use an authoritative RevCent record and a secondary record-backed value for identity verification, then obtain explicit confirmation of the permanent consequence.

---

## Reporting Guidance

`DisableSalvageTransaction` is a mutation operation, not a reporting operation.

Do not use retrieval loops or disable operations for counts, recovery-rate analysis, write-off reporting, or other analytics. Use `BigQueryRunQuery` for those purposes.

---

## Best Practices

1. Retrieve and inspect the exact Salvage Transaction first.
2. Distinguish a temporary pause from a permanent end to recovery.
3. Explain that disabling prevents processing and cannot be reversed.
4. Obtain explicit confirmation immediately before execution.
5. Never guess the Salvage Transaction ID.
6. Stop related scheduled or external retry workflows after success.
7. Use BigQuery for reporting and analysis.

---

## Final MCP Instruction

Use `DisableSalvageTransaction` only when the exact Salvage Transaction is verified and the user explicitly intends to permanently prevent all future processing.

The operation is irreversible: the disabled Salvage Transaction cannot be processed or re-enabled.


---
Document Parent Directory
* [Operations](https://revcent.com/documentation/markdown/mcp/operation/index.md) - AI/MCP details and overviews for operations available within the RevCent MCP.