Merchant Services
bd_4af709dd8df8f3c0 · schema v1 · pii pii-v1
Paysafe Group Holdings Limited (via Merchant Services) disclosed a cybersecurity incident affecting a legacy website. Unauthorized access occurred between May 13, 2018, and November 24, 2020. The incident involved automated queries accessing personal information including names, SSNs, and bank account details. Paysafe engaged forensic experts, closed the site, notified law enforcement, and provided 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 18, 2020
Filed
vs. sector median
3 wks faster
Linked disclosures
Why this link?Regulatory filings (8) · sorted by filing gap
- Indiana State AGbd_48e28894f734a21b2020-12-18Verified
- Washington State AGbd_1151afe21cdd47ff2020-12-16 · +2dVerified
- California State AGbd_1c3042be6747728b2020-12-16 · +2dVerified
- South Carolina State AGbd_a7e7764a6bda27062020-12-16 · +2dVerified
Show 4 more filings ↓Show fewer ↑up to 32d gap
- New Hampshire State AGbd_ec174ff5603cb5902020-12-21 · +3dVerified
- Massachusetts State AGbd_397975980f30df2c2020-12-23 · +5dVerified
- Maine State AGbd_6a289d8c42bb094c2021-01-12 · +25dVerified
- Oregon State AGbd_8e5980705d10b8f52021-01-19 · +32dCandidate
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.