Alternatives to Lemon Squeezy
Other Payment processing vendors we measure, sorted by how much they publish that Lemon Squeezy does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 26 that differ from Lemon Squeezy on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Lemon Squeezy has 6 gaps in what we could measure: Subprocessor list, Status page with history, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116). The column “publishes and Lemon Squeezy does not” is the one that closes them.
| Vendor | Score | Publishes, and Lemon Squeezy does not | Lemon Squeezy publishes, and they do not | |
|---|---|---|---|---|
| Molliemollie.com | 61/100 | 3 Status page with history, Certifications named, security.txt (RFC 9116) | 1 Data location stated | Compare |
| GoCardlessgocardless.com | 55/100 | 3 Status page with history, Certifications named, security.txt (RFC 9116) | 1 Data location stated | Compare |
| Recurlyrecurly.com | 55/100 | 3 Status page with history, Certifications named, Uptime SLA with a figure | 1 Data processing agreement | Compare |
| Stancerstancer.com | 45/100 | 3 Status page with history, No third-party tracking before consent, security.txt (RFC 9116) | 2 Data processing agreement, Data location stated | Compare |
| Maxiomaxio.com | 70/100 | 2 Subprocessor list, Certifications named | nothing | Compare |
| Adyenadyen.com | 65/100 | 2 Certifications named, security.txt (RFC 9116) | nothing | Compare |
| SumUpsumup.com | 50/100 | 2 Status page with history, security.txt (RFC 9116) | 1 Data processing agreement | Compare |
| Airwallexairwallex.com | 30/100 | 2 Status page with history, security.txt (RFC 9116) | 2 Data processing agreement, Data location stated | Compare |
| Stripestripe.com | 30/100 | 2 Certifications named, security.txt (RFC 9116) | 2 Data processing agreement, Data location stated | Compare |
| Unzerunzer.com | 22/100 | 2 Status page with history, security.txt (RFC 9116) | 3 Data processing agreement, Data location stated, Public pricing | Compare |
| Squaresquareup.com | 40/100 | 1 Certifications named | 1 Data processing agreement | Compare |
| Paddlepaddle.com | 39/100 | 1 security.txt (RFC 9116) | 1 Data location stated | 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.