Chargeback evidence assembly across systems: a map of the records and keys that join one dispute

Short answer

Five keys reconstruct a card dispute across systems: the payment provider's dispute ID, the charge or transaction ID, the retailer's order number, the shipment tracking number and the support ticket ID. The payments platform holds the first two, order management holds the order number and tracking, the delivery tracking tool holds the scans, and the support desk holds the ticket. A case is fully joined when every hop still carries its key and the card-issuing bank's outcome is stored against the dispute.

Visual briefFull-size diagram
Five system nodes around one joined dispute case: payments platform, dispute platform, order management, delivery tracking and support desk, with the linking keys dispute ID, charge ID, order number, tracking number and ticket ID travelling along the connectors into the case.
Illustrative. Each key is held by two systems; a case is joinable when every hop still has its key.

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.

SystemRecords it holdsLinking key it sharesUsual owner
Payments platformDispute record, reason code, response deadline, outcome, funds movementDispute ID and charge IDPayments operations or finance
Dispute platform or payment provider dashboardEvidence bundle as submitted, analyst notes, submission dateDispute ID, sometimes its own case IDDisputes director
Order managementOrder lines, delivery address history, payment reference, shipmentsOrder number, charge ID, tracking numberE-commerce or operations lead
Delivery tracking toolCarrier scans, delivery confirmation, delivery photoTracking numberFulfillment manager
Support deskCustomer messages, ticket history, agent notesTicket ID, order number if the agent entered itCustomer 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.

HopFromToKey usedWhat the join adds
1Payments platformDispute platformDispute IDReason code, deadline and the evidence bundle that was sent
2Payments platformOrder managementCharge IDThe order, its lines and the delivery address
3Order managementOrder management historyUser ID and delivery addressTwo earlier undisputed orders from 140 and 300 days before, same address and device
4Order managementDelivery tracking toolTracking numberDelivery scan at the address used on the earlier orders
5Order managementSupport deskOrder numberNo ticket: the customer never contacted support
6Payments platformPayments platformDispute IDOutcome 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.

HopCommon breakWhat to note on the map
Dispute to evidence bundleDispute platform stores its own case ID onlyYears affected; whether the payment provider ID was ever stored
Dispute to orderOlder orders saved a payment token, not the charge IDYear the charge ID started being saved
Order to supportAgents paste the order number inconsistentlyRough share of tickets with an order number, as the director estimates it
Order to deliverySplit shipments, or carrier data held by a third-party toolWhether scans are kept per tracking number
Dispute to outcomeOutcome never copied back to the dispute platformWhere 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.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Is the customer email a good enough join key?

Only as a fallback. Customers often use one address to order and another to contact support, and emails are personal data that need de-identification. A ticket that stores the order number is a far better link.

What if the merchant changed dispute platforms partway through?

Note the year of the switch and whether old cases kept the processor's dispute ID. If they did, the two eras can still be joined through the payments platform; if only the old vendor's case ID survives, the join may be lost.

Do I need to see the systems to fill in the map?

No. The disputes director and the system administrators can answer every row from memory or configuration. Partners never handle the records themselves.

Sources

  1. usa.visa.com/content/dam/VCOM/regional/na/us/support-lega…
  2. docs.stripe.com/disputes/how-disputes-work
  3. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment