---
title: "Chargebacks"
description: "A non-technical overview of Chargebacks in RevCent, focused on how chargeback records are created from credit card transactions, how they connect dispute activity to transaction history, customer context, representment tracking, evidence workflows, AI automation, and reporting."
type: "item"
company: "RevCent"
canonical: "https://revcent.com/documentation/markdown/ecosystem/item/Chargeback.md"
relationships:
  - name: "Transaction"
    url: "https://revcent.com/documentation/markdown/ecosystem/item/Transaction.md"
technical_links:
  web_app: "https://kb.revcent.com/en/payments/credit-card/chargeback"
  api:
    section: "https://revcent.com/docs/api/v2#section-chargebacks"
    operations:
      - name: "Get Chargebacks"
        operation_id: "GetChargebacks"
        operation: "https://revcent.com/docs/api/v2#operation-GetChargebacks"
        schema: "https://revcent.com/documentation/files/api/operation/GetChargebacks.json"
      - name: "Create A Chargeback"
        operation_id: "CreateChargeback"
        operation: "https://revcent.com/docs/api/v2#operation-CreateChargeback"
        schema: "https://revcent.com/documentation/files/api/operation/CreateChargeback.json"
      - name: "Get A Chargeback"
        operation_id: "GetChargeback"
        operation: "https://revcent.com/docs/api/v2#operation-GetChargeback"
        schema: "https://revcent.com/documentation/files/api/operation/GetChargeback.json"
      - name: "Edit A Chargeback"
        operation_id: "EditChargeback"
        operation: "https://revcent.com/docs/api/v2#operation-EditChargeback"
        schema: "https://revcent.com/documentation/files/api/operation/EditChargeback.json"
      - name: "Search Chargebacks"
        operation_id: "SearchChargebacks"
        operation: "https://revcent.com/docs/api/v2#operation-SearchChargebacks"
        schema: "https://revcent.com/documentation/files/api/operation/SearchChargebacks.json"
      - name: "Create A Chargeback Document"
        operation_id: "CreateChargebackDocument"
        operation: "https://revcent.com/docs/api/v2#operation-CreateChargebackDocument"
        schema: "https://revcent.com/documentation/files/api/operation/CreateChargebackDocument.json"
  mcp:
    overview: "https://revcent.com/documentation/markdown/mcp/operation/OverviewChargeback.md"
    operations:
      - name: "Get Chargebacks"
        operation_id: "GetChargebacks"
        markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetChargebacks.md"
        available_via_ai: true
      - name: "Create A Chargeback"
        operation_id: "CreateChargeback"
        markdown: "https://revcent.com/documentation/markdown/mcp/operation/CreateChargeback.md"
        available_via_ai: true
      - name: "Get A Chargeback"
        operation_id: "GetChargeback"
        markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetChargeback.md"
        available_via_ai: true
      - name: "Edit A Chargeback"
        operation_id: "EditChargeback"
        markdown: "https://revcent.com/documentation/markdown/mcp/operation/EditChargeback.md"
        available_via_ai: true
      - name: "Search Chargebacks"
        operation_id: "SearchChargebacks"
        markdown: "https://revcent.com/documentation/markdown/mcp/operation/SearchChargebacks.md"
        available_via_ai: true
      - name: "Create A Chargeback Document"
        operation_id: "CreateChargebackDocument"
        markdown: "https://revcent.com/documentation/markdown/mcp/operation/CreateChargebackDocument.md"
        available_via_ai: true
  bigquery_schema: "https://revcent.com/documentation/files/bigquery/dataset.json"
  bigquery_tables:
    - "chargeback"
---

# Chargebacks

A Chargeback is a RevCent item that represents a credit card dispute or reversal connected to a previous credit card Transaction.

Chargebacks are important because they connect dispute activity back to the original payment and the surrounding commerce context. A Chargeback can help a business understand which Transaction was disputed, which Customer was involved, which Sale or subscription activity was affected, which Gateway processed the original payment, and what information may be needed for review or representment.

Conceptually:

```text
Transaction = original credit card payment attempt or refund record
Chargeback = dispute record connected to that Transaction
```

