This record chain is part of the dispute-to-evidence-packet records guide. It maps identifiers. To score how complete a company's dispute records are, use the completeness checklist; for what one system's export loses, see the missing context case.
The chain from dispute notice to outcome
Read the table top to bottom as one product-not-received dispute travels through a retailer.
| Step | Record | System | Key it carries | Key it must hand on |
|---|---|---|---|---|
| 1. Dispute arrives | Dispute notice with reason code and deadline | Payments platform or chargeback tool | Dispute ID, charge ID | Order number from the charge metadata |
| 2. Original order | Order with items, address and payment | Order system | Order 52071 | Tracking number for the first shipment |
| 3. First shipment | Shipment and carrier events | Warehouse system and carrier | Order 52071, tracking T1 | Return-to-sender event, if any |
| 4. Customer contact | Case with contact history and resolution | CRM | Case number, order 52071 | Replacement order number |
| 5. Replacement order | New order created to settle the complaint | Order system | Order 52244 | Tracking number for the replacement |
| 6. Replacement delivery | Shipment, delivery scan, address, signature | Warehouse system and carrier | Order 52244, tracking T2 | Delivery proof for the packet |
| 7. Evidence packet | Submitted response with exhibits | Payments platform | Dispute ID | Outcome |
| 8. Outcome | Won, lost or accepted | Payments platform | Dispute ID | Closes the chain |
Most handoffs carry a key by design. Step 4 to step 5 is the exception: the CRM case usually names the replacement order in free text, and the replacement order often carries no reference back to 52071 at all.
Where the chain breaks: the replacement order
Illustrative. A fictional 180-person outdoor gear retailer sends order 52071. The parcel is returned to the warehouse undelivered. The customer calls; the agent opens a case and creates replacement order 52244, which arrives with a signature. Weeks later the customer's bank files a product-not-received dispute against the original charge.
Every record exists. The dispute points to 52071. The first tracking number, T1, shows a return. The delivery proof, T2, belongs to 52244. Only the agent's note in the CRM case says that 52244 replaced 52071.
Automation can make the snap worse. Stripe describes retrieving fulfillment history, including delivery status, timestamps and location, from supported carriers when given a carrier and a tracking number. A tool that looks up tracking by the disputed order's number fetches T1, the shipment that came back, and never sees T2. The packet then shows a failed delivery for a customer who did receive the goods.
The timing leaves no room to fix it later. Stripe's documentation says a business gets one opportunity to submit a response, cannot edit it afterward, and usually has 7 to 21 days depending on the card network. Each evidence type accepts one file, so the replacement proof and the explanation that ties it to 52071 have to travel together.
Repairing the link before the packet is built
The repair is a field, not a habit: a "replaces order" reference stored on the replacement order, pointing to the original. With it, step 5 hands its key back to step 2 by design, a lookup by the disputed order can find T2, and the packet can be assembled in the order Stripe advises: chronologically, grouped by type with a short explanation of each item, and for physical goods with proof of shipment and delivery that includes the full delivery address.
| Link | Without the field | With the field |
|---|---|---|
| Original order to replacement | Join depends on reading a case note | Join is a stored reference |
| Dispute to delivery proof | Tracking lookup finds the returned parcel | Lookup follows the reference to the delivered parcel |
| Packet explanation | Written by hand, if at all | Drawn from two linked records |
| Later review of the history | Needs free text to rebuild | Joins by keys alone |
For an introducer, the repair matters as history. A company that added such a field in a given year has two eras: before it, replacement disputes depend on notes; after it, they join cleanly. Both are worth describing. Ask when it changed.
Illustrative: describing a retailer's chain at metadata level
The same fictional retailer described its key coverage to a partner without showing a single record:
| Link | Key present | Since | Strength |
|---|---|---|---|
| Dispute to order | Order number in charge metadata | 2018 | Strong |
| Order to first shipment | Tracking stored on the order | 2017 | Strong |
| Order to CRM case | Order number field on cases | 2019 | Strong |
| Original to replacement | Free text in case notes; field added in 2023 | 2023 | Weak before, strong after |
| Packet to outcome | Outcome recorded on the dispute | 2018 | Strong |
| Saved packets | Shared drive by dispute ID | 2020 | Earlier packets unknown |
That is a complete description for an introduction: keys, years and the one weak link, with nothing from inside a case, an address or a packet. For how chargeback records are described as a data type, see chargeback representment records; for the business-to-business version, see accounts receivable dispute resolution.
Who owns each key and who signs off
The payments team owns dispute IDs and packets. Customer service owns the CRM case. Operations owns orders, shipments and the warehouse system. A licensing discussion normally needs the CFO, COO or owner, because the chain crosses all three and contains customer details. Distributors with similar chains can start from wholesale distribution data; if anyone contests who owns the records, read licensing data subject to an ownership dispute.
Confirm the company baseline: 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license, and an authorized contact. 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. Sign the Channel Partner Agreement before you submit.
What stays unknown until SourceX reviews it under the company's own agreement: whether processor, carrier and privacy terms allow use, how the records would be de-identified, and whether a buyer wants them. You never see or forward a packet, case note or address.
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 a client can name the key at each step, including how a replacement order points back to the original, and an officer will take the call, register as a partner, check who qualifies, and read the terms before you submit.