Transparency alternatives to Square
Other Payment processing vendors we measure, sorted by how much we found at them and not at Square. This is a comparison of disclosure, not of features or fitness.
12 shown of 31 that differ from Square on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Square has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Square” is the one that closes them.
| Vendor | Score | Found there, not found at Square | Found at Square, not found there | |
|---|---|---|---|---|
| Maxiomaxio.comSee also Transparency alternatives to Maxio | 74/100 | 4 Data processing agreement, Subprocessor list, Notice before subprocessors change, +1 | nothing | Compare |
| Adyenadyen.comSee also Transparency alternatives to Adyen | 52/100 | 4 Data processing agreement, security.txt (RFC 9116), Notice before subprocessors change, +1 | 1 Data location stated | Compare |
| Molliemollie.comSee also Transparency alternatives to Mollie | 52/100 | 4 Data processing agreement, security.txt (RFC 9116), Notice before subprocessors change, +1 | 1 Data location stated | Compare |
| Airwallexairwallex.comSee also Transparency alternatives to Airwallex | 48/100 | 3 Status page with history, security.txt (RFC 9116), Named privacy contact | 1 Certifications named | Compare |
| Creemcreem.ioSee also Transparency alternatives to Creem | 48/100 | 3 Data processing agreement, Status page with history, Notice before subprocessors change | 2 Data location stated, Certifications named | Compare |
| GoCardlessgocardless.comSee also Transparency alternatives to GoCardless | 43/100 | 3 Data processing agreement, security.txt (RFC 9116), Named privacy contact | 1 Data location stated | Compare |
| Paddlepaddle.comSee also Transparency alternatives to Paddle | 39/100 | 3 Data processing agreement, security.txt (RFC 9116), Named privacy contact | 2 Data location stated, Certifications named | Compare |
| Stancerstancer.comSee also Transparency alternatives to Stancer | 39/100 | 3 Status page with history, No third-party tracking before consent, security.txt (RFC 9116) | 2 Data location stated, Certifications named | Compare |
| Recurlyrecurly.comSee also Transparency alternatives to Recurly | 43/100 | 2 Uptime SLA with a figure, Named privacy contact | nothing | Compare |
| Stripestripe.comSee also Transparency alternatives to Stripe | 30/100 | 2 security.txt (RFC 9116), Named privacy contact | 1 Data location stated | Compare |
| Unzerunzer.comSee also Transparency alternatives to Unzer | 22/100 | 2 Status page with history, security.txt (RFC 9116) | 3 Data location stated, Public pricing, Certifications named | Compare |
| Lemon Squeezylemonsqueezy.comSee also Transparency alternatives to Lemon Squeezy | 43/100 | 1 Data processing agreement | 1 Certifications named | 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.