A Chargeback should not be treated as a standalone complaint record. In RevCent, it is part of the payment, customer, sale, and risk history surrounding a credit card transaction.

## Technical Links

| Area | Link |
|---|---|
| Web App | https://kb.revcent.com/en/payments/credit-card/chargeback |
| API | https://revcent.com/docs/api/v2#section-chargebacks |
| MCP / AI | https://revcent.com/documentation/markdown/mcp/operation/OverviewChargeback.md |
| BigQuery Schema | https://revcent.com/documentation/files/bigquery/dataset.json |
| BigQuery Table | `chargeback` |

## What a Chargeback Represents

A Chargeback represents a dispute tied to a prior credit card Transaction. The disputed Transaction may be related to an initial sale, subscription renewal, trial expiration, salvage recovery attempt, or another credit card payment flow.

Chargebacks can be created in RevCent manually, automatically, or through API-based workflows. They are specific to credit card transactions and should be linked to the correct source Transaction whenever possible.

A Chargeback may contain or connect to information such as:

- Chargeback amount.
- Chargeback reason code.
- Acquirer reference number, often called ARN.
- Case number.
- Gateway transaction ID.
- Merchant account ID.
- Customer Card reference.
- Customer.
- Sale.
- Transaction.
- Gateway.
- Campaign.
- Subscription, Trial, Subscription Renewal, or Salvage Transaction context when applicable.
- Shipping and tax records when applicable.
- Metadata.
- Representment details.

## How Chargebacks Are Created

A Chargeback may enter RevCent in several ways.

Manual creation usually starts from the Transaction details page. A user views the Transaction related to the dispute, clicks the Chargeback action, and completes the chargeback fields.

Automated or API-based creation is useful when a merchant, payment operation, or third-party chargeback management provider receives dispute information outside RevCent and needs to sync it into RevCent.

The important concept is that the Chargeback should be connected to the correct credit card Transaction. That connection allows RevCent to attach the Chargeback to the correct customer history, sale history, gateway information, and potential evidence package.

Conceptual flow:

```text
Credit card Transaction is created
  ↓
Customer or issuer disputes the charge
  ↓
Chargeback is created in RevCent
  ↓
Chargeback is linked to the original Transaction
  ↓
RevCent connects the dispute to customer, sale, gateway, and related records
```

## Where Users View Chargebacks

Users can view Chargebacks in the RevCent web app under:

```text
Payments > Credit Card > Chargebacks
```

The web app also supports viewing a Chargeback details page. The details page helps users inspect the Chargeback and its related entities, such as the original Transaction, Sale, products sold, shipping, tax, subscriptions, and other connected records.

This makes Chargebacks useful for dispute review, support research, customer-risk analysis, and operational follow-up.

## Chargebacks and Transactions

The Transaction relationship is the core relationship for Chargebacks.

A Transaction is the original payment record. A Chargeback is the dispute record created after that payment is challenged or reversed.

The relationship matters because the Transaction can provide:

- Payment amount.
- Gateway used.
- Gateway transaction ID.
- Gateway response data.
- Authorization and result codes.
- Customer Card reference information.
- BIN 6 and last 4 information.
- Payment Profile context when applicable.
- Sale, Customer, Subscription, Trial, or Salvage Transaction context.

When reviewing a Chargeback, the source Transaction should usually be inspected first. If the wrong Transaction is connected to a Chargeback, downstream reporting, evidence, customer history, and representment analysis may be incorrect.

## Representment Tracking

Representment is the process of fighting or responding to a Chargeback.

RevCent Chargebacks can store representment details so a business can track whether a Chargeback was fought, whether representment was completed, and whether the result was won, lost, or still pending.

Representment tracking is useful because a Chargeback is not always just a final loss. A merchant or third-party chargeback mitigation provider may submit evidence, wait for a decision, and later update the outcome.

Conceptual representment flow:

```text
Chargeback received
  ↓
Representment is initiated
  ↓
Evidence is submitted
  ↓
Representment is completed
  ↓
Outcome is recorded
```

