Alternatives to Payone
Other Retail point of sale vendors we measure, sorted by how much they publish that Payone does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 14 that differ from Payone on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Payone has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “publishes and Payone does not” is the one that closes them.
| Vendor | Score | Publishes, and Payone does not | Payone publishes, and they do not | |
|---|---|---|---|---|
| Kassensichvfiskaly.com | 35/100 | 3 Data location stated, Status page with history, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Hikehikeup.com | 30/100 | 2 Data location stated, Public pricing | 1 security.txt (RFC 9116) | Compare |
| Epsonposepson.de | 17/100 | 2 Data location stated, Named privacy contact | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Ls Retaillsretail.com | 22/100 | 1 Data location stated | 1 security.txt (RFC 9116) | Compare |
| Efstaefsta.eu | 17/100 | 1 Status page with history | 1 security.txt (RFC 9116) | Compare |
| Tillhubtillhub.de | 17/100 | 1 Named privacy contact | nothing | Compare |
| Ccvccv.eu | 14/100 | 1 Named privacy contact | nothing | Compare |
| Orishaorisha.com | 9/100 | 1 No third-party tracking before consent | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Anybillanybill.de | 9/100 | nothing we found there and not here | 1 security.txt (RFC 9116) | Compare |
| Helloclayhelloclay.de | 9/100 | nothing we found there and not here | 1 security.txt (RFC 9116) | Compare |
| Ncr Counterpointncr.com | 9/100 | nothing we found there and not here | 1 security.txt (RFC 9116) | Compare |
| NewPOSnewpos.ai | 0/100 | nothing we found there and not here | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.