SaaS Ranking

Alternatives to Yuno

Other Payment orchestration vendors we measure, sorted by how much they publish that Yuno does not. 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 “publishes and Yuno does not” is the one that closes them.

VendorScorePublishes, and Yuno does notYuno publishes, and they do not
Rebillyrebilly.com 48/100 2 Subprocessor list, Public pricing 5 Data location stated, Status page with history, Certifications named, +2 Compare
Increaseincrease.com 30/100 2 Public pricing, security.txt (RFC 9116) 6 Data processing agreement, Data location stated, Certifications named, +3 Compare
IXOPAYixopay.com 45/100 1 Subprocessor list 5 Data location stated, Certifications named, Uptime SLA with a figure, +2 Compare
Spreedlyspreedly.com 43/100 1 Public pricing 4 Data processing agreement, Uptime SLA with a figure, Notice before subprocessors change, +1 Compare
Corefycorefy.com 30/100 1 Public pricing 6 Data processing agreement, Status page with history, Certifications named, +3 Compare
Modulrmodulrfinance.com 26/100 1 Public pricing 6 Data processing agreement, Data location stated, Certifications named, +3 Compare
TrueLayertruelayer.com 26/100 1 security.txt (RFC 9116) 5 Data processing agreement, Data location stated, Uptime SLA with a figure, +2 Compare
Nomupaynomupay.com 22/100 1 Public pricing 6 Data processing agreement, Data location stated, Status page with history, +3 Compare
Silverflowsilverflow.com 22/100 1 security.txt (RFC 9116) 6 Data processing agreement, Data location stated, Certifications named, +3 Compare
Weavrweavr.io 22/100 1 Public pricing 6 Data processing agreement, Data location stated, Status page with history, +3 Compare
Payneteasypayneteasy.com 17/100 1 No third-party tracking before consent 7 Data processing agreement, Data location stated, Status page with history, +4 Compare
Voltvolt.io 4/100 1 security.txt (RFC 9116) 8 Data processing agreement, Data location stated, Status page with history, +5 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.