Paysafe
1 product we track, 1 with documented attributes
How this entry is matched to public registers, each with the day we last read it. An identifier says which record we mean, not anything about the vendor or the product.
These are claims about who the vendor addresses, read off their own pages. They say nothing about how well the product serves that audience.
| Attribute | Value | Source, tier and retrieval date |
|---|---|---|
| Retail or e-commerce named as a market | Yes | Verified69% confidence www.paysafe.com (Primary documentation), retrieved 2026-10-16 Read from a menu, footer or link list, not from a sentence about the product EvidenceExcerpt ...REX, Stocks & Trading Hospitality iGaming Lotteries Petrol & Diesel Recreational Services Retail Subscription & Membership Services Travel Utilities Video Gaming Industry * Dieses Feld i... Excerpt kindnavigation entry (a menu, footer or link list, not a sentence about the product) Subject named in excerptno Sourcehttps://www.paysafe.com · Primary documentation · retrieved 3 times from 2026-09-14 to 2026-10-16 · every date Confidence69% - the source confidence; no cap applies (below the measured precision) HistoryStatement history How it was read Read bytext pattern muster:\bretail\b(?! (?:price|value|prices|banking|stores?|locations?|partners?|chain)\b)First observed2026-09-14 Last checked2026-10-16 Human reviewnot documented Source confidence69% Reader precision88% (measured by hand for this reader) Excerpt-kind precision69% (measured by hand over 422 statements of this kind) Confidence interpretationA heuristic informed by source assessment and reader samples, not a calibrated probability that this individual claim is correct. |
| Publicly traded | Yes | Verified90% confidence EDGAR company facts (Primary documentation), retrieved 2026-09-09 EvidenceNoteListed in the SEC company ticker file Sourcehttps://www.sec.gov/cgi-bin/browse-edgar?action=getcompany&CIK=0001833835 · Primary documentation · retrieved 33 times from 2026-09-04 to 2026-10-18 · every date Confidence90% - the source confidence; no cap applies (not a text extraction) HistoryStatement history How it was read Read byconnector to an official machine-readable source konnektor:sec-edgarParser version1 First observed2026-09-04 Last checked2026-10-18 Human reviewnot documented Source confidence90% Reader precision71% - no measurement for this reader; this is the average across all our readers, measured by hand Confidence interpretationA heuristic informed by source assessment and reader samples, not a calibrated probability that this individual claim is correct. |
| Industry classification (SIC) | Services-Business Services, NEC | Verified90% confidence EDGAR company facts (Primary documentation), retrieved 2026-09-04 EvidenceNoteSIC 7389 Sourcehttps://data.sec.gov/submissions/CIK0001833835.json · Primary documentation · retrieved 2026-09-04 Confidence90% - the source confidence; no cap applies (not a text extraction) HistoryStatement history How it was read Read byconnector to an official machine-readable source konnektor:sec-edgarParser version1 First observed2026-09-04 Last checked2026-09-04 Human reviewnot documented Source confidence90% Reader precision71% - no measurement for this reader; this is the average across all our readers, measured by hand Confidence interpretationA heuristic informed by source assessment and reader samples, not a calibrated probability that this individual claim is correct. |
| Stock ticker | PSFE | Verified90% confidence EDGAR company facts (Primary documentation), retrieved 2026-09-19 EvidenceSourcehttps://www.sec.gov/cgi-bin/browse-edgar?action=getcompany&CIK=0001833835 · Primary documentation · retrieved 33 times from 2026-09-04 to 2026-10-18 · every date Confidence90% - the source confidence; no cap applies (not a text extraction) HistoryStatement history How it was read Read byconnector to an official machine-readable source konnektor:sec-edgarParser version1 First observed2026-09-04 Last checked2026-10-18 Human reviewnot documented Source confidence90% Reader precision71% - no measurement for this reader; this is the average across all our readers, measured by hand Confidence interpretationA heuristic informed by source assessment and reader samples, not a calibrated probability that this individual claim is correct. |
| Gaming named as a use | Yes | Verified70% confidence www.paysafe.com (Primary documentation), retrieved 2026-10-16 EvidenceExcerpt ...auenswürdiges Spielerlebnis mit schnellen und sicheren Zahlungsmethoden, die speziell für Gaming- und Unterhaltungsplattformen mit hohem Datenaufkommen entwickelt wurden und durch umfass... Excerpt kindrunning text Subject named in excerptno Sourcehttps://www.paysafe.com · Primary documentation · retrieved 3 times from 2026-09-14 to 2026-10-16 · every date Confidence70% - the source confidence; no cap applies (below the measured precision) HistoryStatement history How it was read Read bytext pattern muster:\bgam(?:ing|ers?)\bFirst observed2026-09-14 Last checked2026-10-16 Human reviewnot documented Source confidence70% Reader precision70% (measured by hand for this reader) Excerpt-kind precision79% (measured by hand over 857 statements of this kind) Confidence interpretationA heuristic informed by source assessment and reader samples, not a calibrated probability that this individual claim is correct. |
These attributes are open in our research. We looked and found no reliable evidence; 76 addresses were checked and are listed below. That is a statement about our research and never about the product.
| Attribute | State | What we checked |
|---|---|---|
| Data processing agreement offered | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-16: www.paysafe.com |
| Employees | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-16: www.paysafe.com |
| EU data residency stated | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-16: www.paysafe.com |
| FedRAMP authorisation | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-16: www.paysafe.com |
| Founded | Not yet verified | Checked 1 address (4 reads), most recently on 2026-10-16: www.paysafe.com |
| GDPR compliance stated | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-16: www.paysafe.com |
| HIPAA compliance stated | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-16: www.paysafe.com |
| Headquarters | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-16: www.paysafe.com |
| Education named as a market | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-16: www.paysafe.com |
| Energy or utilities named as a market | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-16: www.paysafe.com |
| Financial services named as a market | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-16: www.paysafe.com |
| Healthcare named as a market | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-16: www.paysafe.com |
| Logistics or supply chain named as a market | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-16: www.paysafe.com |
| Manufacturing named as a market | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-16: www.paysafe.com |
| Public sector named as a market | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-16: www.paysafe.com |
| ISO/IEC 27001 | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-16: www.paysafe.com |
| PCI DSS stated | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-16: www.paysafe.com |
| SOC 2 Type II | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-16: www.paysafe.com |
| Creators named as an audience | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-16: www.paysafe.com |
| Enterprises named as an audience | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-16: www.paysafe.com |
| Families named as an audience | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-16: www.paysafe.com |
| Freelancers named as an audience | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-16: www.paysafe.com |
| Remote or hybrid teams named as an audience | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-16: www.paysafe.com |
| Small businesses named as an audience | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-16: www.paysafe.com |
| Students named as an audience | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-16: www.paysafe.com |
We published these statements and later withdrew them. Each line names the day and the reason. A withdrawal describes our reading of a source, never the product or the vendor; the former value stays visible so that the correction can be checked.
| Attribute | Former value | Withdrawn | Reason |
|---|---|---|---|
| Legal entity status | 2026-09-04 | The LEI record was matched on the legal name alone. A name is not an identity: the register holds legal entities of the same name in other countries. Withdrawn until a second, independent signal confirms the match. | |
| Public API | 2026-09-02 | Retired 2026-09-02: the attribute does not apply to this kind of subject (attribute.gilt_fuer). |
Every documented value above links to the page we read it from, with the source tier and the day we retrieved it, and its row opens the excerpt. An open attribute describes our research and never the product.