Alternatives to TrueLayer
Other Payment orchestration vendors we measure, sorted by how much they publish that TrueLayer does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 33 that differ from TrueLayer on at least one criterion we measured for both. Public transparency score, not a product or security rating.
TrueLayer has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Public pricing, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “publishes and TrueLayer does not” is the one that closes them.
| Vendor | Score | Publishes, and TrueLayer does not | TrueLayer publishes, and they do not | |
|---|---|---|---|---|
| Yunoy.uno | 65/100 | 5 Data processing agreement, Data location stated, Uptime SLA with a figure, +2 | 1 security.txt (RFC 9116) | Compare |
| Rebillyrebilly.com | 48/100 | 5 Data processing agreement, Subprocessor list, Public pricing, +2 | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | Compare |
| IXOPAYixopay.com | 45/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 2 Certifications named, HTTPS enforced with HSTS | Compare |
| Yapilyyapily.com | 35/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Spreedlyspreedly.com | 43/100 | 2 Data location stated, Public pricing | 1 security.txt (RFC 9116) | Compare |
| Unitunit.co | 39/100 | 2 Data location stated, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Solarissolarisgroup.com | 35/100 | 2 Data location stated, Named privacy contact | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Corefycorefy.com | 30/100 | 2 Data location stated, Public pricing | 3 Status page with history, Certifications named, security.txt (RFC 9116) | Compare |
| BR-DGEbr-dge.to | 26/100 | 2 Data location stated, Named privacy contact | 3 Status page with history, Certifications named, security.txt (RFC 9116) | Compare |
| Payrailspayrails.com | 26/100 | 2 Data location stated, Named privacy contact | 3 Status page with history, Certifications named, security.txt (RFC 9116) | Compare |
| Nomupaynomupay.com | 22/100 | 2 Public pricing, Named privacy contact | 3 Status page with history, Certifications named, security.txt (RFC 9116) | Compare |
| Weavrweavr.io | 22/100 | 2 Public pricing, Named privacy contact | 3 Status page with history, Certifications named, security.txt (RFC 9116) | 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.