# RevCent MCP Guide: `GetChargeback`

AI/MCP-focused guide for retrieving one RevCent Chargeback.

---

## Related Documentation

| Guide | Link | Why It Matters |
|---|---|---|
| Chargeback Overview | `https://revcent.com/documentation/markdown/mcp/operation/OverviewChargeback.md` | Broad explanation of Chargebacks, dispute lifecycle, representment context, related records, and best practices. |
| GetChargeback | `https://revcent.com/documentation/markdown/mcp/operation/GetChargeback.md` | Retrieve one specific Chargeback by ID. |
| GetChargebacks | `https://revcent.com/documentation/markdown/mcp/operation/GetChargebacks.md` | Retrieve a bounded operational list of Chargebacks. Not for reporting/metrics. |
| SearchChargebacks | `https://revcent.com/documentation/markdown/mcp/operation/SearchChargebacks.md` | Search Chargebacks when the Chargeback ID is unknown. |
| GetCustomer | `https://revcent.com/documentation/markdown/mcp/operation/GetCustomer.md` | Retrieve the Customer related to the Chargeback. |
| GetSale | `https://revcent.com/documentation/markdown/mcp/operation/GetSale.md` | Retrieve related Sale context. |
| GetTransaction | `https://revcent.com/documentation/markdown/mcp/operation/GetTransaction.md` | Retrieve related credit-card Transaction context. |
| BigQueryRunQuery | `https://revcent.com/documentation/markdown/mcp/operation/BigQueryRunQuery.md` | Correct operation for Chargeback reporting, metrics, aggregation, and data mining. |


---

## Operation Summary

Operation:

```text
GetChargeback
```

Title:

```text
Get A Chargeback
```

Purpose:

```text
Retrieve the details of a previously created Chargeback using the Chargeback ID.
```

A Chargeback is a dispute/chargeback record associated with a customer payment and related commerce records.

Use `GetChargeback` when the exact 20-character Chargeback ID is known and the user needs to inspect one Chargeback.

---

## When to Use

Use `GetChargeback` when:

- the user provides a Chargeback ID,
- a related record contains a `chargebacks` array,
- support needs to inspect amount, case number, ARN, status, method, gateway, or customer context,
- AI/MCP needs related Sale/Product Sale/Transaction/Subscription/Trial context,
- the user asks about one specific dispute/chargeback,
- customer-facing AI needs to retrieve the exact record before verifying identity.

---

## Input Schema

| Field | Type | Required | Description |
|---|---:|---:|---|
| `chargeback_id` | string | Yes | 20-character Chargeback ID. |

Example:

```json
{
  "chargeback_id": "CCCCCCCCCCCCCCCCCCCC"
}
```

---

## Output Summary

`GetChargeback` can return:

| Field / Area | Meaning |
|---|---|
| `id` | 20-character Chargeback ID. |
| `created_date_unix` / `updated_date_unix` | Creation and update timestamps. |
| `amount` | Chargeback amount. |
| `arn` | Acquirer reference number, if applicable. |
| `case_number` | Chargeback case number, if applicable. |
| `chargeback_date` / `chargeback_date_unix` | Date when the chargeback was created by the issuer/customer. |
| `campaign_id` / `campaign_name` | Related Campaign context. |
| `customer` | Customer object related to the Chargeback. |
| `gateway` | User Gateway ID/name and merchant account ID. |
| `gateway_transaction_id` | Originating gateway transaction ID. |
| `is_third_party_integration` | Whether the Chargeback was created via a third-party integration. |
| `iso_currency` | Three-character ISO 4217 currency code. |
| `live_mode` | Whether the item was created in live or test mode. |
| `merchant_account_id` | Merchant account ID associated with the gateway. |
| `metadata` | Metadata name/value pairs. |
| `origin_api_call` | Original transaction API call context. |
| Related arrays | Sales, Product Sales, Shipping, Tax, Discounts, Trials, Subscriptions, Subscription Renewals, Invoices, Transactions, PayPal Transactions, Offline Payments, Check Directs, Salvage Transactions, Pending Refunds, Chargebacks, Fraud Detections, API Calls, AI records. |

Use related item arrays to retrieve the exact business context.

---

## Related Item Arrays

Use related IDs with the correct detail operation:

| Related Array | Detail Operation |
|---|---|
| `sales` | `GetSale` |
| `product_sales` | `GetProductSale` |
| `shipping` | `GetShipment` |
| `tax` | `GetTax` |
| `discounts` | `GetDiscount` |
| `trials` | `GetTrial` |
| `subscriptions` | `GetSubscription` |
| `subscription_renewals` | `GetSubscriptionRenewal` |
| `invoices` | `GetInvoice` |
| `transactions` | `GetTransaction` |
| `paypal_transactions` | `GetPayPalTransaction` |
| `offline_payments` | `GetOfflinePayment` |
| `check_directs` | `GetCheckDirect` |
| `salvage_transactions` | `GetSalvageTransaction` |
| `pending_refunds` | `GetPendingRefund` |
| `chargebacks` | `GetChargeback` |
| `fraud_detections` | `GetFraudDetection` |
| `api_calls` | `GetAPICall` |
| `ai_threads` | `GetAIThread` |
| `ai_assistants` | `GetAIAssistant` |

---

