--- title: "Chargeback Evidence" description: "A non-technical overview of Chargeback Evidence in RevCent, focused on how evidence packages support chargeback mitigation, how documents connect Chargebacks to originating sales and transactions, and how businesses, AI systems, and third-party providers can coordinate representment workflows." type: "feature" company: "RevCent" canonical: "https://revcent.com/documentation/markdown/ecosystem/feature/ChargebackEvidence.md" relationships: - name: "Chargeback" url: "https://revcent.com/documentation/markdown/ecosystem/item/Chargeback.md" - name: "Transaction" url: "https://revcent.com/documentation/markdown/ecosystem/item/Transaction.md" - name: "Sale" url: "https://revcent.com/documentation/markdown/ecosystem/item/Sale.md" - name: "Shipping" url: "https://revcent.com/documentation/markdown/ecosystem/item/Shipping.md" - name: "Fraud Detection" url: "https://revcent.com/documentation/markdown/ecosystem/item/FraudDetection.md" - name: "Function" url: "https://revcent.com/documentation/markdown/ecosystem/feature/Function.md" technical_links: web_app: "https://kb.revcent.com/en/payments/credit-card/automated-chargeback-management" api: section: "https://revcent.com/docs/api/v2#section-chargebacks" operations: - 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" - 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: "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: "Search Transactions" operation_id: "SearchTransactions" operation: "https://revcent.com/docs/api/v2#operation-SearchTransactions" schema: "https://revcent.com/documentation/files/api/operation/SearchTransactions.json" mcp: related_markdown: - name: "Create Chargeback Document" markdown: "https://revcent.com/documentation/markdown/mcp/operation/CreateChargebackDocument.md" - name: "Create Chargeback" markdown: "https://revcent.com/documentation/markdown/mcp/operation/CreateChargeback.md" - name: "Edit Chargeback" markdown: "https://revcent.com/documentation/markdown/mcp/operation/EditChargeback.md" - name: "Chargeback Overview" markdown: "https://revcent.com/documentation/markdown/mcp/operation/OverviewChargeback.md" --- # Chargeback Evidence Chargeback Evidence is the RevCent capability for gathering and packaging purchase, payment, customer, shipping, tracking, and risk context that may help a business respond to a credit card chargeback. In the RevCent ecosystem, Chargeback Evidence is not the Chargeback item itself. A Chargeback is the dispute record. Chargeback Evidence is the supporting package and workflow that helps a business, risk team, or chargeback mitigation provider understand and respond to that dispute. The practical idea is: ```text Chargeback = dispute record Chargeback Evidence = supporting purchase proof and context for review or representment ``` Chargeback Evidence is especially important when a business intends to fight a chargeback through representment. The purpose of this document is to explain the feature conceptually for LLMs, AI crawlers, and planning systems. It does not provide technical implementation instructions. For technical details, use the interface-specific links below. ## Technical Links by Interface | Interface | Use This When | Link | |---|---|---| | Web App | A human or third-party provider is learning how automated chargeback management works with RevCent. | [Web Knowledge Base](https://kb.revcent.com/en/payments/credit-card/automated-chargeback-management) | | API | A developer is creating chargeback records, generating chargeback documents, searching disputes, or updating representment status. | [API Docs: Chargebacks](https://revcent.com/docs/api/v2#section-chargebacks) | | MCP / AI | An LLM, MCP client, or AI agent needs markdown-oriented guidance for generating chargeback evidence packages. | [MCP Markdown: CreateChargebackDocument](https://revcent.com/documentation/markdown/mcp/operation/CreateChargebackDocument.md) | --- ## Core Purpose The core purpose of Chargeback Evidence is to make dispute response more complete and less manual. When a chargeback arrives, a business often needs to assemble details from many places: - the original sale, - the customer, - the disputed transaction, - the card reference, - products purchased, - shipping and delivery records, - tracking visitor context, - fraud detection context, - metadata, - gateway transaction IDs, - case or processor identifiers. Chargeback Evidence helps package that context so the business or its provider can decide whether to fight the dispute and can prepare a representment package when appropriate. Conceptually: ```text Chargeback received | Find originating Transaction or Sale | Gather customer, payment, shipping, tracking, and risk context | Generate evidence package | Submit or review evidence for representment | Update Chargeback representment outcome ``` --- ## Where Chargeback Evidence Fits in RevCent Chargeback Evidence sits in RevCent's dispute, payment, and customer-history layer. It connects to: - Chargebacks, because evidence usually starts from a dispute record. - Transactions, because the disputed charge came from a credit card payment attempt. - Sales, because the original purchase context gives meaning to the dispute. - Shipping, because delivery and tracking details may support the merchant's response. - Fraud Detection, because risk context may explain whether the purchase looked legitimate or suspicious. - Functions, because external providers may receive transaction events or automate chargeback workflows. Chargeback Evidence is a supporting workflow. It does not replace the Chargeback record, the source Transaction, or representment tracking. --- ## Relationship to Chargebacks The Chargeback item is the central dispute record. Chargeback Evidence exists to support review or response to that Chargeback. If the business is fighting the dispute, the evidence package helps show what happened around the originating sale. Typical relationship: ```text Chargeback item | Connected Transaction and Sale | Chargeback Evidence document | Representment package or internal review ``` The evidence package helps with dispute response, but it does not by itself mark the chargeback as fought, pending, won, or lost. Those statuses belong on the Chargeback representment fields. --- ## Relationship to Transactions and Sales A chargeback is tied to an original credit card Transaction. That Transaction often connects to a Sale or another commerce event such as a subscription renewal, trial expiration, or recovery payment. Chargeback Evidence depends on those relationships because they explain the disputed payment. Useful evidence may include: - payment amount, - gateway transaction ID, - gateway response, - payment date, - customer card first 6 and last 4, - customer details, - sale products, - request type and request method, - billing and shipping context, - campaign or product context, - metadata or external order IDs. If the wrong Transaction or Sale is connected to the Chargeback, the evidence package may be incomplete or misleading. --- ## Relationship to Shipping and Delivery Shipping data can be important evidence for physical goods. A delivery-related dispute may depend on whether the item was shipped, which provider was used, which tracking number exists, whether the package was delivered, and which address was used. Conceptually: ```text Sale includes physical product | Shipping record is created | Carrier and tracking data are recorded | Chargeback Evidence can include delivery context ``` Shipping evidence does not guarantee a win, but it can help prove fulfillment activity and support product-not-received dispute responses. --- ## Relationship to Tracking Visitor and Fraud Context Chargeback Evidence may include visitor, IP, device, or fraud context when available. This context can help a reviewer understand whether the purchase looked consistent with a legitimate customer action or whether it showed signs of risk. It may also help connect the purchase to a website visit, checkout path, or fraud detection result. Useful context may include: - tracking visitor ID, - IP address and IP details, - user agent, - tracking entries, - fraud detection details, - card BIN details, - metadata associated with the purchase. This information should be treated as supporting context, not as automatic proof. A human or provider still needs to decide how it applies to the dispute reason. --- ## Chargeback Documents RevCent supports chargeback document generation through the `CreateChargebackDocument` operation. A chargeback document is an evidence package generated from the originating sale context. It is designed for chargeback mitigation, not general documentation or reporting. A successful document generation can provide: - a document ID, - a ZIP URL, - an expiration date, - raw document JSON, - a formatted document file inside the ZIP, - raw evidence JSON inside the ZIP. Important: ```text Generated document URLs expire after 24 hours. ``` If the evidence package is needed for a dispute case, the business or provider should download and retain it promptly according to its document-retention process. --- ## Choosing the Evidence Starting Point Chargeback Evidence can often be generated from several starting points. The best starting point depends on which RevCent record is known. | Starting Point | Use When | |---|---| | Chargeback | A Chargeback record exists and its ID is known. | | Sale | The original Sale is known but the Chargeback record may not be available. | | Transaction | The payment Transaction is known from processor, gateway, or RevCent context. | | Shipping | A shipping record is the strongest available reference for a delivery dispute. | | Fraud Detection | A fraud detection record is the strongest available reference for a fraud review. | For a known chargeback that will be fought, the Chargeback record is usually the best starting point because it should already be linked to the originating Transaction and Sale. --- ## Third-Party Chargeback Management Chargeback Evidence is useful for third-party chargeback management providers. A provider may need to: - receive approved transaction details from RevCent, - create Chargeback records when disputes are received outside RevCent, - search for matching Transactions or Chargebacks by gateway transaction ID or customer details, - request evidence packages, - submit evidence through its own representment workflow, - update RevCent when representment is initiated, - update RevCent when the outcome is won or lost. Conceptually: ```text Provider receives dispute | Provider creates or finds Chargeback in RevCent | Provider requests Chargeback Evidence | Provider submits evidence externally | Provider updates representment status in RevCent ``` This makes RevCent a source of dispute context while allowing external providers to manage their own submission processes. --- ## Relationship to Functions Functions can help automate chargeback and evidence workflows. A Function may send approved transaction details to an external provider, notify a risk team when a Chargeback is created, or coordinate follow-up when representment outcomes are updated. Example patterns: ```text Transaction approved | Function sends transaction context to chargeback management provider ``` ```text Chargeback created | Function notifies risk or operations team ``` ```text Representment outcome updated | Function updates customer metadata or internal status ``` Functions are custom automation. They can support Chargeback Evidence workflows, but they should not be confused with the generated evidence package itself. --- ## Representment Tracking Generating evidence does not complete representment tracking. If a business fights a chargeback, the Chargeback representment fields should be updated to show that representment was initiated and later completed with an outcome. Conceptually: ```text Evidence generated | Evidence submitted for representment | Chargeback marked as representment initiated | Outcome received | Chargeback marked won or lost ``` This distinction matters for reporting. Without representment updates, RevCent may have the dispute and the evidence package, but it may not accurately show fight rate, pending cases, win/loss rate, or completed outcomes. --- ## What Chargeback Evidence Can Include Chargeback Evidence may include context such as: - Sale details. - Customer details. - Product sale records. - Credit card Transaction details. - Gateway transaction details. - Customer Card reference details. - Shipping and tracking details. - Tax details. - Tracking visitor details. - Fraud detection details. - Metadata. - Third-party IDs and external order context. The exact evidence available depends on the original transaction, related records, and what data was captured before the chargeback occurred. --- ## What Chargeback Evidence Does Not Do by Itself Chargeback Evidence does not automatically: - create a Chargeback record unless a separate chargeback creation step is performed; - mark representment as initiated; - submit evidence to card networks or processors; - decide whether the merchant should fight the dispute; - guarantee that representment will be won; - replace Chargeback reporting; - replace BigQuery analysis for dispute trends; - permanently store an expiring document URL. It is supporting evidence. The business or provider still needs to manage the dispute process and record representment status accurately. --- ## Chargeback Evidence and Reporting Chargeback Evidence is case-level support. Reporting is broader. Use Chargeback Evidence when reviewing or fighting a specific dispute. Use BigQuery or reporting workflows when answering questions such as: - How many chargebacks occurred last month? - Which gateways have the highest chargeback rate? - Which campaigns produce the most disputes? - Which reason codes are most common? - Which providers or representment workflows produce the best win rate? - Which customers have repeated chargeback history? Evidence packages help with individual cases. Reporting helps with patterns, prevention, and operational decisions. --- ## AI Assistant and MCP Guidance AI Assistants and MCP clients should treat Chargeback Evidence as sensitive dispute-support material. Before generating evidence, AI should understand: - Which Chargeback, Transaction, Sale, Shipping, or Fraud Detection record is the correct starting point. - Whether the business is reviewing the case or actively fighting it. - Whether the generated evidence package needs to be downloaded before expiration. - Whether representment should be updated after evidence is submitted. - Whether a third-party provider is coordinating the dispute. AI and MCP workflows should not: - invent chargeback IDs, transaction IDs, gateway transaction IDs, or case details; - assume the business wants to fight every chargeback; - claim that document generation submits evidence externally; - leave representment status unexplained after evidence is generated; - use chargeback document generation for general metrics or bulk reporting; - expose sensitive customer or payment context unnecessarily. --- ## Operational Safety Chargeback Evidence can include sensitive customer, payment, visitor, shipping, and risk data. Operationally, businesses should: - generate evidence only for legitimate review or representment needs; - confirm the correct originating sale or transaction; - download expiring document packages promptly when needed; - store downloaded evidence according to internal retention policy; - share evidence only with authorized teams or providers; - update representment tracking when a case is fought; - use reporting tools for aggregate dispute analysis instead of generating documents in bulk. Evidence quality depends on the data captured before the dispute. Strong payment, shipping, tracking, and customer records make evidence packages more useful. --- ## Common Misunderstandings ### "Chargeback Evidence is the same as a Chargeback." No. The Chargeback is the dispute item. Chargeback Evidence is supporting material for review or representment. ### "Generating evidence submits representment." No. Evidence generation packages information. Submission and representment tracking are separate workflow steps. ### "A chargeback document URL is permanent." No. Generated document URLs expire after 24 hours. ### "Evidence guarantees the chargeback will be won." No. Evidence supports the case, but the final outcome depends on the dispute, network rules, processor process, provider handling, and available proof. ### "Chargeback documents should be used for reporting." No. Use case-level documents for evidence. Use BigQuery or reporting workflows for metrics and trends. --- ## Best-Fit Businesses Chargeback Evidence is most useful for ecommerce businesses that: - receive chargebacks that may be worth fighting; - sell physical goods where delivery proof matters; - need structured purchase proof for disputes; - work with third-party chargeback mitigation providers; - want to connect disputes to transaction, sale, customer, shipping, and fraud context; - track representment outcomes and win/loss performance; - need AI or automation support for dispute review. It is less useful when the business never fights disputes, lacks usable source data, or only needs aggregate chargeback metrics. --- ## Summary Chargeback Evidence in RevCent is the supporting evidence and document-generation capability used to review or fight credit card disputes. The key concept is: ```text Chargeback = dispute item Transaction and Sale = originating payment and purchase context Chargeback Evidence = packaged supporting proof Representment fields = tracking for fight status and outcome ``` Used well, Chargeback Evidence helps businesses and chargeback mitigation providers gather the context needed for dispute response while keeping RevCent's Chargeback records accurate for operational review and reporting. --- Document Parent Directory * [Features](https://revcent.com/documentation/markdown/ecosystem/feature/index.md) - Non-technical markdown documentation for features within the RevCent ecosystem. A feature is a part of the RevCent ecosystem that a user can create and configure.