Who can say yes to licensing chargeback evidence assembly records? A decision tree for payments consultants

Short answer

Introduce the CEO, usually with general counsel, and ask the disputes director or head of payments operations to convene. The director knows which systems built the response files and where outcomes are stored, but rarely has authority to discuss licensing company records. The support desk admin who can export every chat has access, not authority. Customer messages need privacy review, carrier and processor data may carry third-party terms, and what is in scope stays unknown until SourceX's rights review.

Visual briefFull-size diagram
A left-to-right approval tree: support desk admin, payments platform admin and dispute analyst can export but not agree; the disputes director convenes; branches for customer messages and carrier or processor data go to counsel; the lit path ends at the CEO with general counsel.
The lit path is the introduction. Orange branches are records counsel reviews before anything is in scope.

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 fileWhose it isWhy it matters for authority
Order history, analyst notes, the response file as assembledThe business's own workThe CEO can authorize discussing it
Issuer decision and outcomeThe business's record of a third-party decisionUsually the business's to discuss; counsel confirms
Customer messages and chat transcriptsHeld by the business, about identifiable peopleNeeds privacy review and de-identification first
Carrier scans and delivery photosCreated by the carrier, copied to the businessCarrier terms may govern reuse
Processor and dispute vendor dataCreated in a third party's systemProcessor 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.

  1. 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.
  2. Who runs dispute operations day to day? The disputes director or head of payments operations. This person convenes.
  3. 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.
  4. Are dispute handling or alerts outsourced? If a vendor assembled response files, its contract may cover what it created. Mark it for counsel.
  5. 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.
  6. 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.

BranchThe questionWho answersTypical handling
Customer messagesCan conversations be used at all, and in what form?Privacy lead and counselDe-identified or excluded
Names, emails, addresses on ordersPersonal data in every recordPrivacy lead and counselRemoved or pseudonymized
Card and payment detailsHighly sensitive payment dataPayments operations and counselExcluded
Carrier scans and photosDo carrier terms allow reuse?CounselOften reduced to a delivery status and date
Dispute vendor case dataDoes the vendor contract cover reuse?Counsel with the disputes directorDepends 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.

RoleWhat they can doWhy it is not authority
Support desk adminExport every chat and ticketHolds the tool, not the right to the content
Payments platform adminPull dispute lists and outcomesAccount access is delegated for operations
Dispute analystOpen any response fileWorks the cases; does not decide on company assets
Outside consultant (you)Describe systems and yearsNot 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.

  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

The merchant outsources dispute handling to a vendor. Who do I introduce?

Still the merchant. The vendor holds copies and may have contract terms over its own work product, but the merchant's CEO is the one who can authorize a discussion. Note the vendor as a branch for counsel.

Is the CFO always the signer?

No. The CEO signs. Because chargebacks sit with finance, the CFO often prepares the case, and in some merchants the COO owns payments operations. In owner-led businesses the owner, as CEO, signs.

Can I mention that lost cases are useful too?

Yes. Lost disputes, with the packet that was sent and the decision, show what did not persuade. That belongs in the conversation with the director, not in any claim about value.

Sources

  1. refer.sourcex.si/terms
  2. docs.stripe.com/disputes/api
  3. docs.stripe.com/disputes/responding
  4. eur-lex.europa.eu/eli/reg/2016/679/oj/eng

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