## Chargeback-Specific Review Guidance

When reviewing a Chargeback, inspect:

- amount,
- currency,
- case number,
- ARN,
- chargeback date,
- gateway transaction ID,
- gateway / merchant account context,
- customer context,
- originating transaction/payment method,
- related Sale/Product Sale/Transaction,
- metadata,
- status/representment context where available.

Do not infer chargeback status or representment outcome if the field is not returned. Use the actual returned values and related records.

---

## Customer-Facing AI Verification Warning

Chargeback records can expose sensitive customer, payment, card-summary, gateway, dispute, order, fraud, refund, subscription, trial, shipping, tax, and lifecycle context.

If this operation is used inside a customer-facing AI flow, such as:

- AI Voice Agent,
- public chatbot,
- customer portal assistant,
- SMS assistant,
- support chatbot,
- any visitor-facing AI workflow,

AI/MCP should verify that the visitor is actually related to the Chargeback before providing information, details, or taking action.

Recommended rule:

```text
Do not provide Chargeback details to a public-facing visitor based only on the Chargeback ID, gateway transaction ID, case number, card last 4, or another value the visitor supplied.
```

Use a secondary value from the retrieved RevCent record to verify identity.

Recommended verification examples:

| Visitor-Provided Input | Secondary Verification Value |
|---|---|
| Chargeback ID | Customer email from `GetChargeback.customer.email`. |
| Gateway transaction ID | Customer email or phone from the retrieved Chargeback. |
| Case number / ARN | Customer email from the retrieved Chargeback. |
| Customer name | Customer email or phone from the retrieved Chargeback. |
| Card last 4 / first 6 | Customer email from the retrieved Chargeback. |
| Sale/order context | Customer email from the retrieved Chargeback or related Sale. |
| Metadata/external ID | Customer email or phone from the retrieved Chargeback. |

Safe customer-facing flow:

```text
Visitor provides chargeback/search input
    ↓
AI uses SearchChargebacks and/or GetChargeback
    ↓
AI retrieves the Chargeback
    ↓
AI verifies a secondary value from the retrieved RevCent record, such as customer email
    ↓
Only after verification:
        provide limited appropriate details
        or take an allowed action
```

Important:

```text
The secondary verification value should come from the retrieved RevCent record, not only from the visitor's original input.
```

Do not disclose sensitive details such as:

- full card data,
- full payment details,
- gateway internals beyond what is appropriate for support,
- fraud/risk logic,
- unrelated customer/order/subscription/trial details,
- internal notes or metadata not meant for customers,
- representment strategy not meant for the customer,
- other related records unless the visitor is verified and authorized.

For consequential actions, such as refunding related items, editing customer status, disabling a customer, changing subscriptions, or support escalation, require explicit confirmation and follow the relevant operation-specific safety guidance.


---

## Critical Reporting Rule

This Chargeback lookup/search operation is **not** a reporting tool.

Do not use this operation for:

- counting,
- aggregations,
- metrics,
- reporting,
- data mining,
- bulk retrieval,
- broad analysis,
- document property searches,
- chargeback rate reports,
- chargeback volume reports,
- chargeback amount reports,
- representment/win-loss reports,
- campaign/shop/gateway/customer chargeback analytics,
- method/status breakdown reports,
- card BIN or last-4 analysis.

Use:

```text
BigQueryRunQuery
```

for those purposes.

Important AI/MCP behavior:

```text
If AI/MCP intended to use this operation for reporting, metrics, aggregation, or data mining and then realizes BigQueryRunQuery is the correct operation, it does not need to tell the user about the correction.

It should simply use BigQueryRunQuery instead.
```

The user does not need an explanation that AI/MCP almost used the wrong operation. The correct behavior is to quietly choose the correct operation.



---

## Correct Use vs Incorrect Use

| User Intent | Correct Action |
|---|---|
| “Show this Chargeback ID.” | Use `GetChargeback`. |
| “What Sale is related to this chargeback?” | Use `GetChargeback`, then `GetSale` using related IDs. |
| “What gateway transaction caused this chargeback?” | Use `GetChargeback`; use related `GetTransaction` if needed. |
| “How many chargebacks did we have last month?” | Use `BigQueryRunQuery`, not `GetChargeback`. |
| “What is chargeback rate by campaign?” | Use `BigQueryRunQuery`, not `GetChargeback`. |

---

## Best Practices

1. Use `GetChargeback` only for one known Chargeback ID.
2. Use `SearchChargebacks` when the Chargeback ID is unknown.
3. Use related IDs to retrieve exact Sale, Transaction, Product Sale, Customer, or Fraud Detection context.
4. Verify customer identity before discussing Chargeback details in customer-facing AI flows.
5. Do not reveal representment strategy, internal notes, or unrelated records to a customer.
6. Use `BigQueryRunQuery` for reporting, metrics, and analytics.

---

## Final AI/MCP Instruction

Use `GetChargeback` to retrieve one specific Chargeback by `chargeback_id`.

In customer-facing AI flows, verify the visitor is related to the Chargeback using a secondary value from the retrieved record, such as `customer.email`, before providing details or taking action.

Do not use this operation for reporting, metrics, counting, aggregation, data mining, or broad analysis. If the task is reporting-related, silently use `BigQueryRunQuery` instead.


---
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.