Buyers of company data publish different payment terms. Some pay a set number of days after acceptance or invoice, one pays on delivery of the dataset to the buyer, one shares revenue on each sale, and Outrich Data funds payment into escrow before delivery. The table in this guide records what each buyer's own page stated on November 17, 2026.
Four things a payment term decides
Three buyers publish what they say raises or lowers an offer. See what buyers say moves the price of company data for a side by side reading.
A price tells a seller how much. Payment terms tell a seller when, on what condition and with what certainty. Two offers at the same price can differ by months and by who carries the risk in between.
Every payment term answers four things. The trigger is the event that makes money due, such as signing, delivery, acceptance or a later sale. The clock is the number of days from the trigger to payment. The form is a single payment, installments or a share of revenue. The location is where the money sits while the seller performs.
Buyers' web pages usually state one or two of the four. The contract states all of them. Treat a web page as a starting point and ask for the rest in writing.
What each buyer publishes
We read each buyer's own page on November 17, 2026. The table records what the page states about payment and nothing else. Where a page is silent on a point, the table says so. Terms change, so confirm with the buyer before relying on a row.
The table covers the same companies as our comparison of companies that buy data for AI, which also lists published ranges and minimum company sizes.
| Buyer | What its page states about payment | Trigger named | Source |
|---|---|---|---|
| micro1 | "We pay in full within 30 days of acceptance." Its FAQ says micro1 has 30 days to review and approve transferred data, then asks for an invoice and pays within 30 days of invoicing | Acceptance, then invoice | micro1 |
| Polyshares | "Net 30 to 60 once the data is approved, shared, and anonymized" | Approval, sharing and anonymization | Polyshares |
| Mercor | Wire transfer on delivery of the anonymized dataset to the buyer, which it says typically occurs within 2 to 4 weeks of the signed agreement | Delivery to the buyer | Mercor |
| DataPaid | "Typically 20 to 60 days from discovery to payment received" | Not stated | DataPaid |
| Mode | The written agreement sets the amount and payment schedule before export. Mode says it generally expects about three months from first conversation through payment | Set in the agreement | Mode |
| Troveo | The seller shares in the revenue on every sale. Terms are stated in the agreement | Each sale to a buyer | Troveo |
| Scale AI | No payment timing stated. Its FAQ says partnerships are designed so there is opportunity for recurring revenue | Not stated | Scale AI |
| Outrich Data | Payment is funded into escrow before the seller delivers and released when delivery passes the agreed checks | Acceptance checks, with funds already deposited | Data escrow |
Payment on acceptance, and what acceptance means
The most common trigger is acceptance. The seller delivers, the buyer reviews, and money becomes due once the buyer accepts. How long that takes depends on how the contract defines acceptance.
Most buyers do not publish that definition. micro1 does, in its Data License Master Terms. Section 1.3 gives it 30 business days after delivery is complete to reject data by written notice. Data not rejected in that time is deemed accepted. Early acceptance requires a written notice from its General Counsel or Chief Financial Officer. Section 3 says the seller may invoice only after acceptance. Our plain-English reading of those terms covers the detail.
Those terms show the parts every acceptance clause has. A seller comparing offers can check each part in each contract. The list below names them.
Subjective standards are the main source of delay. A test such as quality or usability depends on the reviewer. A test such as record count, schema and checksum match can be run by either side with the same result. Our guide to acceptance criteria and the acceptance criteria template show how to write tests that can be measured.
- The standard. What the data is tested against: a written specification, or the buyer's judgment of quality.
- The review period. How many days, counted in calendar or business days, and from what event.
- Deemed acceptance. Whether silence at the end of the period counts as acceptance.
- Who can accept. Whether any confirmation counts or only a notice from a named officer.
- Partial rejection. Whether the buyer can reject part and keep part, and whether a partial rejection can become a full one.
- Cure. How long the seller has to fix a rejected delivery and how many attempts it gets.
- After acceptance. Whether the buyer can still claim a refund later, and for how long.
Net terms and the invoice step
Net terms add a second clock after the trigger. Net 30 means payment is due 30 days after an invoice or another stated event. Polyshares publishes net 30 to 60, counted from the point the data is approved, shared and anonymized. Its page adds that it does not pay for a record it has not seen, so its review comes first.
Where an invoice is required, the sequence has three stages: delivery to acceptance, acceptance to invoice, and invoice to payment. micro1's FAQ describes this sequence, with up to 30 days for review and payment within 30 days of invoicing. A seller controls only the middle stage, by invoicing on the day acceptance arrives.
The practical step is to add the stages together. Ask each buyer for the longest possible time from the day delivery is complete to the day funds arrive, assuming every period runs to its limit. Put that number of days next to the price when you compare offers.
Check what the contract says about disputed amounts. Many payment clauses promise payment of undisputed amounts only. Ask how a dispute is raised, how fast it must be resolved and whether the undisputed part is still paid on time.
Payment on delivery, upfront payments and installments
Mercor's page ties payment to a different event: delivery of the anonymized dataset to the buyer, by wire. It gives a typical timing counted from the signed agreement and says the timing depends on extraction and processing. A seller would want to know which party is the buyer in that sentence and what happens if that delivery is delayed.
None of the seven buyer pages we read states that it pays any part of the price at signing. That does not mean no buyer will agree to it. It means a seller who wants a payment at signing has to ask for it in the negotiation.
Installments split the price across milestones, for example part on acceptance of a first delivery and part on each later refresh. They suit deals with ongoing deliveries. Each installment needs its own trigger and its own clock in the contract, or the later payments become hard to enforce.
How escrow changes who carries the risk
In a deal paid on acceptance, the seller delivers first. Between delivery and payment the buyer holds the data and the seller holds a promise. If the buyer rejects, disputes or delays, the seller's data has already left its systems. The seller carries the risk for the whole review and payment period.
In a deal paid at signing, the position reverses. The buyer pays first and carries the risk that the data does not match what was described. This is why few buyers offer it.
Escrow removes the need for either side to go first. The buyer deposits the price with a neutral holder when the agreement is signed. The seller delivers. The data is checked against tests both sides wrote down in advance. If it passes, the funds release to the seller. If it fails and cannot be cured, the funds return to the buyer and the data is deleted.
Escrow does not make payment faster in every case. It changes what the seller is waiting for. The seller is no longer waiting to learn whether the buyer will pay. It is waiting for a defined check to finish, with the money already set aside. When Outrich Data buys, its payment is deposited into escrow before the seller delivers, and delivery is verified against a checksum manifest. Two parties who have agreed terms elsewhere can also close through Outrich Data as the escrow company.
Escrow depends on its instructions. The release conditions, the review period, the cure period and the return of funds must match the license word for word. Our guide to data escrow explains the instructions.
What to get in writing before you deliver
Use the list below with any buyer. The data license term sheet has a row for each item so two offers can be compared line by line. The guide to AI data licensing agreements explains the clauses, and the micro1 comparison page shows one buyer's published terms next to ours. The data valuation calculator gives an illustrative range for the price itself.
- The event that makes payment due, in one sentence.
- The number of days from that event to payment, and whether they are calendar or business days.
- Whether an invoice is required and when you are allowed to send it.
- The acceptance tests, the review period and what happens if the buyer says nothing.
- The longest possible time from complete delivery to funds received.
- Where the money is during that time, and whether it is in escrow.
- What happens to delivered data if the buyer rejects or the deal ends.
- For revenue share: the percentage, the base, the reporting schedule and audit rights.
- The method of payment and who pays bank or transfer charges.
Common questions
Do AI data buyers pay upfront?
What does payment on acceptance mean?
How long does it take to get paid for company data?
Is revenue share better than a fixed fee?
How does escrow protect a seller?
Sources
- micro1, Data partnerships2026-11-17
- micro1, Data License Master Terms (last updated November 12, 2026)2026-11-17
- Scale AI, Data Partnerships2026-11-17
- Mode, company data page2026-11-17
- Polyshares, home page2026-11-17
- Polyshares, Data licensing2026-11-17
- Mercor, Data2026-11-17
- DataPaid, home page2026-11-17
- Troveo, Business data2026-11-17