All Systems Operational

About This Site

Our home for real-time information on system performance and security. Here you'll find live and historical data on system performance. If there are any interruptions in service, a note will be posted here.

Websites Operational
Clearhaus (clearhaus.com) Operational
My Clearhaus (my.clearhaus.com) Operational
Payment Processing APIs Operational
Gateway API (gateway.clearhaus.com) Operational
Gateway API Test (gateway.test.clearhaus.com) Operational
Merchant API Operational
Production (merchant.clearhaus.com) Operational
Sandbox (merchant.test.clearhaus.com) Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Gateway API Availability
Fetching
Gateway API Response Time
Fetching
Merchant API Availability
Fetching
Merchant API Response Time
Fetching
Apr 25, 2025

No incidents reported today.

Apr 24, 2025

No incidents reported.

Apr 23, 2025

No incidents reported.

Apr 22, 2025

No incidents reported.

Apr 21, 2025

No incidents reported.

Apr 20, 2025

No incidents reported.

Apr 19, 2025

No incidents reported.

Apr 18, 2025

No incidents reported.

Apr 17, 2025

No incidents reported.

Apr 16, 2025

No incidents reported.

Apr 15, 2025

No incidents reported.

Apr 14, 2025

No incidents reported.

Apr 13, 2025

No incidents reported.

Apr 12, 2025

No incidents reported.

Apr 11, 2025
Resolved - Starting April 11th 11:00 CEST, approximately 8% of subsequent-in-series Mastercard transactions were rejected with status code 40416 by specific issuers. For the affected issuers, a significant percentage of subsequent-in-series are rejected. No Visa transactions nor non-series Mastercard transactions were affected by this.

On April 14th, the problem was noticed, and investigations have been ongoing together with Mastercard, an affected issuer, and our upstream provider.

On April 17th, the problem was confirmed to be an issue with our upstream provider.

On April 18th 22:00 CEST, our upstream provider released a fix.

On April 19th, we confirmed that the fix was working for PAN-initiated transactions, but the problem still persisted on token-initiated subsequent-in-series Mastercard authorizations. We continued to work with our upstream provider to get this fully fixed.

On April 24th 12:00 CEST, we managed to implement a workaround to mitigate the problems for token-initiated subsequent-in-series Mastercard authorizations. This fully resolved the impact of this incident.

We continue to work with our upstream provider to coordinate the removal of the workaround when a fix is in place.

Partners and merchants are recommended to retry both PAN- and token-initiated subsequent-in-series Mastercard authorizations that failed with 40416.

Apr 11, 09:00 UTC