# Neobank Paid $375,000 to License Its Data: Case Study

> A neobank was paid $375,000 to license its company records. What a digital bank holds, what buyers publish and the privacy rules to check first.

Canonical: https://origindatapartners.com/case-studies/neobank-data-license-375000
By: Origin Data Partners
Status: Published
Published: 2026-11-12
Updated: 2026-11-12
Sources checked: 2026-11-12

## Quick answer

A neobank was paid $375,000 for licensing its company records in a deal Origin helped place. This is one outcome, not a forecast: price depends on the records, the rights held, demand and the agreed scope. Origin does not publish the record types in this deal, and names stay private.

## Key points

- Payment: $375,000, for licensing a neobank’s company records.
- A neobank holds both financial records and software records: code, tickets and product documents.
- Gramm-Leach-Bliley limits disclosure of customers’ nonpublic personal information; blind data without identifiers is excluded under Regulation P.
- Published programs list ranges from $100K up to $3M+ and $4M+.

## Deal facts

These are deals Origin helped place. Company and buyer names stay private, and each is an individual outcome, not a forecast for another company: what a buyer pays depends on the records, rights, demand and agreed scope. See [all case studies](https://origindatapartners.com/case-studies).

- Company type: Neobank
- Records licensed: Company operating records (record types not published)
- Amount paid: $375,000


## What records did the neobank license?

The deal covered the company’s operating records. Origin does not publish which record types were included, so this page does not list them. The table below is general context about what a digital bank or fintech keeps.

A neobank is both a financial firm and a software company. Alongside transaction and account histories, it usually keeps code repositories, issue trackers, product specifications, customer support tickets and compliance procedures.

| Record type a neobank may hold | What it shows an AI model | What must be removed first |
| --- | --- | --- |
| Transaction and account histories | How money moves and where exceptions occur | Account numbers, names, addresses and other identifiers |
| Support tickets and chat | How customer problems are diagnosed and resolved | Customer identities, contact details, account references |
| Code, issues and pull requests | How financial software is built and fixed | Secrets and keys; customer data in test fixtures |
| Compliance and onboarding procedures | How a regulated process runs step by step | Embedded customer examples |
| Product specs and decision logs | How product decisions are made and recorded | Partner confidential information |


## What do AI companies do with neobank records?

They use them to train and evaluate models that work inside real financial and software processes. [Mercor](https://www.mercor.com/data/) says “Frontier AI models are increasingly being trained to work inside companies, navigating real tools, workflows, and decisions,” and lists “Finance & Insurance” and GitHub repositories among the data it takes in.

Support threads linked to the code change that fixed the problem, or a flagged transaction linked to the review note, show cause and effect. See [licensing transaction data for AI training](https://origindatapartners.com/guides/license-transaction-data-ai-training) and [selling source code to AI companies](https://origindatapartners.com/guides/sell-source-code-ai-training).


## How much is a neobank’s data worth?

In this deal, a neobank was paid $375,000. That is one outcome; Origin does not publish the scope, exclusivity or terms behind it.

Published company-data programs list the ranges below. None publishes a figure specific to neobanks or fintechs.

| Published program | What it says it pays companies | Who it says it is looking for |
| --- | --- | --- |
| micro1 Enterprise Data Partnerships | $100K-500K for qualified partnerships; $500K-3M for large-scale operational datasets; $3M+ for highly unique proprietary data | Established companies with 30+ full-time employees and substantial historical operational data, primarily in English |
| Handshake AI company data licensing | $100K to $4M+ payouts; its estimate is "indicative" and "not an offer" | Companies with 20+ full-time employees and 3+ years in operation |
| Mercor data program | No dollar range published; compensation is based on data volume, the tools connected and the depth of the data | Lists “Finance & Insurance” among target industries: “Statements, underwriting files, claims” |

Figures as published on 12 November 2026 by [micro1](https://origindatapartners.com/guides/micro1-company-data-partnerships), [Handshake AI](https://joinhandshake.com/ai/data-partnerships/license/) and [Mercor](https://www.mercor.com/data/). They are program ranges, not quotes for any company.

Origin Data Partners works with companies that own data and helps get it bought. We are independent of the services on this page, and a buyer may pay us when a deal closes ([how Origin is paid](https://origindatapartners.com/referral-disclosure)). [See what your data is worth](https://origindatapartners.com/check-fit).


## Can a small fintech sell its data?

Programs publish their own floors. [Handshake AI](https://joinhandshake.com/ai/data-partnerships/license/) looks for “20+ full time employees & 3+ years in operation”; [micro1](https://origindatapartners.com/guides/micro1-company-data-partnerships) looks for “30+ full-time employees.” Origin does not publish this neobank’s headcount.

Many fintechs rely on a partner bank. The bank partnership agreement may say who controls customer data, so read it before describing any records outside the company. See [data licensing for software companies](https://origindatapartners.com/who-we-help/software-companies).


## What had to be removed or checked first?

Origin does not publish the checks made in this deal. For any neobank, start with privacy law. Under the [Gramm-Leach-Bliley Act](https://www.law.cornell.edu/uscode/text/15/6802), “a financial institution may not, directly or through any affiliate, disclose to a nonaffiliated third party any nonpublic personal information” unless the law’s conditions or an exception are met. [Regulation P](https://www.ecfr.gov/current/title-12/chapter-X/part-1016/section-1016.3) excludes “blind data that does not contain personal identifiers such as account numbers, names, or addresses.”

Then check contracts: the partner bank agreement, card network and processor terms, and vendor agreements can each limit what data you may use or share. Remove secrets from code before anyone sees it. Decide whether the license is exclusive; see [exclusive vs non-exclusive data licenses](https://origindatapartners.com/guides/exclusive-vs-non-exclusive-data-license).


## How does the process work?

A neobank can start at category level: which kinds of records exist, for how many years, and which contracts touch them. No customer data is shared to begin.

Start with a company overview. Origin helps organize the record categories, open questions, and a possible next step in a Company Licensing Brief. Your company separately approves any named introduction, evaluation access, and license. No files or system connections are required to begin.

| Step | What happens |
| --- | --- |
| 1. Describe the company | Start with your company name, website, and contact details. Add your industry, team size, country, and the types of records your business has. |
| 2. Talk through the opportunity | Origin follows up to understand the business, the records you describe, and the question you want to explore. Together we organize a Company Licensing Brief: categories, questions to resolve, unknowns, and a possible next step. |
| 3. Explore a relevant opportunity | If a relevant opportunity is identified, Origin explains the proposed recipient and the company information to be shared. Your authorized contact approves that named introduction before it is made. |
| 4. Assess the terms | Your company reviews the proposed license and decides whether to proceed. Confirm the records, permitted uses, delivery requirements, and payment conditions. |

The full steps are on [how it works](https://origindatapartners.com/how-it-works). The brief is a starting point for a discussion. It is not a valuation, rights clearance, or a receiving program’s acceptance.


## Is licensing data the same as selling the fintech?

No. A data license grants defined rights to use a de-identified copy of certain records; the company keeps operating and keeps its records. What the company would sell for is a separate question. See [what is my business worth](https://origindatapartners.com/guides/what-is-my-business-worth).

More deals are on the [case studies page](https://origindatapartners.com/case-studies).

Does your company hold records like these? [See what your data is worth](https://origindatapartners.com/check-fit).


## Questions and answers

### How much was the neobank paid for its data?

$375,000, for licensing its company records in a deal Origin helped place. Names stay private; this is one outcome, not a forecast.

### What records does a neobank have that AI companies want?

Origin does not publish the record types in this deal. Neobanks generally hold transaction histories, support tickets, code and issue trackers, compliance procedures and product documents.

### Can a fintech share customer data for AI training?

Gramm-Leach-Bliley limits disclosure of nonpublic personal information to nonaffiliated third parties. Blind data without identifiers falls outside Regulation P’s definition, so de-identifying first is the usual route. Check the partner bank agreement too.

### Does a fintech need 30 employees?

It depends on the program. micro1 looks for 30+ full-time employees; Handshake AI looks for 20+ and 3+ years in operation.

### Where are the other case studies?

On the [case studies page](https://origindatapartners.com/case-studies), grouped by industry.

## Sources

- [15 U.S.C. 6802, Gramm-Leach-Bliley Act disclosure limits (Cornell LII)](https://www.law.cornell.edu/uscode/text/15/6802)
- [12 CFR 1016.3, Regulation P definitions (eCFR)](https://www.ecfr.gov/current/title-12/chapter-X/part-1016/section-1016.3)
- [Handshake AI: company data licensing, published payouts and eligibility](https://joinhandshake.com/ai/data-partnerships/license/)
- [Mercor: published data program terms and target industries](https://www.mercor.com/data/)

## Related reading

- [Licensing payments and transaction data to AI companies](https://origindatapartners.com/guides/license-transaction-data-ai-training)
- [/who-we-help/software-companies](https://origindatapartners.com/who-we-help/software-companies)
- [Can a company sell its source code to AI companies for training?](https://origindatapartners.com/guides/sell-source-code-ai-training)
- [Exclusive vs non-exclusive data licenses: what sellers should know](https://origindatapartners.com/guides/exclusive-vs-non-exclusive-data-license)
- [/case-studies](https://origindatapartners.com/case-studies)
- [/case-studies/mortgage-lender-loan-data-1-15-million](https://origindatapartners.com/case-studies/mortgage-lender-loan-data-1-15-million)
- [/case-studies/insurance-firm-claims-data-1-3-million](https://origindatapartners.com/case-studies/insurance-firm-claims-data-1-3-million)