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