Transparency alternatives to Yuno
Other Payment orchestration vendors we measure, sorted by how much we found at them and not at Yuno. This is a comparison of disclosure, not of features or fitness.
12 shown of 33 that differ from Yuno on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Yuno has 4 gaps in what we could measure: Subprocessor list, Public pricing, No third-party tracking before consent, security.txt (RFC 9116). The column “Found there, not found at Yuno” is the one that closes them.
| Vendor | Score | Found there, not found at Yuno | Found at Yuno, not found there | |
|---|---|---|---|---|
| Rebillyrebilly.comSee also Transparency alternatives to Rebilly | 57/100 | 3 Subprocessor list, Public pricing, No third-party tracking before consent | 5 Data location stated, Status page with history, Certifications named, +2 | Compare |
| Increaseincrease.comSee also Transparency alternatives to Increase | 30/100 | 2 Public pricing, security.txt (RFC 9116) | 6 Data processing agreement, Data location stated, Certifications named, +3 | Compare |
| IXOPAYixopay.comSee also Transparency alternatives to IXOPAY | 45/100 | 1 Subprocessor list | 5 Data location stated, Certifications named, Uptime SLA with a figure, +2 | Compare |
| Spreedlyspreedly.comSee also Transparency alternatives to Spreedly | 43/100 | 1 Public pricing | 4 Data processing agreement, Uptime SLA with a figure, Notice before subprocessors change, +1 | Compare |
| TrueLayertruelayer.comSee also Transparency alternatives to TrueLayer | 39/100 | 1 security.txt (RFC 9116) | 4 Data processing agreement, Uptime SLA with a figure, Notice before subprocessors change, +1 | Compare |
| Corefycorefy.comSee also Transparency alternatives to Corefy | 30/100 | 1 Public pricing | 6 Data processing agreement, Status page with history, Certifications named, +3 | Compare |
| Modulrmodulrfinance.comSee also Transparency alternatives to Modulr | 26/100 | 1 Public pricing | 6 Data processing agreement, Data location stated, Certifications named, +3 | Compare |
| Yapilyyapily.comSee also Transparency alternatives to Yapily | 26/100 | 1 Subprocessor list | 6 Data processing agreement, Data location stated, Status page with history, +3 | Compare |
| Nomupaynomupay.comSee also Transparency alternatives to Nomupay | 22/100 | 1 Public pricing | 6 Data processing agreement, Data location stated, Status page with history, +3 | Compare |
| Weavrweavr.ioSee also Transparency alternatives to Weavr | 22/100 | 1 Public pricing | 6 Data processing agreement, Data location stated, Status page with history, +3 | Compare |
| Payneteasypayneteasy.comSee also Transparency alternatives to Payneteasy | 17/100 | 1 No third-party tracking before consent | 7 Data processing agreement, Data location stated, Status page with history, +4 | Compare |
| Silverflowsilverflow.comSee also Transparency alternatives to Silverflow | 13/100 | 1 security.txt (RFC 9116) | 7 Data processing agreement, Data location stated, Status page with history, +4 | 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.