A surge in transactions is not the same as licensable data: a volume-versus-rights matrix that asks whose record each transaction creates

Short answer

Screen transaction growth for rights before volume. A surge in payments, orders or claims shows that records are piling up; it does not show whose they are. Split each transaction into layers (the record of the sale, the people in it, client data handled on someone else's behalf, and the company's own handling work) and ask who decides how each layer is used. The part a company can usually license is its own work around the transactions, and that part grows more slowly than the count.

Visual briefFull-size diagram
A matrix with five layers of a transaction as rows and three questions as columns; the three layers that grow with every transaction are marked client or consumer controlled, while the two slower layers of the company's own handling work and procedures are marked company controlled.
Illustrative volume-versus-rights matrix. Layers and markings follow the method on this page; no real company's records.

Volume headlines play no part in fit. The published screening asks for 50 or more full-time employees at peak, years of original documentation the company created itself, rights to license it, an authorized sponsor and relevance to a current program, and it lists personal consumer data and material that belongs to clients as usually not a fit. A transaction business can pass all of that. It rarely passes on the strength of the transactions themselves, which is why the growth-versus-suitability plot never lets volume stand in for the score.

Name the metric before you read the surge

"Transaction growth" covers several different counts, and each describes somebody's activity in a different way.

Metric as announcedWhat it countsWhose activity it mostly describes
Transactions processedPayments or messages handled for clientsThe clients' own customers
Gross volume, such as GMV or TPVMoney moving through the platformBuyers and sellers, valued in their money
Orders or order linesSales the company itself madeThe company and its business customers
Claims, tickets or cases handledWork items the company resolvedThe company's staff, and the people they served

Record every surge with its metric, period, source and date. Two figures with different metrics are not a trend. A gross-volume figure says least of all about records, because it measures other parties' money rather than the company's work. An orders figure says the most, because each order is a sale the company made and handled.

The volume-versus-rights question matrix

Take any transaction the company handles and separate it into five layers. Ask the same four questions of each.

LayerGrows one-for-one with volume?Who usually decides how it is usedUsual fit on the screening profileMetadata question for the CEO
1. The transaction record: amount, time, parties, statusYesThe client whose sale it is, when the company processes on its behalf; the company itself when the sale is its ownClient-owned material is usually not a fit; the company's own sales records can beAre these your sales, or sales you process for clients?
2. Personal data of consumers or cardholdersYesThe client, as controllerPersonal consumer data is usually not a fit; card data also falls under PCI DSSWhich systems hold consumer identities, and can they be kept apart?
3. Client business data handled for them, such as catalogs or invoicesRoughlyThe clientUsually not a fitWhich records do your client agreements say are theirs?
4. The company's handling work: exceptions, disputes, fraud reviews, routing decisions, support ticketsNo; it grows with problems, not with countThe company, subject to client contracts and privacyCan fit: original documentation of the company's own workHow many years of exception and dispute notes, in which system?
5. The company's procedures: SOPs, QA reviews, policy changes, training materialNoThe companyStrong candidate, if the company wrote itWho maintains the procedures, and since when?

Layers 1 to 3 grow with every transaction, and they are where most volume headlines live. In the EU framework, the client that decides why and how its customers' personal data is processed is the controller; a company handling that data on the client's behalf is a processor. The European Commission adds that a processor which uses the data for its own purposes becomes a controller for that use. Licensing client transaction data for AI training would be such a purpose, so client contracts and privacy law decide whether it is possible at all. Card payments carry a standard of their own: PCI DSS applies to entities that store, process or transmit cardholder data, including merchants, processors, acquirers, issuers and service providers. A payments surge widens that compliance scope. It does not widen what the company may license.

Layers 4 and 5 are the company's own work. They grow when transactions go wrong, when rules change and when the company teaches new staff how it decides, which is exactly the documented judgment the screening profile describes. For the general test of what makes records licensable, see what makes a dataset licensable.

Method note. Layers and questions were built on 2026-10-26 from the published screening profile, the program terms, the European Commission's controller and processor guidance and the PCI Security Standards Council's description of PCI DSS scope. The matrix sorts records by who controls them. It does not measure buyer demand, record quality or what any license would pay; SourceX's rights review and relevance check settle those.

A payments surge and an order surge under the same questions (Illustrative)

Illustrative. Two generic companies with invented details; no outcome is implied.

A 450-person payment processor for independent restaurants says its processed transactions tripled between 2023 and 2025. A 260-person industrial fasteners distributor founded in 1987 says its order lines rose 40% after it opened a B2B web store in 2024. Most screens would put the processor first. The matrix reads them differently.

