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