# Chargeback evidence packet records | SourceX

Canonical: https://refer.sourcex.si/guides/chain-dispute-to-evidence-packet
Last updated: 2026-11-04

A referral partner can describe a company's dispute-to-evidence-packet history from metadata alone: where card disputes are received, which CRM holds the customer's contact history, which warehouse or carrier system holds shipping and delivery proof, how many disputes exist over how many years, which order or case number links them, and who assembles each response. The case to test is a replacement shipment, because its delivery proof carries a different order number from the disputed charge.

## The business task: answer a chargeback with proof that holds together

A cardholder tells their bank they never got what they paid for, the bank pulls the money back, and the seller has one chance to answer. For an online seller or subscription business, those reversals add up to lost revenue, fees and, past a threshold, trouble with the card networks. Winning depends less on being right than on showing it clearly and on time. Stripe's documentation describes the constraints: the response window is typically 7 to 21 days depending on the card network, the merchant gets one submission that cannot be edited afterward, and each evidence type accepts one file. The same guidance advises arranging evidence chronologically, grouping it by type with short explanations, and, for physical goods, including proof of shipment and delivery with the full delivery address.

Building the response pulls from three places. The processor or a dedicated tool holds the reason code and deadline. The CRM holds the buyer's contact history: complaints, requests for a new item, promises made. Fulfillment records hold what left the building, when and to where. The response is the one moment those three records sit side by side, and the win or loss tells you whether the story they told was convincing.

Over a few years, those decisions form a rare record of judgment under a deadline: which cases a team chose to contest and which it simply refunded, what it believed separated genuine fraud from a confused buyer, and which kinds of proof persuaded issuers. That reasoning lives in internal notes and spreadsheets, not in any public source.

## What metadata can a referral partner collect about dispute-to-evidence-packet without reading private content?

Answers to a short set of questions, written down in your own words. You never need a submitted file, a screenshot or a customer record.

### Eight questions and what a useful answer sounds like (Illustrative answers)

1. **Where do disputes arrive?** "Our payments processor's dashboard; a dedicated dispute tool since 2021."
2. **How many, over how long?** "Roughly 2,000 disputes a year, back to 2017."
3. **Where is the customer's history?** "A CRM with cases and call notes from 2018."
4. **Where is delivery proof?** "The warehouse system for what shipped, plus carrier tracking for each box."
5. **What links them?** "The order number, and for replacements, a note in the CRM case."
6. **Are past responses kept?** "Since 2020, saved in a shared drive by case ID, with the outcome in a spreadsheet."
7. **Who builds responses, and who owns each system?** "A two-person payments team; customer service owns the CRM; operations owns the warehouse system."
8. **What is unknown?** "Whether pre-2020 responses survive, and how many second shipments lack a CRM note."

Notice what is missing: names, addresses, order values and response contents. Counts, years, systems, owners and unknowns are enough. For how these records are described as a data type, see [representment records](/data-types/chargeback-representment-records); for the B2B equivalent, see [accounts receivable dispute resolution](/data-types/accounts-receivable-dispute-resolution-process).

## What breaks when proof covers a replacement order instead of the original

The proof is real and still proves the wrong thing. The graphic on this page shows an Illustrative case. A customer disputes a $1,180 charge on order 48113 under Visa reason 13.1, which falls in the product not received category. The original shipment was returned to the warehouse on January 14. Customer service sent a replacement as order 48390, and that box has a signed delivery. The payments team attaches the signed delivery to the response, but it carries order number 48390, not 48113. Only CRM case 7781 records that the two orders are the same purchase.

If the case note is missing, the response shows a delivery for an order nobody disputed. If it is present, the second shipment explains everything, provided the analyst who built the response included it. Because the submission is final, that judgment is recorded once and cannot be corrected.

For the metadata packet, the replacement case reduces to three countable facts:

| Question | Illustrative answer | Owner |
|---|---|---|
| How are replacement orders numbered? | New order number, with the original in a CRM case note | Customer service lead |
| Roughly what share of disputes involve a replacement? | Unknown; estimated at under one in ten | Payments team |
| Are packet outcomes recorded next to the packet? | Win or loss in a spreadsheet since 2020 | Payments team |

An honest "unknown" in the second row is a useful answer. SourceX's review can measure the share later, under the company's own agreement, without the partner seeing a packet.

## Who can authorize a discussion, and what stays unknown

Dispute records span payments, customer service and operations, so the sponsor is usually the CFO, COO or owner rather than the payments specialist who builds packets.

Before you introduce, confirm:

- The company has 50+ full-time employees at peak, contractors excluded, and a documented operating history.
- The company has the right to license the records. Payment processor terms, carrier agreements and customer privacy notices can all limit reuse, which SourceX reviews; if ownership of the records is contested, read [licensing data subject to an ownership dispute](/questions/license-data-subject-to-ownership-dispute).
- A named decision-maker will take a first call.
- Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

What stays unknown until SourceX reviews it: whether the records can be de-identified to a buyer's standard, which years and dispute types a buyer would want, what card network and processor rules allow, and what the company would be paid. You never handle or forward raw records. For retailers, [identifying ecommerce operating workflows](/guides/how-to-identify-ecommerce-operating-workflows) and the [ecommerce industry page](/industries/ecommerce) cover related records; investors can add the questions above to a [portfolio review checklist](/resources/a-data-opportunity-handoff-checklist-for-a-portfolio-review). The [systems hub](/systems) lists other record locations.

## Go deeper on dispute-to-evidence-packet records

- [How chargeback, CRM and warehouse records link end to end](/guides/dispute-to-evidence-packet-record-linkage): a record-chain table of each step, its record, its key and its system.
- [Dispute-to-evidence-packet completeness checklist](/resources/dispute-to-evidence-packet-completeness-checklist): a pass, partial or fail scorecard for judging whether the records are complete enough to discuss.
- [What a single-system dispute export leaves out](/guides/dispute-to-evidence-packet-missing-context): one Illustrative case read before and after its surrounding context is added.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If your client can answer the replacement-order question and name who owns payments, the CRM and the warehouse, [register as a partner](/register), check [who qualifies](/who-qualifies) and read the [program terms](/terms) before you introduce them.

## Sources

- https://refer.sourcex.si/terms
- https://docs.stripe.com/disputes/responding
- https://docs.stripe.com/disputes/best-practices
- https://docs.stripe.com/disputes/reason-codes-defense-requirements