QuestionPayment processor, transactions tripledFasteners distributor, order lines up 40%
Size at peak450 full-time employees260 full-time employees
Layers 1 to 3Nearly all of the surge is restaurants' sales and cardholder data, processed for clientsOrders are sales the distributor made; buyers are business contacts
Layers 4 and 5Chargeback dispute notes since 2016, merchant risk reviews and support ticketsQuote revisions, returns and supplier lead-time corrections in its ERP since 2009; written procedures for pricing exceptions
Rights questionsMerchant agreements, consumer personal data, PCI DSS scopeConfidentiality clauses in customer contracts and supplier price lists
Authorized pathFounder-CEO, reachable through a board memberOwner-CEO, reachable through an LP
What the matrix saysA narrow candidate: layers 4 and 5 only, if the company controls themA broader candidate: its own sales plus its handling work

The processor's number is the more impressive one, and almost none of it is the processor's to license. The distributor's number is modest, and most of what sits behind it is its own. Neither row is accepted or declined by this table; it tells you which question to ask first.

How much history sits behind the surge?

A surge compresses activity into the most recent periods, so test it with three questions before you count it as history.

  1. When did the company start handling this kind of transaction? A process with fifteen years behind it is different from a product line launched last year.
  2. Did the process exist before the surge? The distributor's web store is new, but its ERP order history runs back to 2009, so the surge adds a channel on top of fifteen years. A company whose entire volume arrived with a new product holds months of history, however large the count.
  3. Did the surge come with a new system? Records before a cutover may sit in an old platform. A documented retirement date for that platform is the one real deadline in this picture, because retired systems can take their history with them.

Rank the shortlist by controlled share, ownership and operating load

Order candidates on these keys, in this order:

  1. Controlled share. How much of the record base sits in layers 4 and 5, or in sales the company made itself, by the CEO's own rough estimate.
  2. Process history. Years the company has handled this work, not years since the surge.
  3. Ownership. A pending sale moves the decision to the buyer's CEO; a parent and its subsidiaries count as one company for the reward cap.
  4. Operating load. A team in the middle of a surge, a peak season or a platform migration has little time for a licensing review; record a date and ask after it.
RankCompany (Illustrative)Controlled shareProcess historyOwnershipOperating load
1Fasteners distributorHigh39 yearsOwner-run, settledNormal
2180-person freight claims administratorHigh in layers 4 and 514 yearsSettledPeak season ends in January
3Payment processorLow, layers 4 and 5 only10 yearsSettledMigration under way
490-person marketplace launched in 2024Low2 yearsSale announced, not closedIntegration ahead

For the portfolio side of the program, see the overview for venture platform teams, and test single companies with the company fit checker.

Where volume-first screening, and this matrix, can fail

  • Contracts can cut both ways. Some client agreements grant broad rights to use processed data, which would open layers 1 to 3; others restrict even layer 4. Only SourceX's rights review reads them.
  • Volume is not value. The matrix sorts by control, not by worth. Whether a company's handling records match a current program is checked in review.
  • Personal data runs through every layer. Dispute notes and support tickets name people too. A layer marked "company" still goes through privacy review.
  • Metrics are defined by the company. "Transactions" in one announcement and another may not count the same thing, and gross volume can rise with prices while activity is flat.
  • Substitutes may narrow demand. If AI developers find synthetic or public stand-ins for some record types, the handling layers that look strongest here could matter less.

A measurable next step. Take ten companies in your network whose growth story is transactional and fill the matrix for each from what their CEOs or relationship owners already know. Count how many have a layer 4 or 5 with at least five years of history. After a quarter, compare conversation outcomes between the high and low controlled-share groups. SourceX has not published conversion data by business model, so that comparison would be yours alone.

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 a company's matrix shows years of handling work it controls and its CEO wants a conversation, register for a partner link, confirm the basics on who qualifies and read the program terms before you submit.

Screening transaction businesses is referral work; if the question on your desk is SourceX as an investment, treat it on its own and ask for materials through the SourceX investor overview.

This article is for information only and is not an offer to sell or a solicitation of an offer to buy securities. Any offering by SourceX is made only to verified accredited investors through its offering documents.

  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 a payments company ever worth introducing?

It can be, when its own handling work has years of history it controls: dispute notes, risk reviews, support tickets and procedures. The card and consumer data at the center of its volume is usually not a fit, so describe the handling layers on their own and let SourceX's review decide what could be in scope.

Does more transaction volume mean a bigger reward for the partner?

Nothing in the program ties the reward to transaction counts. It is the greater of $50,000 plus 5% and 15% of the Actual Supplier Payout, the compensation SourceX actually pays the company under its own agreement, with no cap. Illustrative: a $400,000 actual supplier payout gives a $70,000 reward, whatever the company's volume.

Should a partner ask for a sample of transactions to show the records exist?

No. Ask at metadata level instead: which record types, roughly how many, over how many years, in which system and owned by whom. Partners never request, receive or forward records, and transaction samples often contain exactly the client and consumer data that is usually not a fit.

Sources

  1. refer.sourcex.si/who-qualifies
  2. refer.sourcex.si/terms
  3. commission.europa.eu/law/law-topic/data-protection/information-bu…
  4. pcisecuritystandards.org/standards/pci-dss
  5. sourcex.si/investors

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