Transparency alternatives to Teller
Other Payment processing vendors we measure, sorted by how much they publish that Teller does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 31 that differ from Teller on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Teller 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, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Teller does not” is the one that closes them.
| Vendor | Score | Publishes, and Teller does not | Teller publishes, and they do not | |
|---|---|---|---|---|
| Maxiomaxio.com | 74/100 | 7 Data processing agreement, Subprocessor list, Data location stated, +4 | 1 No third-party tracking before consent | Compare |
| Molliemollie.com | 61/100 | 7 Data processing agreement, Status page with history, Public pricing, +4 | 1 No third-party tracking before consent | Compare |
| Adyenadyen.com | 52/100 | 6 Data processing agreement, Public pricing, Certifications named, +3 | 1 No third-party tracking before consent | Compare |
| GoCardlessgocardless.com | 43/100 | 5 Data processing agreement, Public pricing, Certifications named, +2 | 1 No third-party tracking before consent | Compare |
| Recurlyrecurly.com | 43/100 | 5 Data location stated, Public pricing, Certifications named, +2 | 1 No third-party tracking before consent | Compare |
| Creemcreem.io | 48/100 | 4 Data processing agreement, Status page with history, Public pricing, +1 | 1 No third-party tracking before consent | Compare |
| Paddlepaddle.com | 39/100 | 4 Data processing agreement, Public pricing, security.txt (RFC 9116), +1 | 1 No third-party tracking before consent | Compare |
| Stripestripe.com | 30/100 | 4 Public pricing, Certifications named, security.txt (RFC 9116), +1 | 1 No third-party tracking before consent | Compare |
| Lemon Squeezylemonsqueezy.com | 43/100 | 3 Data processing agreement, Data location stated, Public pricing | 1 No third-party tracking before consent | Compare |
| Squaresquareup.com | 35/100 | 3 Data location stated, Public pricing, Certifications named | 1 No third-party tracking before consent | Compare |
| Airwallexairwallex.com | 30/100 | 3 Status page with history, Public pricing, security.txt (RFC 9116) | 1 No third-party tracking before consent | Compare |
| Payrexxpayrexx.com | 30/100 | 3 Status page with history, Public pricing, Named privacy contact | 1 No third-party tracking before consent | 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.