Tracking these fields helps businesses understand dispute performance over time, including win/loss rates, reason-code patterns, gateway or campaign risk, and which cases are worth fighting.

## Chargeback Documents and Evidence

Chargebacks often require supporting evidence. RevCent can support evidence workflows through chargeback document generation.

A chargeback document is an evidence package generated from the originating sale context. It can help show details such as who purchased, what was purchased, how the transaction was processed, whether shipping or tracking information exists, and what customer or visitor context was available.

Evidence may include details from:

- Original API call.
- Customer.
- Sale.
- Product sale records.
- Transaction.
- Shipping.
- Tracking visitor activity.
- Fraud detection records.
- Chargeback metadata.

This can be useful for internal review, external chargeback mitigation providers, and representment workflows.

When a chargeback document package is generated, the document URL should be treated as temporary and downloaded promptly if it is needed for a dispute case.

## Chargebacks and Customers

Because Chargebacks connect to Customers through the original payment and sale history, they are useful for customer-level risk review.

A customer with Chargeback history may need a different operational path than a customer with a clean history. Depending on the business policy, a customer with one or more Chargebacks may be reviewed before future purchases, added to a customer group, marked with metadata, suppressed from outreach, or escalated to a risk or support team.

Useful customer-level questions include:

- Has this Customer created a Chargeback before?
- How many Chargebacks are associated with this Customer?
- What was the total Chargeback amount?
- Were any representments won or lost?
- Is the Customer also associated with fraud detections, refunds, failed renewals, or support issues?

The Chargeback item is therefore not only a dispute record. It is also a customer-history signal.

## Chargebacks and Ecommerce Risk

Chargebacks are high-value risk signals for ecommerce businesses.

A Chargeback may indicate:

- Fraud or friendly fraud.
- Product dissatisfaction.
- Fulfillment or delivery issues.
- Subscription cancellation confusion.
- Billing descriptor confusion.
- Customer support breakdown.
- Poor traffic quality.
- Campaign or affiliate quality issues.
- Gateway or merchant-account risk.

For this reason, Chargebacks should be reviewed as part of payment operations, customer support, fraud review, and business reporting.

## Chargebacks and AI Assistants

AI Assistants can use Chargeback information as context for analysis and follow-up workflows.

Examples include:

- Summarizing a Customer's Chargeback history.
- Reviewing whether a Chargeback appears connected to fraud, fulfillment, billing confusion, or support issues.
- Summarizing the related Transaction and Sale context.
- Reviewing Chargeback reason codes and available evidence.
- Creating internal notes or AI Memos for risk teams.
- Recommending customer group placement, such as manual review or chargeback-risk groups.
- Analyzing trends across Chargebacks with BigQuery.

AI should not treat every Chargeback as the same type of issue. A dispute connected to an undelivered shipment may need a different response than a dispute connected to a fraud pattern or subscription billing confusion.

## Chargebacks and Functions / External Systems

Functions and external systems can extend Chargeback workflows.

Common patterns include:

```text
Chargeback created
  ↓
Function sends the dispute to an external risk or chargeback platform
```

```text
Chargeback representment outcome updated
  ↓
Function updates customer metadata or customer group placement
```

```text
Chargeback amount exceeds a threshold
  ↓
Function alerts finance, risk, or support teams
```

```text
Third-party chargeback provider syncs a dispute
  ↓
RevCent stores third-party IDs and links the dispute to the original Transaction
```

These workflows help make Chargebacks operational instead of passive historical records.

## Chargebacks and BigQuery

The `chargeback` BigQuery table contains Chargebacks created manually or by API.

Use BigQuery when the goal is reporting, analysis, or trend detection rather than reviewing one individual Chargeback.

The `chargeback` table can support questions such as:

- How many Chargebacks were created in a date range?
- What is total Chargeback amount by Campaign?
- Which Gateways or merchant accounts are associated with the most Chargebacks?
- Which reason codes are most common?
- Which Customers have multiple Chargebacks?
- Which currencies, card BIN 6 values, or card brands are most represented?
- Which Chargebacks are related to subscriptions, trials, or salvage recoveries?
- Which metadata values are associated with dispute risk?

