Is Clearhaus down?

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.

On 2026-08-06 between 12:52 and 16:56 UTC (4h 04m), all Google Pay transactions failed with status code 40000, "Google Pay input error, no valid signature of intermediate key". No other payment methods, including Apple Pay and regular card transactions, were affected. We are improving our alerting in this area to prevent future regressions.

### What happened? A configuration change caused Google Pay transactions to fail. The change was made to clean up configuration inconsistencies between environments. Google Pay had an implicit dependency on one of these configurations. Before moving traffic to a new deployment, we always run automated test transactions. However, Google Pay is not tested automatically but only per need, as it is a convoluted payment method and difficult to automate. Since this deployment did not include any changes to Google Pay and was not expected to affect it, no additional effort was made to test Google Pay. ### Why were we slow to detect it? Google Pay has significantly less traffic than other payment methods so it hits below our alerting threshold, and because of this we were slow to notice the issue. ### Preventive actions * We have reviewed the remaining configuration for similar implicit dependencies and found none. * We have improved our alerting \(see below\). #### Improved alerting We have improved our alerting to catch failures affecting a small share of traffic. To avoid a significant number of false positives, we’ve done thorough analysis and backtesting to create advanced alerts that check to confirm that errors don't only happen on individual merchant accounts or for individual issuers. This allows us to be alerted per payment method — even for smaller ones like Google Pay — but also per transaction type — even for smaller ones like credits. With these new alerts in place we would have been alerted to the outage within, at most, 15 minutes.

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.