Transparency alternatives to Yapily
Other Payment orchestration vendors we measure, sorted by how much we found at them and not at Yapily. This is a comparison of disclosure, not of features or fitness.
12 shown of 33 that differ from Yapily on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Yapily has 9 gaps in what we could measure: Data processing agreement, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116). The column “Found there, not found at Yapily” is the one that closes them.
| Vendor | Score | Found there, not found at Yapily | Found at Yapily, not found there | |
|---|---|---|---|---|
| Yunoy.unoSee also Transparency alternatives to Yuno | 65/100 | 6 Data processing agreement, Data location stated, Status page with history, +3 | 1 Subprocessor list | Compare |
| Spreedlyspreedly.comSee also Transparency alternatives to Spreedly | 43/100 | 5 Data location stated, Status page with history, Public pricing, +2 | 3 Subprocessor list, Notice before subprocessors change, Named privacy contact | Compare |
| TrueLayertruelayer.comSee also Transparency alternatives to TrueLayer | 39/100 | 5 Data location stated, Status page with history, Certifications named, +2 | 3 Subprocessor list, Notice before subprocessors change, Named privacy contact | Compare |
| Rebillyrebilly.comSee also Transparency alternatives to Rebilly | 57/100 | 4 Data processing agreement, Public pricing, Uptime SLA with a figure, +1 | 1 Named privacy contact | Compare |
| Unitunit.coSee also Transparency alternatives to Unit | 39/100 | 4 Data location stated, Status page with history, Certifications named, +1 | 2 Subprocessor list, Notice before subprocessors change | Compare |
| Increaseincrease.comSee also Transparency alternatives to Increase | 30/100 | 4 Status page with history, Public pricing, HTTPS enforced with HSTS, +1 | 3 Subprocessor list, Notice before subprocessors change, Named privacy contact | Compare |
| Payrailspayrails.comSee also Transparency alternatives to Payrails | 35/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 2 Subprocessor list, Notice before subprocessors change | Compare |
| Corefycorefy.comSee also Transparency alternatives to Corefy | 30/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 3 Subprocessor list, Notice before subprocessors change, Named privacy contact | Compare |
| Marqetamarqeta.comSee also Transparency alternatives to Marqeta | 26/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 2 Subprocessor list, Notice before subprocessors change | Compare |
| Modulrmodulrfinance.comSee also Transparency alternatives to Modulr | 26/100 | 3 Status page with history, Public pricing, HTTPS enforced with HSTS | 3 Subprocessor list, Notice before subprocessors change, Named privacy contact | Compare |
| IXOPAYixopay.comSee also Transparency alternatives to IXOPAY | 45/100 | 2 Data processing agreement, Status page with history | 1 Named privacy contact | Compare |
| BR-DGEbr-dge.toSee also Transparency alternatives to BR-DGE | 26/100 | 2 Data location stated, HTTPS enforced with HSTS | 2 Subprocessor list, Notice before subprocessors change | 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.