Paysafe Group Holdings Limitedd
bd_a7e7764a6bda2706 · schema v1 · pii pii-v1
Full breach record for Paysafe Group Holdings Limitedd →2 incidents on filePaysafe Group Holdings Limited notified South Carolina of a cybersecurity incident affecting a legacy website used by Merchant Services. Unauthorized actors submitted automated queries between May 2018 and November 2020, potentially accessing names, contact details, SSNs, and bank account information. Paysafe engaged forensics, notified law enforcement, closed the site, and offered two years of credit monitoring.
J jump to incidentP pin to compareR raw source
Incident timeline
May 13, 2018
Begins
Nov 6, 2020
Discovered
Dec 16, 2020
Filed
vs. sector median
4 wks faster
Linked disclosures
Why this link?Regulatory filings (8) · sorted by filing gap
- Washington State AGbd_1151afe21cdd47ff2020-12-16Verified
- California State AGbd_1c3042be6747728b2020-12-16Verified
- Indiana State AGbd_48e28894f734a21b2020-12-18 · +2dVerified
- Montana State AGbd_4af709dd8df8f3c02020-12-18 · +2dVerified
Show 4 more filings ↓Show fewer ↑up to 34d gap
- New Hampshire State AGbd_ec174ff5603cb5902020-12-21 · +5dVerified
- Massachusetts State AGbd_397975980f30df2c2020-12-23 · +7dVerified
- Maine State AGbd_6a289d8c42bb094c2021-01-12 · +27dVerified
- Oregon State AGbd_8e5980705d10b8f52021-01-19 · +34dCandidate
Filing propagation · 9 filings · 9 states
View merged incident ↗Pattern: first filing Dec 16 (WA), last Jan 19 (OR) — a 34-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.