This system map is part of the chargeback evidence assembly guide. It is for payments operations consultants who need to describe, without touching a file, whether a retailer's dispute history can still be put back together case by case.
Five systems, one dispute: the map
Each system holds one slice of a dispute and knows at least one key that points to the next. The table is the map in rows.
| System | Records it holds | Linking key it shares | Usual owner |
|---|---|---|---|
| Payments platform | Dispute record, reason code, response deadline, outcome, funds movement | Dispute ID and charge ID | Payments operations or finance |
| Dispute platform or payment provider dashboard | Evidence bundle as submitted, analyst notes, submission date | Dispute ID, sometimes its own case ID | Disputes director |
| Order management | Order lines, delivery address history, payment reference, shipments | Order number, charge ID, tracking number | E-commerce or operations lead |
| Delivery tracking tool | Carrier scans, delivery confirmation, delivery photo | Tracking number | Fulfillment manager |
| Support desk | Customer messages, ticket history, agent notes | Ticket ID, order number if the agent entered it | Customer service director |
The evidence bundle sent to the bank is where these systems meet once, under a deadline. The map shows whether they can meet again years later, without anyone rebuilding the bundle by hand.
The keys that carry a case from system to system
Dispute ID. Issued by the payment provider when the card dispute is created. The payments platform treats it as the primary key. A separate dispute platform may store it, or may store only its own case number; ask which.
Charge ID. Ties the dispute to the payment. Order management usually saves it at checkout, but older orders sometimes kept only a payment token, so the join from dispute to order breaks for those years.
Order number. The retailer's own key. It links payment, shipments and, when agents type it in, support tickets. Inconsistent entry in the support desk is the most common weak link.
Tracking number. Links an order to carrier scans. Split shipments carry several numbers, so one order may map to more than one delivery record.
Ticket ID. The support desk's key. It connects to the order only if the ticket stores the order number or the agent linked the two.
Account and device data. One card network's rule turns these fields into a key of their own. Under Visa's March 2023 Compelling Evidence 3.0 guidance for fraud disputes involving ordinary card-absent purchases, a merchant can support its response by linking the disputed purchase to two earlier purchases at the same merchant, processed 120 to 365 days before the dispute processing date, with no fraud activity. At least two of customer account or login ID, IP address, delivery address and device ID or fingerprint must match between the historical and disputed purchases, including IP address or device ID or fingerprint. A prior non-fraud dispute does not by itself disqualify a historical transaction. So the account and device history acts as a sixth key. A retailer that kept those fields linkable can still trace its past answers to such claims.
One fully joined case (Illustrative)
A fictional 520-person home goods retailer, written for this page. A card-absent fraud dispute on a $240 order. The table follows the keys hop by hop.
| Hop | From | To | Key used | What the join adds |
|---|---|---|---|---|
| 1 | Payments platform | Dispute platform | Dispute ID | Reason code, deadline and the evidence bundle that was sent |
| 2 | Payments platform | Order management | Charge ID | The order, its lines and the delivery address |
| 3 | Order management | Order management history | User ID and delivery address | Two earlier undisputed orders from 140 and 300 days before, same address and device |
| 4 | Order management | Delivery tracking tool | Tracking number | Delivery scan at the address used on the earlier orders |
| 5 | Order management | Support desk | Order number | No ticket: the customer never contacted support |
| 6 | Payments platform | Payments platform | Dispute ID | Outcome recorded as won, with the decision date |
Every hop found its key, so the case is fully joined: the claim, the account history that answered it, the delivery record, the absence of any support contact, the evidence bundle and the card-issuing bank's decision. Stripe's guidance puts the response window at usually 7 to 21 days and the card-issuing bank's decision at 60 to 75 days, so hop 6 often lands long after the dispute platform has closed the case. Whether the outcome was written back is a question worth asking separately.
Where joins break, and what to note instead
Most retailers can join some years and not others. The gaps are predictable.
| Hop | Common break | What to note on the map |
|---|---|---|
| Dispute to evidence bundle | Dispute platform stores its own case ID only | Years affected; whether the payment provider ID was ever stored |
| Dispute to order | Older orders saved a payment token, not the charge ID | Year the charge ID started being saved |
| Order to support | Agents paste the order number inconsistently | Rough share of tickets with an order number, as the director estimates it |
| Order to delivery | Split shipments, or carrier data held by a third-party tool | Whether scans are kept per tracking number |
| Dispute to outcome | Outcome never copied back to the dispute platform | Where outcomes live and for which years |
The delivery side of the chain is covered in proof of delivery disputes. If the order system is an ERP the retailer is leaving, NetSuite data after cancellation explains what to ask before access ends, and preserving chargeback evidence assembly records puts those dates on a timeline.
Questions for the disputes director
Ask these at metadata level, then stop. Do not request exports, evidence bundles or sample cases.
- Which systems in the table does the company use, and since which year?
- Which keys does each system store, and when did that start?
- Are outcomes stored against the dispute, won and lost, for every year?
- Who owns each system, and who could authorize a licensing discussion?
The authority question has its own decision tree. The introduced company needs 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. What stays unknown until SourceX reviews it: buyer interest, how payment provider and carrier terms affect rights, the de-identification customer messages need, and whether an offer follows. Why AI companies pay for data explains why joined, outcome-labeled cases matter, and chargeback representment records describes the finished response file.
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 the map shows a retailer can still join dispute, order, delivery, support and outcome records for several years, register as a partner, check the company against who qualifies and read the program terms before you introduce the disputes director.