This template is part of the chargeback evidence assembly guide. Copy the block, fill it in on a call with the disputes director, and check it against the include-and-leave-out list before it goes anywhere.
The fill-in handoff, ready to copy
Paste this into an email. Replace each bracket with a short answer, or write "unknown".
- Company: [what it sells, channel, full-time staff at peak]
- Business task: assembling evidence to answer card disputes, from claim to issuer decision
- Systems: [dispute platform or processor dashboard; payments platform; order management; shipping platform; support desk]
- Years covered: [first and last year per system; year of any vendor switch]
- Volume: [approximate disputes per year or in total, and how that was counted]
- Outcomes kept: [won and lost, or wins only; where outcomes are stored]
- Reason mix: [roughly which dispute reasons dominate: fraud, not received, not as described]
- Record owner: [disputes director, payments operations, support lead]
- Who can authorize: [the CEO's name, plus counsel]
- Open question: [the rights or linkage question nobody can answer yet]
- Documented event: [renewal, vendor switch or contract end, with its source]
Eleven lines. If the director cannot answer a line from memory or a report total, it stays "unknown". That is more useful to SourceX than a guess.
What to include, and what stays out
The brief describes the history without carrying any of it. Use this list as a filter on every line.
| Include | Leave out |
|---|---|
| The business task in one line | Any dispute file, packet or screenshot |
| Record classes: packets, order histories, delivery records, chats, outcomes | Customer names, emails, addresses or message text |
| Approximate coverage in years and dispute counts (Illustrative or counted) | Card numbers, payment tokens or bank details |
| Systems in plain text | Win rates the company cannot document |
| Whether lost cases were kept | Any estimate of what the history is worth |
| The open question, stated plainly | Pressure on timing the contract does not support |
| The CEO, who can authorize, with counsel | A system admin as the only contact |
Customer messages deserve the strictest line. Stripe's evidence object has a customer communication field for emails, texts or a written account of calls, so packets routinely contain them. The brief may say that packets include customer communication; it never quotes one.
Filling the harder lines
Volume. The payments platform shows dispute totals by month or year without opening a case. Ask for those totals, then write a range and its source.
Outcomes kept. Stripe's documentation says a company usually has 7 to 21 days to respond and the issuer usually takes 60 to 75 days to decide. Because the decision arrives long after the packet, some platforms close the case before the outcome lands. Ask where outcomes are recorded and whether lost cases were ever purged.
Reason mix. It changes what the history contains. Some reasons rest on account and device history, others on carrier scans and customer messages. A rough split, as the director remembers it, tells SourceX which record classes matter most.
Open question. For many companies it is whether outcomes were always written back to the case, or whether the support desk stored order numbers before a certain year. The system map helps phrase it.
Documented event. Only a date with a source: the renewal notice deadline in the contract, a planned vendor switch. The retention timeline explains which date matters most.
One completed handoff (Illustrative)
A fictional 430-person online pet supplies company, written for this page. The values are invented.
| Line | Illustrative entry |
|---|---|
| Company | Online pet supplies retailer, direct-to-consumer, 430 full-time staff at peak |
| Business task | Assembling evidence to answer card disputes, from claim to issuer decision |
| Systems | Dispute platform since year two; payments platform; order management; shipping platform; support desk |
| Years covered | Six years of disputes; processor dashboard only in year one |
| Volume | About 4,000 disputes in total, from the payments platform's annual totals |
| Outcomes kept | Won and lost, stored on the payments platform; written back to the dispute platform from year three |
| Reason mix | Mostly not received and fraud; a smaller share not as described |
| Record owner | Disputes director for packets and notes; support lead for chats |
| Who can authorize | CEO, with the CFO and general counsel; disputes director copied |
| Open question | Whether support tickets before year three stored order numbers |
| Documented event | Dispute platform renewal notice deadline January 15, per the current contract |
The CEO reading this knows what exists, how far back it goes, who is responsible and what is unresolved. Nothing in it is a customer record.
Where the brief goes next
The CEO decides whether the company applies. If it does, SourceX reviews record classes, rights and qualification. Buyer interest, how processor, carrier and vendor terms affect rights, the de-identification customer messages need, and whether an offer follows all stay unknown until then. The who-can-say-yes tree shows who else to involve before sending.
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. Sign the Channel Partner Agreement before submitting; the first valid introduction within the 90-day window is credited when the company submits a verified application. Reductions in the supplier payout reduce the reward proportionately, as referral fee clawback explains.
The client opportunity brief generator can turn the lines into a forwardable note, the warm introduction brief shows how to frame it, and why AI companies pay for data answers the owner who asks why outcome-labeled cases matter.
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.
When the handoff is filled and every line passes the include-and-leave-out filter, register as a partner, confirm the company on who qualifies and read the program terms before the disputes director forwards it.