DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed11 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 11 filings

Payactiv — April 2025 breach

Clustered 11 filings across 11 jurisdictions · filing window Sep 25, 2025 → Jan 7, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

11

Affected · reported

202,194

First → last filing

Sep 25, 2025 → Jan 7, 2026

Merge confidence

100%

incident inc_209ffccd04674add · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe unauthorized access. Intrusion Apr 3, 2025–Aug 20, 2025, discovered Aug 19, 2025 — the first regulatory filing landed 37 days later (flagged late). 202,194 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 2 more. Notifications rolled out on a 104-day schedule across 11 filings beginning Sep 25, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
37days

Discovered → first regulatory filing

Discovery variance
24days

Range of discovered_at dates across filings

Filing span
104days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksTexas✗ TX AG >30dMaine⏱ ME AG >30d · 53dWashington⏱ WA AG >30dDate basis✓ Clock withheld · confirmation dateOregon✓ OR AG ≤45dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 3, 2025breach begins
Aug 19, 2025discovered · members disagree
notification delay · 37 days
Sep 25, 2025first filing
Jan 7, 2026most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. SEP 25IN AGIN AG noticefirst filing · states nationwide total 21,077day 0
  2. SEP 29MT AGMT AG notice174 MT residents+4d
  3. SEP 29NH AGNH AG notice54 NH residents+4d
  4. SEP 29NE AGNE AG notice388 NE residents+4d
  5. SEP 30VT AGVT AG noticeno count stated+5d
  6. OCT 11OR AGOR AG noticestates nationwide total 176,282+16d
  7. OCT 11MA AGMA AG notice288 MA residents+16d
  8. OCT 11ME AGME AG notice118 ME residents+16d
  9. OCT 11WA AGWA AG notice18,085 WA residents+16d
  10. OCT 11CA AGCA AG noticeno count stated+16d
  11. JAN 7TX AGTX AG noticemost recent · states nationwide total 202,194+104d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 3, 2025
IN AG
Discovered
Aug 19, 2025NH AG + NE AG + ME AG +2Sep 12, 2025MT AG + VT AG + OR AG +1filings disagree on discovery
Data types
Credentials · Financial account · Identity (basic) · Government ID · PII
MT AG + VT AG + CA AG +6
Attack vector
Unauthorized Access
MT AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

202,194

Sum of filed state slices

34,836· 17.2% of stated

83% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US202,194
WA18,085
TX14,461
IN1,268
NE388
MA288
MT174
ME118
NH54

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing11 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

104 days

Cadence

~1 / 10.4d

vs. multi-state median

13.0× slower

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.