What's useful
- Transaction tables: payments, refunds, chargebacks and their outcomes.
- Order and fulfilment data: orders, inventory movements and shipments.
- Fraud and risk decisions, with what happened afterwards.
- Schemas and documentation that explain what the tables mean.
Several years of history from a payments or commerce business is the core of this listing.
What qualifies
The listing doesn't set a size limit. What matters is holding years of transaction, order, inventory or shipment tables.
What to check first
- Card data. Full card numbers and other cardholder data covered by PCI DSS must never be shared. Make sure any export excludes them.
- Personal data. Transactions linked to individuals are personal data under UK GDPR, and spending patterns can reveal sensitive details. They need removing, aggregating or properly protecting.
- Whose data it is. If you process payments or orders on behalf of merchants, your contracts with them, and your role as their processor, may limit what you can do with their data.
- Regulatory obligations. Check the scope against your FCA permissions and any confidentiality duties to partner banks and schemes.
What it's worth
Mercor lists potential company earnings of $80k–$900k for payments and fintech companies, depending on what's in scope. That is Mercor's own figure, not a promise or guarantee from us.
Would aggregated data be enough?
Sometimes. Row-level data is usually more valuable, but aggregated or de-identified tables can reduce the risk. Raise it during scoping.
We run an online shop rather than a fintech. Does this apply?
It can. The listing covers commerce businesses with years of order, inventory or shipment data too.