This decision tree is part of the chargeback evidence assembly guide. It answers one question for payments operations consultants: who can say yes to a conversation about a business's dispute history?
Three kinds of ownership inside one dispute file
A single dispute file mixes records the business owns outright with records it holds under someone else's terms. Sort them before you sort people.
| Record in the file | Whose it is | Why it matters for authority |
|---|---|---|
| Order history, analyst notes, the response file as assembled | The business's own work | The CEO can authorize discussing it |
| Issuer decision and outcome | The business's record of a third-party decision | Usually the business's to discuss; counsel confirms |
| Customer messages and chat transcripts | Held by the business, about identifiable people | Needs privacy review and de-identification first |
| Carrier scans and delivery photos | Created by the carrier, copied to the business | Carrier terms may govern reuse |
| Processor and dispute vendor data | Created in a third party's system | Processor or vendor agreements may govern reuse |
Stripe's evidence fields show how mixed a response file is: shipping documentation and tracking number sit beside a customer communication field for emails, texts or a written account of calls. Stripe also forwards the response file to the card-issuing bank immediately, with no edits afterward, so the submitted file is a fixed record. It is still a mix of owners.
Walk the tree: from disputes director to signer
Work these questions with the disputes director, in order. Each answer moves the introduction one step.
- Did the business keep closed dispute files, won and lost? If only open cases survive, there is little to introduce. If closed files exist, continue.
- Who runs dispute operations day to day? The disputes director or head of payments operations. This person convenes.
- Who owns card disputes as a business line? Usually the CFO, because disputes are a loss and a fee line. Sometimes the COO. In an owner-led business, the owner. Name a person; they often prepare the case, and the CEO authorizes it.
- Are dispute handling or alerts outsourced? If a vendor assembled response files, its contract may cover what it created. Mark it for counsel.
- Do files include customer messages? Almost always. Mark them for the privacy lead and counsel. Where EU law applies, the GDPR treats information relating to an identifiable person as personal data, and a chat transcript tied to an order fits.
- Does a parent, sponsor or board need to consent? If the business is a subsidiary, referring a subsidiary with its own processes explains how authority can sit at two levels.
The lit path in the graphic ends at the CEO and counsel together. That pair is the introduction.
Records that need privacy, processor or carrier review
These branches leave the main path and wait for counsel. Note them in the handoff and move on.
| Branch | The question | Who answers | Typical handling |
|---|---|---|---|
| Customer messages | Can conversations be used at all, and in what form? | Privacy lead and counsel | De-identified or excluded |
| Names, emails, addresses on orders | Personal data in every record | Privacy lead and counsel | Removed or pseudonymized |
| Card and payment details | Highly sensitive payment data | Payments operations and counsel | Excluded |
| Carrier scans and photos | Do carrier terms allow reuse? | Counsel | Often reduced to a delivery status and date |
| Dispute vendor case data | Does the vendor contract cover reuse? | Counsel with the disputes director | Depends on the agreement |
None of these ends the conversation. They decide scope, which is the subject of why data rights matter.
Access is not authority: who can export but cannot agree
Several people can produce dispute records in minutes. None of them can agree to license them.
| Role | What they can do | Why it is not authority |
|---|---|---|
| Support desk admin | Export every chat and ticket | Holds the tool, not the right to the content |
| Payments platform admin | Pull dispute lists and outcomes | Account access is delegated for operations |
| Dispute analyst | Open any response file | Works the cases; does not decide on company assets |
| Outside consultant (you) | Describe systems and years | Not an employee or officer of the business |
That is why the tree routes through the director to the CEO. A partner who asks the support admin for "a sample" has skipped the tree and handled records that carry customer data. Partners stay at metadata level: record classes, years, systems and owners.
Open until SourceX's rights review
After the CEO agrees to talk, these questions remain, and only SourceX's review answers them:
- Rights: which record classes and years the business can license after privacy, processor, carrier and vendor checks.
- Preparation: how much de-identification customer messages and order records need.
- Demand: whether any buyer wants dispute assembly history when SourceX reviews it.
- Terms: whether an offer follows, and its schedule.
The introduced company needs 50+ full-time employees at peak (contractors excluded; outsourced dispute agents do not count), 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, and one partner is credited per company.
The system map helps the director describe which systems hold what, and the referral brief template turns the tree's answers into a forwardable page. If the CFO is fractional, fractional CFOs for e-commerce brands covers that relationship, and the chargeback representment records page describes the finished 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.
Once the disputes director has agreed to bring in the CEO, who can say yes, and flagged the customer, carrier and vendor branches, register as a partner, confirm the business on who qualifies and read the program terms before making the introduction.