Yes, in part. Banks, insurers and payment companies can license de-identified case files under a signed data license if they have the right to share them, but several categories have to come out first: suspicious activity reports and anything that would reveal one, nonpublic personal information about consumers, card and bank account numbers, government IDs and health records. What is left is the decision trail: the evidence reviewed, the steps taken and the outcome.
This article is general information, not legal advice. Your own counsel should review what your institution may disclose.
Which case files Paid4Data lists
The industry pages name the record types:
- Banks and payment companies: payment operations and exception handling records, chargeback and dispute case files, fraud investigations and their outcomes, AML and KYC review files and decisions.
- Insurance carriers, MGAs and reinsurers: quotes, binders and underwriting files, claim files with notes and outcomes, treaty slips, bordereaux and delegated authority reports.
- Independent adjusting firms: claim reports and estimates, coverage analysis notes, correspondence and negotiation, supplements and appeals.
- Commercial lenders: loan packages and checklists, underwriting memos, closing workflows, lender and borrower correspondence.
Each page carries the same condition: records can be included only where the firm has the right to share them.
Suspicious activity reports stay out
The Bank Secrecy Act, at 31 U.S.C. 5318(g)(2)(A)(i), says that when a financial institution reports a suspicious transaction, neither the institution nor its directors, officers, employees or agents may "notify any person involved in the transaction that the transaction has been reported or otherwise reveal any information that would reveal that the transaction has been reported."
The regulation for banks, 31 CFR 1020.320(e), states: "A SAR, and any information that would reveal the existence of a SAR, are confidential and shall not be disclosed except as authorized in this paragraph (e)." Paragraph (e)(1)(i) adds that no bank, and no director, officer, employee or agent of a bank, "shall disclose a SAR or any information that would reveal the existence of a SAR."
Under that text, the question for an AML or fraud file is not only whether it contains the report itself but whether anything in it would reveal that a report was filed. That call belongs to the institution's BSA officer and counsel. Paid4Data's banking page states that records law or regulation bars a firm from disclosing, "such as suspicious activity reports, cannot be included."
Nonpublic personal information under Regulation P
Regulation P (12 CFR part 1016) implements the privacy provisions of the Gramm-Leach-Bliley Act for the institutions it covers. Section 1016.10(a)(1) says a covered institution may not disclose "any nonpublic personal information about a consumer to a nonaffiliated third party" unless it has given the required notices and a reasonable opportunity to opt out and the consumer has not opted out, except as the rule otherwise authorizes.
Three definitions in 12 CFR 1016.3 do most of the work:
- Nonpublic personal information, at (p)(1), means "personally identifiable financial information" and any list, description or other grouping of consumers derived using personally identifiable financial information that is not publicly available.
- Personally identifiable financial information, at (q)(1), means any information a consumer provides to obtain a financial product or service, information about a consumer resulting from a transaction, or information otherwise obtained about a consumer in connection with providing a financial product or service. The examples at (q)(2)(i) include account balance information, payment history, and "the fact that an individual is or has been one of your customers."
- What is not included, at (q)(2)(ii)(B): "Information that does not identify a consumer, such as aggregate information or blind data that does not contain personal identifiers such as account numbers, names, or addresses."
The definition does not name a method for producing blind data. Whether a specific dataset "does not identify a consumer" is a judgment for the institution and its counsel.
Two scope points are in 12 CFR 1016.1(b). The part applies only to information about individuals who obtain financial products or services "primarily for personal, family, or household purposes," and does not apply to information about companies. And it does not apply to registered broker-dealers, registered investment advisers, or an insurance company "with respect to its insurance activities" that is "subject to supervision by a state insurance regulator." Those firms need to ask counsel which privacy rules cover them.
Card numbers, bank account numbers and government IDs
PCI DSS is an industry standard, not a statute. The PCI Security Standards Council describes it as "a baseline of technical and operational requirements designed to protect payment account data," applying to entities that "store, process, or transmit cardholder data (CHD) and/or sensitive authentication data (SAD)."
Paid4Data's rule here is simpler than any standard. Payment card numbers, bank account numbers and government ID numbers are on the never accepted list, along with patient and health records, data about children and biometric data. Payroll and HR records are always excluded.
Health information in claim files
HHS states that the HIPAA Rules apply to covered entities and business associates, and that a covered entity is a health care provider that transmits information electronically in connection with a standard transaction, a health plan, or a health care clearinghouse. Its list of health plans includes health insurance companies. HHS also states that an entity that does not meet either definition "does not have to comply with the HIPAA Rules."
Whether HIPAA reaches a given claim file is therefore a question about who holds it. For licensing through Paid4Data the answer does not change the outcome: health records are not accepted from anyone. Injury and disability claim files that contain medical records are out, or the medical content is.
What must come out, by record type
| Record type | What must be excluded or removed | Primary rule |
|---|---|---|
| AML and fraud investigation files | Any SAR and any information that would reveal the existence of a SAR | 31 U.S.C. 5318(g)(2); 31 CFR 1020.320(e) |
| Consumer account, dispute and loan files | Nonpublic personal information about consumers, including account numbers, names and addresses | 12 CFR 1016.3(p) and (q); 12 CFR 1016.10 |
| Chargeback and payment operations files | Cardholder data and sensitive authentication data; card numbers are never accepted | PCI DSS; Paid4Data never-accepted list |
| Insurance claim files | Patient and health records | HIPAA Rules (45 CFR 160.103 definitions); Paid4Data never-accepted list |
| KYC and onboarding files | Government ID numbers and bank account numbers | Paid4Data never-accepted list |
What is left: the decision trail
Once those items are removed, a case file still shows how the work was done: what triggered the case, which evidence the analyst pulled, which policy or coverage clause was applied, who reviewed it, and how it ended. The banking page puts the value this way: case files that pair the evidence with the decision made "show how trained analysts judge risk, which public data does not capture."
Paid4Data's own process then removes names, emails, phone numbers, street addresses, account and invoice numbers, tax IDs and signatures, replaces people and company names with consistent pseudonyms, and shifts dates by a consistent offset. The steps are described in how de-identification works.
Where the exclusions get written down
The data license includes a Data Schedule listing approved systems, date ranges, exclusions and restricted buyers. That is where a compliance lead records that SAR-related material, a given product line or a date range is out. Nothing is uploaded before then: the advanced intake only describes each system and its volume, and the scoping call takes place under a mutual NDA. Export is by secure upload or temporary read-only access, never email.
No price or sale is guaranteed, and no payment is owed until a buyer pays. If your counsel is comfortable with the categories above, you can request a free data review.
Sources
Checked on November 16, 2026.
- 31 U.S.C. 5318 - Compliance, exemptions, and summons authority, U.S. Government Publishing Office (govinfo.gov), United States Code
- 31 CFR 1020.320 - Reports by banks of suspicious transactions, Electronic Code of Federal Regulations (National Archives / GPO)
- 12 CFR 1016.3 - Definitions (Regulation P), Electronic Code of Federal Regulations (National Archives / GPO)
- 12 CFR 1016.10 - Limits on disclosure of nonpublic personal information to nonaffiliated third parties, Electronic Code of Federal Regulations (National Archives / GPO)
- 12 CFR 1016.1 - Purpose and scope, Electronic Code of Federal Regulations (National Archives / GPO)
- PCI DSS (Payment Card Industry Data Security Standard), PCI Security Standards Council
- Covered Entities and Business Associates, U.S. Department of Health and Human Services, Office for Civil Rights
- 45 CFR 160.103 - Definitions, Electronic Code of Federal Regulations (National Archives / GPO)