Important fields in the `chargeback` table include:

| Field | Meaning |
|---|---|
| `created_at` | When the Chargeback was created in RevCent. |
| `id` | Chargeback ID. |
| `amount` | Chargeback amount. |
| `live_mode` | Whether the Chargeback was live or test mode. |
| `campaign` | Campaign associated with the Chargeback. |
| `customer_card` | Customer Card associated with the Chargeback. |
| `iso_currency` | Currency code. |
| `reason_code` | Chargeback reason code. |
| `request_type` | Origin request type. |
| `request_method` | Origin request method. |
| `first_6` | BIN 6 of the associated customer card. |
| `last_4` | Last 4 digits of the associated customer card. |
| `gateway_transaction_id` | Gateway transaction ID. |
| `arn` | Acquirer reference number. |
| `merchant_account_id` | Merchant account ID associated with the Chargeback. |
| `received_date` | Date the Chargeback was received. |
| `chargeback_date` | Date the Chargeback was filed. |
| `case_number` | Chargeback case number. |
| `gateway` | Gateway associated with the Chargeback. |
| `sale` | Sale associated with the Chargeback. |
| `customer` | Customer associated with the Chargeback. |
| `subscription` | Subscription associated with the Chargeback, if applicable. |
| `trial` | Trial associated with the Chargeback, if applicable. |
| `subscription_renewal` | Subscription Renewal associated with the Chargeback, if applicable. |
| `salvage_transaction` | Salvage Transaction associated with the Chargeback, if applicable. |
| `tax` | Related Tax records. |
| `shipping` | Related Shipping records. |
| `transaction` | Transaction associated with the Chargeback. |
| `metadata` | Custom metadata attached to the Chargeback. |

Example conceptual BigQuery table reference:

```sql
`revcent.user.chargeback`
```

## Practical Ecommerce Use Cases

### Monitor Chargeback Volume

Use Chargebacks to monitor dispute volume by date, Campaign, Gateway, merchant account, currency, reason code, or product context.

### Review Customer Risk

Use Chargebacks to identify Customers with prior dispute history and decide whether future purchases should be allowed, reviewed, suppressed, or routed through a manual process.

### Coordinate Representment

Use representment fields to track which Chargebacks were fought and whether they were won, lost, or pending.

### Support Third-Party Chargeback Management

Use API and automation workflows to help external chargeback management providers create or update Chargeback records and request evidence packages.

### Improve Support and Fulfillment

Use Chargeback patterns to identify product, shipping, customer service, subscription, or billing issues that may be causing disputes.

## Best Practices

1. Link each Chargeback to the correct source Transaction whenever possible.
2. Store accurate case, ARN, reason code, amount, gateway transaction, and received-date information.
3. Use metadata for external case IDs, provider names, review statuses, and internal risk flags.
4. Use representment fields to track whether a dispute was fought and what the outcome was.
5. Use evidence documents when the business or mitigation provider needs structured purchase proof.
6. Use BigQuery for Chargeback metrics and trends rather than relying on list views.
7. Treat customer-level Chargeback history as a meaningful risk and support signal.
8. Avoid duplicate Chargeback records for the same dispute unless the business has a clear reason.

## Summary

Chargebacks are RevCent items that represent credit card disputes tied to source Transactions.

They help connect dispute activity to the original Transaction, Customer, Sale, Gateway, Campaign, and related ecommerce records. They also support representment tracking, evidence generation, third-party chargeback management, AI-assisted review, and BigQuery reporting.

The most important concept is:

```text
Chargeback = dispute item connected to a credit card Transaction and its broader customer/payment context
```

Used well, Chargebacks help ecommerce businesses monitor dispute risk, understand customer history, fight disputes with evidence, and make better operational decisions across payments, support, fraud, and revenue recovery.


---
Document Parent Directory
* [Items](https://revcent.com/documentation/markdown/ecosystem/item/index.md) - Non-technical markdown documentation for items within the RevCent ecosystem. An item is an entity that is spawned as a result of a feature or operation conducted within the RevCent ecosystem.