Clearhaus status
Clearhaus status history
- Operational
- Degraded
- Partial outage
- Major outage
- Community report
Community reports
No community reports yet
No users have reported issues with this provider yet.
Official incidents
in the last 30 days
-
Visa Credit and Debit transactions failing
Since 2026-10-14 07:15 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. Unfortunately, we see the same underlying issue as we did yesterday, and we are in constant communication with Visa trying to resolve the issue fully.
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.
A hotfix was deployed at 12:03 CEST, and the affected service is performing normally again. We are monitoring the situation and will post an update once we have confirmed the issue is resolved.
We deployed a stable fix at 2026-10-14 14:09 CEST which we have been monitoring and confirmed to be successful. We are still in communication with Visa to understand the root cause on the Visa side, but as there is no more impact of this incident, it will hereby be considered resolved.
During the incident period 07:15–12:03 CEST, 86 % of Visa credits or debits received status code 50000.
Impacted merchants will receive direct communication from us to clarify the actual state of the impacted transactions that received status code 50000 and a status message indicating “status unknown”. -
Settlements unavailable in Merchant API
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. -
Visa Credit and Debit transactions failing
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. -
Connectivity issue towards upstream
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.
Services
No currently affected Clearhaus services
There are no reported issues with this provider’s services in the last 24 hours.
-
Clearhaus (clearhaus.com)
Operational -
My Clearhaus (my.clearhaus.com)
Operational -
Gateway API (gateway.clearhaus.com)
Operational -
Gateway API Test (gateway.test.clearhaus.com)
Operational -
Production (merchant.clearhaus.com)
Operational -
Sandbox (merchant.test.clearhaus.com)
Operational
About Clearhaus status page
- Monitoring since Oct 2026
- 6 services and components tracked
- 54 incidents total
- Last updated: Oct 25, 2026
Saw an error in description or reports for Clearhaus?
Frequently asked questions
Quick answers for payment teams and merchants investigating an incident. Firemap explains the evidence; it does not diagnose your merchant account.
No. Clearhaus reports normal operation on its official status page. Firemap last read the status page today at 12:05 UTC.
They are the four status levels Firemap uses for Clearhaus, the same scale most status pages use. Operational means everything works normally. Degraded means the services work, but some are slower or return more errors than usual. Partial outage means some services, regions or payment methods are unavailable, while the rest still work. Major outage means a key service is unavailable for most customers. When Clearhaus publishes it, each official incident also shows its stage: Investigating, Identified, Monitoring or Resolved. In the status history, each day shows its incidents by level, and a purple strip marks days with community reports.
Not on its own. Firemap shows what Clearhaus publishes about its platform, not the state of your account. An incident may affect only some regions, payment methods or integrations. Check your own transaction logs and decline codes, and contact Clearhaus support with specific transaction IDs if you see failures.
From the official Clearhaus status page, once Firemap has connected it. Firemap then reads the page automatically every few minutes and records each status change and incident Clearhaus publishes there. Community reports come from PayAtlas users and appear in their own block; they do not change the official status.
They come from different sources. Official incidents are what Clearhaus has confirmed, and providers often post one only after the first failures. Community reports come from users and can show a problem earlier, but it may be local: one bank, one country or one integration. Treat reports without an official incident as an early signal, not a confirmed outage.
Start with your own data: error rates, decline codes and response times by payment method, card scheme and country. Compare them with the scope of the incident on the status page. Make sure the backup provider supports the same methods and currencies, move a small share of traffic first, and switch back once the incident is resolved and your metrics recover.
It shows how old the data is instead of guessing. When Firemap has a status for Clearhaus, the top of this page shows when Firemap last read the official status page, for example “Updated 2h ago”. If a check fails, the page keeps the last status Firemap read, with its time. If there has been no reading for 7 days, or Firemap has no working status page for Clearhaus, the page shows “Status page not connected” instead of a status. The status history counts incidents, so a day without incidents stays green even if the page could not be read that day.
Firemap tracks the official status pages of payment providers listed on PayAtlas. It checks each page automatically and stores every incident with its start time and, once resolved, its end time. When Firemap has data for Clearhaus, this page shows 30 days of status history, every official incident that is still open and the resolved incidents that started in the last 30 days. Community reports from the last 30 days are shown for every provider.
Firemap can confirm only what Clearhaus has published on its status page: the current status, incidents with their start time and, once resolved, end time, and how long the page has been tracked. It cannot confirm the impact on a specific merchant, transaction or region unless Clearhaus says so, and it cannot see problems the provider has not reported.
PayAtlas Stack
Manage Your Payment Stack in One Place
Save the providers you work with and get instant access to their status, coverage, insights, comparisons, and recommended alternatives whenever you need them.
- Free monitoring
- 5 minutes setup
