Clearhaus had 10 outages in the last 2 years totaling 217h 53m of downtime — averaging 0.4 incidents per month.
There were 10 Clearhaus outages since October 31, 2024 totaling 217h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.
Between 18:18 and 18:53 UTC, settlement data was unavailable in the Merchant API due to a database outage. Gateway transaction processing was not affected at any point. We apologise for any inconvenience.
Since 2026-10-13 08:16 CEST, we have seen an increased rate of rejections on Visa credit and debit transactions (Visa Direct OCT and AFT, sent via the /credits and /debits endpoints), including refunds of debits. This concerns these transaction types only, not Visa credit cards or Visa debit cards. Regular Visa authorizations, captures, refunds and voids are unaffected, as are all Mastercard transactions. We are working with our upstream provider to investigate and will post an update when we know more.
Since 2026-10-13 12:30 CEST, Visa Direct OCT and AFT, sent via the /credits and /debits endpoints), including refunds of debits, has been working as normal. We are monitoring the situation in case it comes back.
We have monitored the situation and confirmed that error rates have normalized. This incident is now closed.
Starting 2026-10-09T02:00Z we are experiencing intermittent connectivity issues towards our upstream provider for authorizations and voids (and Mastercard debits and debit refunds). Automatic failover and recovery is greatly alleviating the impact, but we have observed error rates of 0.75 % between 2026-10-09T02:00Z – 2026-10-09T07:00Z. We are investigating and reaching out to our upstream provider to resolve. Captures and capture refunds and Visa debits and debit refunds are not impacted.
Since 06:36Z we locked all traffic to our upstream provider’s secondary data center where we saw a lower error rate of ~0.04 %. At 07:42Z we were informed that the problem was resolved by our upstream provider. Since 07:53Z we moved traffic back to the primary data center and have seen no further errors.
We are closing this incident as no errors have been observed since 06:36Z and since the problem is confirmed to be resolved. An average failure rate of 1.14 % was observed between 2026-10-09T04:01Z and 2026-10-09T06:35Z (of when the first and last error occurred) with a peak error rate within a minute of 31 %. Additionally, we also observed a small collection of errors 2026-10-08T22:32Z – 2026-10-08T22:41Z at an average failure rate of ~11 %. Correction on affected transaction types! Authorizations, voids, capture refunds and Mastercard credits were affected. Remaining transaction types (captures, debits, debit refunds, and Visa credits) were not affected.
Between 2026-08-27T00:30:35Z and 2026-08-27T00:48:01Z, all Visa authorizations failed with status code 40400, "backend problem". A few Visa transactions were failing already starting 2026-08-27T00:25:25Z. Mastercard authorizations along with all captures, refunds, voids and credits were unaffected. We have seen no further connectivity errors since 2026-08-27T00:48:01Z. Failed authorizations were not charged and can be retried. We are working with our upstream provider to determine the root cause and to prevent similar issues in the future.
Since 2026-08-07 00:00 CEST, we’ve seen a rise in rejections of Credit transactions by Mastercard. Credit transactions using EUR as currency are not affected. We are reaching out to our upstream provider and will post another update once we have more information. Regular authorizations and all other transaction types are unaffected.
We have now confirmed with our upstream provider that all non-EUR Credits are currently being rejected by Mastercard, due to a configuration change between Clearhaus, upstream provider and Mastercard. Our upstream provider are working on a rollback, and believe to be able to complete this during the night.
Since 2026-08-12 00:05 CEST, approval rate of Mastercard Credits are back to normal. We are still working with the upstream provider to investigate the core issue, and ensure continued operations. Regular authorizations and all other transaction types remain unaffected.
We are currently investigating the issue. Gateway transaction processing is not affected.
Transactions available again in Merchant API This issue has been resolved. Transactions are now available in the Merchant API and the service is operating normally. Gateway transaction processing was not affected at any point. We apologise for any inconvenience.
This incident has been resolved.
The /settlements endpoint in Merchant API was unavailable and returning 500 between 2026-02-03T08:55Z - 2026-02-03T09:15Z. The incident was resolved with no lingering issues.
Due to a service provider we are experiencing degraded performance in the Merchant API. This does not affect our ability to process transactions.
After taking remedial action, performance of the degraded components has returned to normal during the course of the week. Additionally, we have taken measures to improve visibility into the affected systems in order to strengthen our infrastructure and prevent similar events in the future. We are in contact with the service provider to continue to investigate the root cause of the issue and explore additional measures to increase the robustness of our systems.