# RevCent Chargebacks Overview This document gives a broad overview of how chargebacks work in RevCent and how ecommerce businesses can use RevCent chargeback data for monitoring, reporting, customer history, repurchase prevention, and chargeback mitigation. This is not an MCP guide. It is a RevCent overview of the chargeback capability as a business, reporting, customer-risk, and evidence-management tool. Sources: - RevCent Knowledge Base: Chargebacks — `https://kb.revcent.com/en/payments/credit-card/chargeback` - RevCent Knowledge Base: Automated Chargeback Management — `https://kb.revcent.com/payments/credit-card/automated-chargeback-management` - RevCent Knowledge Base: Chargeback Documents — `https://kb.revcent.com/en/tools/documents` - RevCent API operation details for chargebacks, chargeback documents, customers, customer groups, and BigQuery reporting --- ## What Is a Chargeback in RevCent? A chargeback in RevCent represents a credit card dispute or reversal connected to a prior credit card transaction. A chargeback is not just a standalone dispute record. In RevCent, it can be tied back to the original payment and ecommerce context, including: - Customer - Sale - Product sale - Credit card transaction - Gateway transaction - Gateway - Merchant account - Campaign - Shipping - Taxes - Discounts - Trials - Subscriptions - Subscription renewals - Invoices - License keys - Fraud detections - API calls - Metadata - Chargeback representment status This makes the chargeback record useful for monitoring, reporting, customer history, risk analysis, operational follow-up, and evidence generation. --- ## Why Chargebacks Matter Chargebacks are a serious ecommerce signal. They can indicate: - Customer dispute - Fraud - Friendly fraud - Fulfillment issue - Product dissatisfaction - Billing confusion - Subscription cancellation confusion - Payment authorization dispute - Delivery or shipping dispute - Customer support issue - Gateway or merchant account risk - Campaign/source quality issue Because chargebacks affect revenue, risk, merchant account standing, and customer trust, they should be tracked carefully. RevCent helps by connecting chargebacks back to the transaction, customer, sale, and related business data. --- # How Chargebacks Are Created in RevCent A chargeback in RevCent must be associated with a previous credit card transaction. The chargeback can be created using either: ```text transaction_id ``` or: ```text gateway_transaction_id ``` This matters because the chargeback should tie back to the original transaction that was disputed. Conceptual flow: ```text Customer makes purchase ↓ Credit card transaction is created ↓ Issuer/customer creates dispute ↓ Merchant receives chargeback ↓ Chargeback is created in RevCent and linked to original transaction ↓ RevCent connects chargeback to customer, sale, gateway, products, shipping, and related records ``` --- ## Chargeback Creation Sources Chargebacks may be created in different ways. Examples: - Manually by a user. - Through a chargeback management workflow. - Through a third-party chargeback management company. - Through API-based chargeback automation. - Through an internal operational process that receives chargeback data from another system. When created by a third-party chargeback management provider, the chargeback can include third-party identifiers such as: - Third-party integration ID - Third-party chargeback ID - Third-party order ID This helps RevCent store the relationship between the RevCent chargeback and the external chargeback system. --- ## Chargeback Details Stored A chargeback record can include details such as: - Chargeback amount - Acquirer reference number, also known as ARN - Case number - Reason code - Chargeback date - Received date - Gateway transaction ID - Gateway - Merchant account ID - Currency - Live/test mode - Related customer - Related sale IDs - Related product sale IDs - Related shipping IDs - Related transaction IDs - Metadata - Third-party integration details - Representment status and outcome This provides a structured record of the dispute and how it relates to the rest of the business. --- # Representment Tracking Representment is the process of fighting or responding to a chargeback. RevCent chargebacks can store representment details, including: - Whether representment was initiated - Representment initiated date - Whether representment was completed - Representment completed date - Representment outcome Possible outcomes include: ```text pending won lost ``` This is important because a chargeback is not always final at the moment it is received. A merchant or chargeback mitigation company may submit evidence, fight the dispute, and later receive an outcome. Conceptual flow: ```text Chargeback received ↓ Representment initiated ↓ Evidence submitted ↓ Representment completed ↓ Outcome recorded as won or lost ``` --- ## Why Representment Tracking Matters Tracking representment helps businesses understand: - Which chargebacks were fought. - Which chargebacks were not fought. - Which chargebacks were won. - Which chargebacks were lost. - Which reason codes are most winnable. - Which campaigns or products generate disputes. - Which chargeback mitigation partner is performing well. - Which evidence packages are effective. - Whether chargeback losses are concentrated by gateway, product, campaign, or customer segment. Without representment tracking, chargebacks become a revenue loss number without operational insight. --- # Chargebacks for Monitoring RevCent chargebacks help businesses monitor dispute activity across the business. Monitoring can answer questions like: ```text How many chargebacks have we received this week? ``` ```text Which campaigns are generating chargebacks? ``` ```text Which gateway or merchant account is seeing the most chargebacks? ``` ```text Which customers have chargeback history? ``` ```text Which products have higher dispute rates? ``` ```text Which chargebacks are pending representment? ``` ```text Which chargebacks have been won or lost? ``` ```text Which chargebacks came from third-party management systems? ``` Chargeback monitoring is important because dispute activity can affect more than individual sales. It can affect processing relationships, risk review, customer support priorities, and profitability. --- # Chargebacks for Reporting Chargebacks should be reported on at the business level. For list views and individual chargeback review, RevCent chargeback records can be searched or retrieved. For counts, metrics, aggregations, and trends, BigQuery should be used. BigQuery reporting can answer: - Total chargeback amount by date range - Chargeback count by date range - Chargeback rate by campaign - Chargeback amount by gateway - Chargeback amount by merchant account - Chargeback count by product - Chargeback count by customer group - Chargebacks by reason code - Chargebacks by currency - Chargebacks by third-party provider - Representment win/loss rate - Chargeback losses after representment - Chargeback amount compared to gross sales - Chargeback rate by affiliate or metadata - Chargeback rate by customer lifetime value segment - Chargeback rate by subscription status - Chargeback rate by product group --- ## Reporting Examples ### Campaign Risk ```text Campaign A generated high revenue but also high chargebacks. ``` This may indicate poor traffic quality, misleading offer expectations, affiliate issues, or product/customer mismatch. ### Gateway Risk ```text Gateway B has a higher chargeback count than Gateway A. ``` This may indicate that certain traffic, products, or risk profiles are being routed differently. ### Product Risk ```text Product Group C has more chargebacks than other product groups. ``` This may indicate product dissatisfaction, delivery issues, billing confusion, or unclear marketing. ### Customer Segment Risk ```text Customers from metadata affiliate_id = aff_123 have a higher chargeback rate. ``` This helps evaluate affiliate quality and customer acquisition quality. ### Representment Performance ```text Chargebacks with reason code X are often won, while reason code Y is rarely won. ``` This helps decide when fighting a chargeback is worth the effort. --- # Chargebacks Per Customer One of the most important advantages of tracking chargebacks in RevCent is that chargebacks are connected to customer records. This allows a business to see customer-level dispute history. Customer chargeback history can help answer: ```text Has this customer charged back before? ``` ```text How many chargebacks are associated with this customer? ``` ```text What is the total chargeback amount for this customer? ``` ```text Was the customer’s previous chargeback won or lost? ``` ```text Did the same customer dispute multiple purchases? ``` ```text Is this customer also associated with refunds, fraud detections, or payment failures? ``` This customer-level view is important for support, risk review, repurchase prevention, and future payment decisions. --- ## Customer-Level Chargeback Risk A customer with chargeback history may need to be treated differently than a customer with no dispute history. Possible actions include: - Add customer to a Chargeback Risk group. - Add customer to a Manual Review group. - Disable or block customer if appropriate. - Require human review before future purchases. - Suppress automated offers. - Suppress AI Voice Agent sales outreach. - Notify customer support before further engagement. - Review customer metadata and notes. - Review related sales, transactions, shipments, and fraud detections. The goal is not only to record the chargeback, but to make sure future customer workflows understand that the chargeback happened. --- # Preventing Chargeback Customers From Re-Purchasing RevCent customer data can be used to prevent customers with chargeback history from repurchasing when the business decides that is appropriate. A business may not want to continue selling to customers who have: - One or more chargebacks - Repeated chargebacks - Lost representments - Chargeback plus fraud detection history - Chargeback plus refund abuse history - Chargeback plus support abuse history - Chargeback plus suspicious metadata - Chargeback plus high-risk order patterns RevCent can support prevention strategies through customer status, customer groups, metadata, and workflows. --- ## Customer Blocking If a customer should not be allowed to purchase again, the customer can be blocked or disabled according to the business’s policy. A blocked customer flag helps future workflows understand that the customer should not be treated like a normal eligible customer. Conceptual flow: ```text Chargeback created ↓ Customer is associated with chargeback ↓ Business determines customer should not repurchase ↓ Customer is blocked or added to suppression group ↓ Future purchase/support/AI workflows can treat customer differently ``` --- ## Customer Groups for Chargeback Prevention Customer Groups are especially useful for organizing customers with chargeback history. Example groups: ```text Chargeback Risk Do Not Sell Manual Review Required Chargeback Customer Repeat Chargeback Customer Lost Representment Customer Fraud + Chargeback Review ``` These groups can be used to: - Filter customers - Generate reports - Trigger internal review - Suppress outreach - Prevent automated offers - Trigger AI Assistant review - Trigger external risk review - Alert support teams - Route future purchase attempts differently --- ## Group-Based Chargeback Automation A customer entering a chargeback-related group can trigger automation. Examples: ```text Customer added to Chargeback Risk ↓ AI Assistant summarizes customer history ↓ Function sends record to risk system ↓ Customer support note is created ``` ```text Customer added to Do Not Sell ↓ Future outreach is suppressed ↓ Support is alerted before any manual order ``` ```text Customer added to Manual Review Required ↓ Third-party AI Agent reviews prior behavior ↓ Risk recommendation is returned ``` Customer groups allow chargeback information to become operational, not just historical. --- # Metadata for Chargeback Context Chargeback records and customers can use metadata to store additional business-specific context. Examples: ```text chargeback_source = midigator chargeback_partner_case_id = abc123 risk_review_status = pending customer_dispute_pattern = repeat representment_strategy = fight evidence_requested = true evidence_sent_at = 2026-05-28 external_case_status = submitted ``` Metadata can help connect RevCent chargeback data to chargeback management providers, CRM systems, risk systems, reporting workflows, and internal review processes. --- # Automated Chargeback Management RevCent can support automated chargeback management workflows, especially for third-party chargeback management companies. A chargeback management company may need to: 1. Create or sync a chargeback into RevCent. 2. Search for the related transaction or chargeback. 3. Request or create evidence for the originating sale. 4. Indicate that representment has been initiated. 5. Update the representment outcome once completed. 6. Store external IDs and metadata for reconciliation. This creates a workflow where RevCent becomes the system that connects the dispute to the underlying sale/customer evidence. Conceptual flow: ```text Chargeback received by third-party system ↓ Chargeback is created in RevCent ↓ Chargeback is linked to transaction/sale/customer ↓ Chargeback document is created from originating sale ↓ Evidence is submitted by mitigation company ↓ Representment status is updated ↓ Outcome is recorded as pending, won, or lost ``` --- ## Third-Party Chargeback Management Companies Third-party chargeback mitigation companies can use RevCent chargeback data to: - Import or create chargeback records. - Connect chargebacks to original transactions. - Retrieve customer and sale context. - Generate chargeback documents. - Access evidence packages. - Track representment initiation. - Track representment completion. - Report outcomes back to the merchant. - Store external chargeback IDs and order IDs. - Keep RevCent aligned with the external chargeback platform. This helps the merchant and third-party provider work from the same chargeback context. --- # Chargeback Documents Chargeback Documents are used for chargeback mitigation. A Chargeback Document is created from an originating sale and contains evidence related to the purchase. The purpose is to help prove that the customer made the purchase and to provide supporting evidence such as transaction, customer, tracking visitor, product, and shipping information. Chargeback Documents are especially useful for: - Chargeback representment - Dispute response - Chargeback mitigation companies - Internal risk review - Customer purchase evidence - Shipping/delivery evidence - Tracking visitor evidence - Transaction evidence - Raw JSON evidence export - Friendly formatted `.docx` evidence package --- # `CreateChargebackDocument` The relevant operation for chargeback evidence generation is: ```text CreateChargebackDocument ``` This operation creates a chargeback mitigation document from an originating sale by searching for the sale using: ```text item_type item_value ``` Allowed `item_type` values include: ```text sale transaction shipping fraud_detection chargeback ``` The `item_value` is the value used to search for the selected item type. Examples: ```json { "item_type": "chargeback", "item_value": "CHARGEBACK_ID_OR_SEARCH_VALUE" } ``` ```json { "item_type": "transaction", "item_value": "TRANSACTION_ID_OR_GATEWAY_TRANSACTION_VALUE" } ``` ```json { "item_type": "sale", "item_value": "SALE_ID_OR_SEARCH_VALUE" } ``` The operation creates evidence based on the originating sale related to that item. --- ## CreateChargebackDocument Output `CreateChargebackDocument` can return: - Document ID - Expiration date - ZIP URL - Raw document JSON - Result message The `zip_url` points to a ZIP file that contains: - A friendly formatted `.docx` file - The raw `document_json` in a `.json` file Important: ```text Document URLs expire after 24 hours. ``` This means a chargeback mitigation provider or internal team should download/store the document package promptly after creation if needed for a dispute case. --- ## What Evidence Can Be Included? A chargeback document can include detailed evidence from the originating sale. Examples of evidence included in the raw document JSON may include: ### API Call / Original Request Evidence - API account - API call ID - Request type - Request method - Billing details - Shipping details - Customer ID - IP address - Metadata - Payment profile - Products requested - Shipping requested - Unique request ID ### Customer Evidence - Customer ID - Name - Email - Phone - Address - Company - Enabled/blocked state - Internal ID - Metadata - Device details - IP details - Email intelligence details - Phone intelligence details ### Sale Evidence - Sale ID - Sale amount - Created date - Unique request ID - Currency - Campaign ### Product Evidence - Product ID - Product internal ID - Product name - SKU - Price - Quantity - Total amount ### Transaction Evidence - Transaction ID - Amount - Approved/declined/error status - Gateway - Gateway transaction ID - Gateway result phrase - Gateway authorization code - AVS/CVV/CAVV result codes - Merchant account ID - Customer card reference data - BIN details ### Shipping Evidence - Shipping ID - Shipping provider - Shipping method - Tracking number - Tracking URL - Shipped status - Delivered status - Ship date - Delivered date - Ship-to details - Fulfillment account - Fulfillment notification status ### Tracking Visitor Evidence - Tracking visitor ID - Visitor fingerprint - IP address - User agent - IP geolocation details - Network/company details - Threat/proxy/TOR/datacenter indicators - Tracking entries - Tracking domain - Host/path visited ### Fraud Detection Evidence - Fraud detection request ID - Fraud score - Fraud threshold - Whether fraud was detected - Third-party fraud detection ID - Raw response details ### Chargeback Evidence - Chargeback record details - Related chargeback records - Metadata - Case or external identifiers when present This evidence can help support representment by showing purchase, customer, transaction, visitor, and fulfillment context. --- # How Chargeback Mitigation Companies Can Use CreateChargebackDocument Chargeback mitigation companies can use `CreateChargebackDocument` to generate evidence packages for chargebacks they are fighting. Example workflow: ```text Chargeback mitigation company receives chargeback case ↓ Chargeback is created or identified in RevCent ↓ Provider calls CreateChargebackDocument using item_type = chargeback ↓ RevCent finds the originating sale ↓ RevCent creates document package ↓ Provider downloads ZIP containing .docx and raw JSON ↓ Provider uses evidence in representment package ↓ Representment initiated/completed status is updated in RevCent ``` This allows a third-party provider to obtain evidence without manually reconstructing the purchase history from many separate systems. --- ## Why This Helps Chargeback Mitigation Chargeback mitigation depends on evidence. A good evidence package may need to show: - Who purchased - What was purchased - When it was purchased - How it was paid - Which gateway processed it - Which card reference was used - Whether fraud detection ran - What IP/device/visitor information was associated - Whether the item was shipped - Whether tracking exists - Whether the package was delivered - Whether customer/billing/shipping data matched - Whether there was prior customer history - Whether metadata or unique request IDs link the transaction to the merchant’s records `CreateChargebackDocument` helps package that information from RevCent into a usable `.docx` and raw JSON evidence format. --- # Chargeback Documents Are Not General Documentation Chargeback Documents should not be confused with product documentation or system documentation. They are evidence documents. Their main purpose is chargeback mitigation and purchase proof. They are designed to help prove facts about the originating sale, such as: ```text Customer purchased this item. Transaction was attempted or approved. Shipping/tracking evidence exists. Visitor/tracking evidence exists. Customer/order details were recorded. ``` --- # Chargebacks and Customers Because chargebacks connect to customers, chargeback data can become part of customer intelligence. A customer with chargeback history may be: - Added to a chargeback risk group - Marked with metadata - Reviewed by support - Reviewed by risk team - Blocked or disabled - Suppressed from future offers - Prevented from repurchasing - Routed to manual review - Excluded from automated AI Voice Agent sales outreach - Reported on in BigQuery Customer-level chargeback data is especially important because some chargeback risk is behavioral, not just transaction-specific. --- # Chargebacks and Customer Groups Customer Groups can help operationalize chargeback history. Example groups: ```text Chargeback Customer Repeat Chargeback Customer Chargeback Risk Do Not Sell Manual Review Required Fraud + Chargeback Review Lost Representment Customer Won Representment Customer ``` These groups can be populated manually, through workflows, or through automation. Group changes can trigger workflows such as: - AI Assistant customer summary - Function call to external risk system - Customer support alert - Third-party AI Agent review - Suppression from marketing outreach - Manual review before new sale - Customer status change - BigQuery monitoring --- # Chargebacks and AI Assistants AI Assistants can help with chargeback workflows by analyzing customer, transaction, and dispute context. Possible AI Assistant tasks: - Summarize a customer’s chargeback history. - Determine whether a customer should be reviewed before future purchases. - Summarize the evidence in a chargeback document. - Compare chargeback reason code with available evidence. - Suggest whether a chargeback should be fought. - Create internal risk notes. - Identify patterns across chargeback metadata. - Recommend customer group placement. - Recommend whether to block or suppress a customer. - Generate a plain-English case summary for a mitigation company or support team. AI Assistants can be useful because chargebacks often require context, not just raw fields. --- # Chargebacks and Functions / External Tools Functions and external tools can extend chargeback workflows. Examples: ```text Chargeback created ↓ Function sends chargeback to external risk platform ``` ```text Chargeback created by third-party provider ↓ Function updates CRM or helpdesk ticket ``` ```text Chargeback document created ↓ External mitigation company downloads document package ``` ```text Representment outcome updated to lost ↓ Function adds customer to Do Not Sell group ``` ```text Chargeback amount exceeds threshold ↓ Function alerts finance or risk team ``` Third-party AI Agents can also use chargeback data to classify risk, summarize evidence, recommend response strategy, or coordinate chargeback mitigation workflows. --- # Chargebacks and BigQuery For chargeback analytics, BigQuery is the best tool for metrics, grouping, and reporting. Use list/search views to locate individual chargebacks. Use BigQuery for: - Counts - Totals - Rates - Trends - Aggregations - Segment analysis - Group-by reporting - Campaign/gateway/product/customer analysis - Representment win/loss analysis Example reporting questions: ```text How many chargebacks did we receive last month? ``` ```text What was total chargeback amount by campaign? ``` ```text Which customer groups have the highest chargeback rate? ``` ```text Which gateways have the most chargeback amount? ``` ```text Which products generate the most disputes? ``` ```text Which reason codes are most common? ``` ```text Which representment cases were won or lost? ``` ```text Which chargeback mitigation partner has the best win rate? ``` ```text Which customers have multiple chargebacks? ``` ```text Which affiliate metadata values are associated with chargebacks? ``` BigQuery reporting turns chargebacks into business intelligence instead of isolated case records. --- # Chargeback Lifecycle Example ```text 1. Customer purchases product. 2. Credit card transaction is created. 3. Customer or issuer initiates chargeback. 4. Chargeback is created in RevCent and linked to transaction. 5. Chargeback links back to customer, sale, products, shipping, gateway, and metadata. 6. Customer may be added to Chargeback Risk group. 7. AI Assistant or risk workflow reviews customer history. 8. CreateChargebackDocument generates evidence package. 9. Chargeback mitigation provider submits representment. 10. Representment is marked pending, won, or lost. 11. BigQuery reports chargeback outcome and business impact. 12. Customer future purchase eligibility is updated if needed. ``` --- # Practical Ecommerce Use Cases ## Monitoring Chargeback Volume ```text Track chargebacks by date, campaign, gateway, and product. ``` Benefit: ```text Detect issues early before they become larger merchant-account or business-risk problems. ``` --- ## Preventing Repeat Chargeback Customers ```text Customer has prior chargeback history ↓ Customer is added to Chargeback Risk or Do Not Sell group ↓ Future purchase attempts can be reviewed or blocked according to business policy ``` Benefit: ```text Protects the business from repeat dispute behavior. ``` --- ## Fighting Chargebacks With Evidence ```text Chargeback received ↓ CreateChargebackDocument generates .docx and raw JSON ↓ Mitigation company uses purchase, tracking visitor, shipping, and transaction evidence ↓ Representment outcome is tracked ``` Benefit: ```text Evidence can be generated from RevCent instead of manually piecing together records. ``` --- ## Reporting on Chargeback Risk ```text Chargebacks are grouped by campaign, product, customer group, affiliate metadata, or gateway. ``` Benefit: ```text The business can see which acquisition sources, products, or customer segments generate dispute risk. ``` --- ## Improving Customer Support ```text Support sees customer has prior chargeback history ↓ Support handles new requests with more context ``` Benefit: ```text Support avoids treating high-risk customers the same as customers with clean history. ``` --- ## Coordinating With Third-Party Chargeback Managers ```text Third-party chargeback company creates chargeback records ↓ Requests evidence through CreateChargebackDocument ↓ Updates representment status and outcome ``` Benefit: ```text RevCent and the provider can coordinate using shared chargeback, customer, transaction, and evidence data. ``` --- # Best Practices ## Link Chargebacks to the Correct Transaction A chargeback should be associated with the correct original credit card transaction using `transaction_id` or `gateway_transaction_id`. This ensures RevCent can connect the chargeback to the correct customer, sale, products, shipping, and evidence. --- ## Store Third-Party IDs When using a third-party chargeback management company, store third-party identifiers when available. Useful fields include: ```text third_party_integration_id third_party_chargeback_id third_party_order_id ``` This helps reconcile RevCent chargebacks with external systems. --- ## Use Metadata for Business Context Use metadata to store custom chargeback context. Examples: ```text chargeback_source external_case_status evidence_requested representment_strategy risk_review_status ``` --- ## Use Customer Groups for Prevention Create customer groups such as: ```text Chargeback Risk Do Not Sell Manual Review Required Repeat Chargeback Customer ``` These groups make it easier to filter, report, and trigger workflows. --- ## Use CreateChargebackDocument for Evidence Use `CreateChargebackDocument` when a chargeback needs purchase evidence. It can generate: - Friendly formatted `.docx` - Raw JSON evidence - ZIP package - Originating sale context Remember: ```text Document URLs expire after 24 hours. ``` --- ## Use BigQuery for Metrics Do not rely on chargeback list views for reporting metrics. Use BigQuery to measure: - Count - Amount - Rate - Trend - Customer segment - Campaign impact - Product impact - Gateway impact - Representment outcomes --- # Summary Chargebacks in RevCent are more than dispute records. They connect customer, transaction, sale, shipping, campaign, gateway, fraud, subscription, and metadata context into one chargeback history. RevCent chargebacks help ecommerce businesses: - Monitor disputes - Track chargebacks per customer - Report on chargeback trends - Understand chargeback risk by campaign, product, gateway, customer, and metadata - Prevent repeat chargeback customers from repurchasing - Coordinate with chargeback mitigation providers - Track representment status and outcomes - Generate chargeback evidence through `CreateChargebackDocument` - Use `.docx` and raw JSON purchase evidence in representment workflows - Improve fraud/risk and customer support decisions The key concept is: ```text A RevCent chargeback is not only a dispute. It is a connected risk, reporting, customer-history, and evidence object that can help the business monitor, prevent, and fight chargebacks. ``` --- 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.