Alternatives to IXOPAY
Other Payment orchestration vendors we measure, sorted by how much they publish that IXOPAY does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 21 that differ from IXOPAY on at least one criterion we measured for both. Public transparency score, not a product or security rating.
IXOPAY has 6 gaps in what we could measure: Data location stated, Public pricing, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, Named privacy contact. The column “publishes and IXOPAY does not” is the one that closes them.
| Vendor | Score | Publishes, and IXOPAY does not | IXOPAY publishes, and they do not | |
|---|---|---|---|---|
| Spreedlyspreedly.com | 43/100 | 4 Data location stated, Public pricing, Certifications named, +1 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | Compare |
| Marqetamarqeta.com | 39/100 | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | Compare |
| Corefycorefy.com | 30/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | Compare |
| BR-DGEbr-dge.to | 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 |
| Payrailspayrails.com | 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 |
| Primerprimer.io | 26/100 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | Compare |
| Nomupaynomupay.com | 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.io | 22/100 | 3 Public pricing, HTTPS enforced with HSTS, Named privacy contact | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | Compare |
| Increaseincrease.com | 30/100 | 2 Public pricing, HTTPS enforced with HSTS | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | Compare |
| Modulrmodulrfinance.com | 26/100 | 2 Public pricing, HTTPS enforced with HSTS | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | Compare |
| Juspayjuspay.in | 13/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | Compare |
| Paydockpaydock.com | 13/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 4 Data processing agreement, Subprocessor list, Status page with history, +1 | 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.