Status page with history in Payment processing
A status page without past incidents tells you nothing about reliability.
- 17Published
- 31Vendors measured
- 55%Of those measured
- 2026-08-31Checked
55% here against 49% across every category we measure. Payment processing sits above the overall share for this criterion.
Back to Status page with history across all categories, or to Payment processing.
Published
A public status page with incident history.
No public status page found.
We reached at least one address for each of these vendors and none of them carried it. That is what we found at the addresses we checked, on the date we checked them, and not a statement about what the vendor has.
| Vendor | What we found |
|---|---|
| Braintree | 3 addresses checked |
| Checkout.com | 3 addresses checked |
| Lemon Squeezy | 3 addresses checked |
| Mangopay | 3 addresses checked |
| Maxio | 3 addresses checked |
| Nexi | 3 addresses checked |
| Novalnet | 3 addresses checked |
| Nuvei | 3 addresses checked |
| Rapyd | 3 addresses checked |
| Razorpay | 3 addresses checked |
| Square | 3 addresses checked |
| Stripe | 3 addresses checked |
| Worldline | 3 addresses checked |
| Zuora | 3 addresses checked |
Not measured
We could not look at these, or their robots.txt asks us not to. That says something about our measurement, not about them, and they are left out of the percentage above.
| Vendor | What we found |
|---|---|
| Computop | The vendor’s server blocked or rate-limited our crawler, so this was not measured. |
Found something we missed? Tell us and the next run picks it up.