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