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