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