Documented criteria are source-backed values, not estimates. Research records can still have unknown results. Verified does not mean independently tested; extraction confidence and human review are shown with each claim.
| Attribute | Value | State and source |
|---|---|---|
| Gaming named as a use | Yes | Verified69% confidence Read from a menu, footer or link list, not from a sentence about the product EvidenceExcerpt ...Cash Deposits Back Cash Out Back Park Christmas Savings Back Love2shop Gift Vouchers Back Gaming Vouchers Back Entertainment Vouchers Back Payment Exception Service Back FAQ Store locato... Excerpt kindnavigation entry (a menu, footer or link list, not a sentence about the product) Subject named in excerptno Sourcehttps://www.paypoint.com/ · Primary documentation · retrieved 3 times from 2026-09-02 to 2026-10-03 · every date Confidence69% - capped at the measured precision of this kind of excerpt (69%, navigation), which is below the reader's own precision (70%) HistoryStatement history How it was read Read bytext pattern muster:\bgam(?:ing|ers?)\bFirst observed2026-09-02 Last checked2026-10-02 Human reviewnot documented Source confidence90% Reader precision70% (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. |
These are claims about who the vendor addresses, read off their own pages. They say nothing about how well the product serves that audience.
Every documented value links to the page we read it from, with the source tier and the day we retrieved it, in its row under Specifications. “Evidence” in that row opens the excerpt.
These attributes are open in our research. We looked and found no reliable evidence; 84 addresses were checked and are listed below. That is a statement about our research and never about the product.
| Attribute | State | What we checked |
|---|---|---|
| Public API | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
| Audit log | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
| Data processing agreement offered | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
| EU data residency stated | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
| FedRAMP authorisation | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
| GDPR compliance stated | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
| HIPAA compliance stated | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
| Education named as a market | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
| Energy or utilities named as a market | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
| Financial services named as a market | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
| Healthcare named as a market | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
| Logistics or supply chain named as a market | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
| Manufacturing named as a market | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
| Public sector named as a market | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
| Retail or e-commerce named as a market | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
| ISO/IEC 27001 | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
| Mobile app (iOS or Android) | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
| PCI DSS stated | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
| SCIM user provisioning | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
| SOC 2 Type II | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
| Single sign-on | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
| Creators named as an audience | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
| Enterprises named as an audience | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
| Families named as an audience | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
| Freelancers named as an audience | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
| Remote or hybrid teams named as an audience | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
| Small businesses named as an audience | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
| Students named as an audience | Not yet verified | Checked 1 address (3 reads), most recently on 2026-10-03: www.paypoint.com |
An open attribute describes our research and never the product.
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.
Ask PayPoint for a demo, a quote or an introduction. Your request is passed on only with your consent.
