THIS IS A SCHEDULED EVENT May <var data-var='date'>30</var>, <var data-var='time'>18:00</var> - <var data-var='time'>22:00</var> UTC May <var data-var='date'>23</var>, <var data-var='time'>20:31</var> UTC Scheduled - We will be conducting scheduled maintenance on our databases. This does not affect our ability to process transactions nor to settle merchants.

Merchant API: Unavailability due to database maintenance

Mar <var data-var='date'>18</var>, <var data-var='time'>04:18</var> UTC Completed - The scheduled maintenance has been completed. Mar <var data-var='date'>18</var>, <var data-var='time'>03:48</var> UTC Verifying - Verification is currently underway for the maintenance items. Mar <var data-var='date'>18</var>, <var data-var='time'>03:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar <var data-var='date'> 6</var>, <var data-var='time'>09:29</var> UTC Scheduled - Due to database maintenance the transaction gateway will be unavailable in up to 2 periods of 10-15 seconds each. All transaction types are affected.

Transaction gateway: Unavailability due to database maintenance

Mar <var data-var='date'>17</var>, <var data-var='time'>04:37</var> UTC Completed - The scheduled maintenance has been completed. Mar <var data-var='date'>17</var>, <var data-var='time'>03:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar <var data-var='date'> 6</var>, <var data-var='time'>09:28</var> UTC Scheduled - Due to database maintenance the transaction gateway will be unavailable in up to 4 periods of 10-15 seconds each. All transaction types are affected.

Feb <var data-var='date'> 4</var>, <var data-var='time'>12:21</var> UTC 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.

Settlements briefly unavailable in Merchant API

Dec <var data-var='date'>22</var>, <var data-var='time'>10:57</var> UTC Resolved - We are closing this incident as no error has been observed since 9:23 UTC and since our upstream provider confirms that service has been restored. An average failure rate of 8.98 % was observed between 07:48:49 UTC and 09:23:30 UTC (of when the first and last error occurred). Authorizations and voids were affected. Captures, capture refunds, debits and debit refunds were unaffected. Mastercard credits were affected. Visa credits were unaffected. Dec <var data-var='date'>22</var>, <var data-var='time'>09:45</var> UTC Monitoring - We saw fluctuations of success rates between 75 % and 100 % until 9:23 UTC and have seen no connectivity errors since. We continue to monitor the situation. Dec <var data-var='date'>22</var>, <var data-var='time'>08:55</var> UTC Investigating - Starting 07:48 UTC we are seeing timeouts and general connectivity issues towards both the primary and secondary data centres of our upstream provider. Authorization success rates fluctuate between ~50 % and 100 % on the primary data centre and worse on the secondary. We are in contact with our upstream provider who have confirmed that they are having a wider incident impacting several of their systems. We will update you as soon as we have more information to share, and no later than in 1 hour. Authorizations and voids are affected. Captures, capture refunds, debits and debit refunds are unaffected. Mastercard credits are affected. Visa credits are unaffected.

Connectivity issue towards upstream

Apr <var data-var='date'>11</var>, <var data-var='time'>09:00</var> UTC 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.

Some subsequent recurring transactions fail upstream

Mar <var data-var='date'> 2</var>, <var data-var='time'>04:30</var> UTC Resolved - On the night of 2025-03-02 we saw timeouts and connectivity issues towards our upstream provider OmniPay. Mostly we’ve been able to route traffic to a healthy data-center, but between 2025-03-02T05:27Z and 2025-03-02T05:35Z, all data-centers were not responding. The incident was resolved within 8 minutes, and we have not seen any further connectivity issues since then. We are actively working with our upstream provider to determine how similar issues can be prevented in the future when they do network updates.

Nov <var data-var='date'>20</var>, <var data-var='time'>01:00</var> UTC Resolved - Between 2024-11-20T02:27:09Z and 2024-11-20T02:40:09Z we experienced connectivity issues towards our upstream provider, reaching up to 26% error rate at the peak of the incident. Only a few transactions were affected but we are posting this update for transparency. The incident was resolved within 14 minutes, and we have not seen any further connectivity issues since then.

Nov <var data-var='date'> 8</var>, <var data-var='time'>09:16</var> UTC Resolved - 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. Oct <var data-var='date'>31</var>, <var data-var='time'>04:09</var> UTC Investigating - Due to a service provider we are experiencing degraded performance in the Merchant API. This does not affect our ability to process transactions.

Merchant API: Degraded performance

Oct <var data-var='date'> 3</var>, <var data-var='time'>21:30</var> UTC Resolved - At 2024-10-03T11:26Z a warning triggered an investigation of an increase in the error rate for authorizations. The investigation showed that we were receiving a subtle amount of declines from issuers reasoned with “format error” starting 2024-10-02T05:45Z. These rejects are normal and have numerous times shown issuers to be misbehaving – which is why we have a non-zero threshold that must be met before we become aware. Together with the “format error” must be an identification of the malformatted field. This led us to identify an issue with an update we applied during 2024-10-02 resulting in AUD authorizations to be consistently declined in the time span 2024-10-02T19:55Z - 2024-10-03T17:05Z. This, however, only explained a minority of the declines. The remaining declines indicated a field that we have never populated, however, since our investigation indicated it to be an issue across multiple issuing banks, we quickly implemented a change to populate the field. Both a fix for AUD and for populating the extra field were deployed, and they turned out to fix both issues. The field population issue caused sporadic declines in the time span 2024-10-02T05:45Z - 2024-10-03T19:08Z. In summary, the two issues above caused an average 0.15 percentage point drop in approval rate in the time span 2024-10-02T05:45Z - 2024-10-03T19:08Z. We will work hard to identify how the AUD error could happen and will ensure to introduce checks to avoid a similar error to happen in the future. We will also try to work with issuers to identify the cause of the rejects based on the previously unpopulated field.

Marginally increased error rate for Mastercard authorizations

Sep <var data-var='date'>12</var>, <var data-var='time'>20:39</var> UTC Resolved - Our upstream partner has resolved their issue and our monitoring shows that the connection has been stable and without problems since our last update. We will investigate mitigating actions and the root cause of this incident and will publish a postmortem once we have a complete overview from the upstream partner. To summarize, we saw on average around 90 % of authorizations impacted during the time period 2024-09-12T03:30 - 2024-09-12T11:45 UTC. All impacted authorizations were responded with status code 50000 by our gateway API for transaction processing. We sincerely regret the inconvenience this serious incident has caused! Sep <var data-var='date'>12</var>, <var data-var='time'>12:04</var> UTC Monitoring - We have seen a significant increase in approval rates and the connectivity is now back to normal. Due to the severity of this issue and the previous sudden change in approval rate we are still actively monitoring this situation. Sep <var data-var='date'>12</var>, <var data-var='time'>11:51</var> UTC Update - We are again seeing an improvement in approval rate starting 11:46 UTC and are continuing to monitor the situation as we previously have seen such improvement temporarily. Sep <var data-var='date'>12</var>, <var data-var='time'>10:47</var> UTC Update - We are awaiting further communication from our provider. We are actively monitoring the situation. There is no ETA for when this issue is resolved. We will update as soon as we know more. Sep <var data-var='date'>12</var>, <var data-var='time'>09:06</var> UTC Update - We saw an improvement in approval for a short period of time from around 08:47 UTC to 08:59 UTC. Unfortunately, this has worsened again, and we are back on approval rates below 15 %. Sep <var data-var='date'>12</var>, <var data-var='time'>08:41</var> UTC Update - Unfortunately, we still see very high failure rates on authorizations. Our upstream provider is still trying to mitigate this critical incident. We are seeing examples where amounts are being reserved on cardholders' accounts despite the authorization failing. Therefore we recommend that subsequent-in-series recurring and unscheduled (e.g. subscriptions) are not attempted until after this incident is resolved. Furthermore, we are exploring options to potentially release these reservations. Sep <var data-var='date'>12</var>, <var data-var='time'>06:34</var> UTC Identified - We have identified that the issue is with our upstream provider. We have attempted mitigating actions but unfortunately with very limited impact. We are still seeing very low approval rates that fluctuates approximately from 0 % to 15 %. Our upstream provider is trying to resolve the connectivity issue. Sep <var data-var='date'>12</var>, <var data-var='time'>05:05</var> UTC Update - Our upstream provider has confirmed and is aware of a connectivity issue. Currently almost all authorizations, voids and Mastercard credits are impacted. Sep <var data-var='date'>12</var>, <var data-var='time'>04:42</var> UTC Investigating - Since 2024-09-12T03.39Z we have observed connectivity issues towards an upstream provider. We have reached out and are investigating with the provider.

Sep <var data-var='date'> 2</var>, <var data-var='time'>08:18</var> UTC Resolved - The cause of this incident was that an issuer/Visa disabled the impacted BINs although they were actively being used. Luckily, issuer/Visa succeeded in reenabling the impacted BINs over the weekend. This has propagated through systems, and made both new transactions and previously impacted transactions able to clear. After careful analysis we can confirm that all previously impacted transactions are now cleared successfully and they are also included in settlements. Aug <var data-var='date'>30</var>, <var data-var='time'>19:46</var> UTC Update - Visa has identified that the BINs involved in clearing failures are: 414865, 432921, 435786, 443254, 449269, 451143, 451349, 455853, 455854, 457101, 460312, 457154, 461061, 462003, 464254, 479870, 481686, 494109, 457153, and 457154. Aug <var data-var='date'>30</var>, <var data-var='time'>13:34</var> UTC Identified - Some captures and refunds for card numbers starting with 457153 and tokens that are generated from such card numbers failed clearing this night even though Clearhaus accepted the transactions. There are two consequences for such impacted captures and refunds: 1. They do not yet appear on cardholders’ bank accounts; this is especially unfortunate for refunds. 2. They are not yet being settled on merchants’ accounts; this is especially unfortunate for captures. No action from you is required or recommended; this incident is for your information. Please notice that authorizations on both impacted cards and tokens appear to be functioning normally. Though, 3-D Secure authentications are also impacted. Transactions on any other card are not impacted! Visa has acknowledged the issue and is working with the bank that issues these cards and tokens to ensure that clearings can again go through. We await further updates from Visa and also await the issuer to resolve the problem and do expect these clearings to eventually go through. We will keep you updated whenever there is news to share. We intend to update you no later than 2024-09-03T12:00Z.

Visa DK issuing BIN6 457153 partly dysfunctional

Aug <var data-var='date'>21</var>, <var data-var='time'>22:16</var> UTC Completed - The scheduled maintenance has been completed. Aug <var data-var='date'>21</var>, <var data-var='time'>21:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Aug <var data-var='date'>12</var>, <var data-var='time'>13:29</var> UTC Scheduled - We will be conducting scheduled maintenance on our database system on 2024-08-21 from approximately 21:00 to 23:00 UTC. During the maintenance, you may experience slower than usual performance when accessing My Clearhaus and Merchant API, and some requests to the latter may fail for a short period. We apologize for any inconvenience this may cause. Additionally, please be aware that transaction data will be delayed in both My Clearhaus and Merchant API during this maintenance window. We anticipate that the maintenance will last for approximately 2 hours, and we will do our best to complete the process as quickly and efficiently as possible. This does not affect our ability to process transactions nor to settle merchants.

Merchant API: Partial unavailability due to database maintenance

Aug <var data-var='date'> 2</var>, <var data-var='time'>09:21</var> UTC Resolved - This incident has been resolved. Aug <var data-var='date'> 2</var>, <var data-var='time'>09:21</var> UTC Update - Our monitoring shows all Visa transactions are functional, and we therefore close this incident. The time window of failures lasted from 2024-08-02T05:59Z till 2024-08-02T08:13Z. Aug <var data-var='date'> 2</var>, <var data-var='time'>08:45</var> UTC Monitoring - Visa has announced that the service disruption is fully mitigated and we can positively confirm that the impacted Visa transactions are now being processed again. We will continue to monitor the error rates. Aug <var data-var='date'> 2</var>, <var data-var='time'>07:27</var> UTC Update - While we are awaiting an update from Visa we have to the best of our ability confirmed that transactions are not being processed upstream; thus, retrying a transaction is not expected to result in multiple processing if retried when this issue is resolved. However, we will advise you to be careful especially when retrying credit transactions. Aug <var data-var='date'> 2</var>, <var data-var='time'>07:11</var> UTC Identified - At 2024-08-02T05:59Z we started noticing consistent failures in communication with Visa for both credit and debit transactions; neither Mastercard nor other Visa transaction types (e.g. authorizations and captures) are impacted. Visa has announced a service disruption, and we will keep you updated as we get information to share from Visa.

Transaction gateway: Visa credit and debit transaction outage

Apr <var data-var='date'>26</var>, <var data-var='time'>11:13</var> UTC Resolved - The hotfix has been replaced with a proper solution that has been monitored for the last couple of hours. We are hereby closing this incident. Apr <var data-var='date'>25</var>, <var data-var='time'>18:23</var> UTC Update - All impacted authorizations have now been voided. These voids are visible via my.clearhaus.com. We expect to update and close this incident when we have tested and applied a proper solution in the coming days. Apr <var data-var='date'>25</var>, <var data-var='time'>16:51</var> UTC Update - A significant amount of the authorizations that we responded with 50000 was approved upstream. We are currently attempting to void these approved authorizations and expect this to be completed within the next few hours. We will update this incident when the voids are completed. Apr <var data-var='date'>25</var>, <var data-var='time'>11:52</var> UTC Monitoring - The issue started 2024-04-25T10:35:00Z and ended 2024-04-25T11:48:00Z when we applied a hotfix. Apr <var data-var='date'>25</var>, <var data-var='time'>11:03</var> UTC Investigating - We are currently seeing an increase in declined Visa Authorizations and are currently investigating.

Transaction gateway: Declined Visa authorizations

Feb <var data-var='date'>20</var>, <var data-var='time'>20:00</var> UTC Completed - The scheduled maintenance has been completed. Feb <var data-var='date'>20</var>, <var data-var='time'>19:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb <var data-var='date'> 6</var>, <var data-var='time'>14:38</var> UTC Scheduled - Scheduled maintenance will take place on 2024-02-20 from 19:00 to 20:00 UTC. During this time the Merchant API will be partially unavailable. Transaction processing and merchant settlements are not affected.

Jan <var data-var='date'>15</var>, <var data-var='time'>14:05</var> UTC Resolved - The missing references have been brought back. The affected captures, refunds and voids are in the time span 2024-01-08T12:33:47Z - 2024-01-13T10:16:38Z. Jan <var data-var='date'>12</var>, <var data-var='time'>09:57</var> UTC Identified - Since 2024-01-08 references have been missing on some captures, refunds and voids in the Merchant API and on my.clearhaus.com. We apologize for the inconvenience and are doing our best to quickly bring them back. Transaction processing is not affected.

Merchant API and my.clearhaus.com: Missing references

Nov <var data-var='date'> 3</var>, <var data-var='time'>08:22</var> UTC Resolved - We experienced an increased amount of declines on authorizations, voids and Mastercard credits with status code 40400 backend problem in the time span 2023-11-03T00:59:31Z to 2023-11-03T01:09:38Z due to problems confirmed by an upstream provider. Neither captures, refunds, debits, debit refunds nor Visa credits were affected.

Increased amount of declines

Oct <var data-var='date'>26</var>, <var data-var='time'>20:46</var> UTC Resolved - We have worked with Visa to resolve the issue. Some authorization responses in the affected timespan did not include Visa transaction IDs (TIDs). Should any client require the missing TIDs, do not hesitate to reach out. If missing TIDs do not pose a problem, no action is required. We apologize for any inconvenience. Oct <var data-var='date'>13</var>, <var data-var='time'>20:15</var> UTC Update - Our upstream service provider has confirmed the issue is a result of a system upgrade on their end, and they are working on a resolution. Some subsequent-in-series authorizations may still fail for the time being, and we ask clients to postpone these authorizations until the issue has been resolved. Fortunately, very few authorizations are affected by this issue. Oct <var data-var='date'>13</var>, <var data-var='time'>15:46</var> UTC Identified - We have identified the issue and have managed to contain it to some degree. It is now the case that some attempts at creating a subsequent-in-series Visa authorization referencing a previous authorization created in the time span 2023-10-13T09:49:16Z - 2023-10-13T15:08:48Z might fail. We are working towards complete resolution. Oct <var data-var='date'>13</var>, <var data-var='time'>15:00</var> UTC Investigating - Some attempts at creating a subsequent-in-series Visa authorization referencing a previous authorization created after 2023-10-13T09:49:16Z are currently failing.

Transaction gateway: Failure for some subsequent-in-series Visa authorizations

Oct <var data-var='date'>14</var>, <var data-var='time'>09:42</var> UTC Completed - The scheduled maintenance has been completed. Oct <var data-var='date'>14</var>, <var data-var='time'>09:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Sep <var data-var='date'>22</var>, <var data-var='time'>09:11</var> UTC Scheduled - Due to network maintenance we expect a few interruptions in the Merchant API.

Merchant API: Partial unavailability

Oct <var data-var='date'> 3</var>, <var data-var='time'>07:44</var> UTC Resolved - We noticed at 2023-10-03T04:32:30Z that our DNS provider had issues. They identified and were able to resolve the issue by 2023-10-03T05:25Z. Since the TTL is one hour on the DNS records, the immediate impact of this issue is expected to be limited. However, during the period of the DNS issue, clients may have experienced sporadic connectivity problems or delays in accessing our services depending on their reliance on DNS.

DNS issue

Sep <var data-var='date'>22</var>, <var data-var='time'>12:15</var> UTC Resolved - All affected transactions have been settled and the issue is resolved. Aug <var data-var='date'>18</var>, <var data-var='time'>13:34</var> UTC Investigating - We are investigating an issue on Mastercard transactions for the period between 2023-08-09T19:00Z and 2023-08-10T19:00Z. Only captures, refunds and credits are impacted whereas neither authorizations nor voids are impacted. Transactions appear successful in Clearhaus’ systems — also with respect to bookkeeping and payouts to merchants. There is no impact from a merchant’s perspective; only via clearing transactions not being effectuated on their cardholders’ accounts. Our investigation so far confirms that: - A majority of captures from 2023-08-10T09:00Z to 2023-08-10T14:00Z are impacted. - A majority of refunds from 2023-08-09T19:00Z to 2023-08-10T14:00Z are impacted. - All captures and refunds from 2023-08-10T14:00Z to 2023-08-10T19:00Z are impacted. - All credits from 2023-08-09T19:00Z to 2023-08-10T19:00Z are impacted. It is greatly important to note that this update is solely for informational purposes, as no action is required from any other party than Clearhaus and our upstream provider. We have identified the impacted transactions and are working with our upstream provider and Mastercard on a resolution. Since transactions appear successful in Clearhaus systems, we expect to be able to resolve the issue without your involvement. If you need to do anything, we will reach out directly.

Mastercard clearings missing

Jul <var data-var='date'> 3</var>, <var data-var='time'>19:56</var> UTC Resolved - No further timeouts have been observed. We have been in contact with our service provider and confirmed all systems to be operational. We apologize for the inconvenience. Jul <var data-var='date'> 3</var>, <var data-var='time'>19:04</var> UTC Investigating - From 2023-07-03T18:30:13Z to 18:48:41Z today, we saw an intermittent increase in timeouts towards our upstream service provider affecting authorizations and voids. Mastercard credits were also impacted. Other transactions like captures and refunds were not impacted. The issue appears to have subsided, but we will continue to monitor the situation and post another announcement should the issue reemerge.

Transaction gateway: Intermittent service disruption for authorization transactions

Jun <var data-var='date'>16</var>, <var data-var='time'>09:55</var> UTC Resolved - In collaboration with Mastercard we are investigating and exploring the options for cleaning up the remaining inconsistencies. Fortunately only very few merchants are impacted, so further communication will happen directly with the affected merchants; they should expect an update no later than 2023-06-19T16:00:00Z. Therefore, we mark this incident as resolved here. We have run extra checks to confirm that the fix of inconsistencies for the impacted Mastercard credits from 2023-06-07T08:00:00Z till 2023-06-09T15:00:00Z is successful. We are deeply sorry about the inconvenience this incident has caused to partners, merchants and cardholders. We strive to do our best so we will surely use the learnings we have had over the last week to improve our systems to help avoid similar consequences in the future. Jun <var data-var='date'>15</var>, <var data-var='time'>09:41</var> UTC Update - We can positively confirm that the inconsistency has been fixed for the impacted Mastercard credits from 2023-06-07T08:00:00Z till 2023-06-09T15:00:00Z whereas the inconsistency could not be resolved for the transactions in the beginning of the interval (from 2023-06-06T19:00:00Z till 2023-06-07T08:00:00Z). We are further investigating the remaining inconsistencies and will again be working with Mastercard to resolve this. Please expect an update on the resolution of the remaining inconsistencies no later than 2023-06-16T10:00:00Z. Still, Mastercard credits for merchant accounts with MCC 7800, 7801, 7802, 7994, 7995 or 9406 created since processing was resumed Monday are working without issues. Jun <var data-var='date'>14</var>, <var data-var='time'>14:23</var> UTC Update - We have been working with Mastercard (and have also in parallel run tests) to resolve the inconsistency for the impacted Mastercard credit transactions from 2023-06-06T19:00:00Z till 2023-06-09T15:00:00Z. Preparations for a final solution are happening today, and the results should be available to us tomorrow after a nightly run at Mastercard. Thus, please expect an update on the resolution of the inconsistency no later than 2023-06-15T10:00:00Z. We have been following the status of Mastercard credits for merchant accounts with MCC 7800, 7801, 7802, 7994, 7995 or 9406 that have been processed since processing of these transactions was resumed Monday, and are happy to report that we see no errors or inconsistencies. Jun <var data-var='date'>12</var>, <var data-var='time'>14:23</var> UTC Monitoring - We can confirm that our solution was successful and are thus resuming processing of the impacted Mastercard credit transactions. Please notice that we are still researching how to resolve the inconsistency of approved credits processed from 2023-06-06T19:00:00Z till 2023-06-09T15:00:00Z. Please expect an update on this no later than 2023-06-14T16:00:00Z. Jun <var data-var='date'>10</var>, <var data-var='time'>22:13</var> UTC Update - The solution is developed in testing, reviewed and tested, and will undergo testing for production readiness. If everything goes as planned, we will run production tests through Mastercard systems Sunday 2023-06-11, and will need to wait for the result till Monday 2023-06-12. No later than 2023-06-12T16:00:00Z will we provide an update regarding our confidence in the solution. If we are confident that our solution is correct, we will resume processing together with the update, otherwise we will most likely need to postpone processing of the impacted Mastercard transactions for another 24 hours. Thus, expect the next update no later than 2023-06-12T16:00:00Z. Jun <var data-var='date'> 9</var>, <var data-var='time'>22:31</var> UTC Update - We have been looking into this issue throughout the day and will continue to do so over the weekend. A solution for the impacted transactions is under development and has been partially submitted for internal review. The solution is currently being tested. Progress will be slightly slower over the weekend, but we are working on resuming processing of the impacted Mastercard credit transactions as soon as possible. You can expect the next update before 2023-06-11T00:00:00Z. Jun <var data-var='date'> 9</var>, <var data-var='time'>14:55</var> UTC Identified - We can confirm that this incident is relevant only for Mastercard credits on merchant accounts with MCC 7800, 7801, 7802, 7994, 7995 or 9406. Impacted transactions are currently being actively declined from our end with status code 50000 (Clearhaus error). The focus is on finding a solution to resume processing, and we are actively working to achieve this. The time frame for a solution is unfortunately not yet known. You can expect an update before midnight UTC. After processing has resumed we will detail and communicate a plan for resolving the inconsistency of approved credits processed from 2023-06-06T19:00:00Z till 2023-06-09T15:00:00Z. We will explore all options to most effectively (and conveniently to you) handle such inconsistencies. At this stage, we are not yet able to fully investigate the state of these transactions in Mastercard systems. Further updates also in this regard will be posted here as soon as we have them. The impact of the inconsistency is that an approved credit transaction for an account with above-listed MCCs appears as successful to the partner/merchant but may appear as failed to the cardholder. Please be aware of this when handling cases from cardholders. Jun <var data-var='date'> 9</var>, <var data-var='time'>12:25</var> UTC Investigating - We are noticing problems processing Mastercard credits for specific merchant accounts, namely those with MCC 7800, 7801, 7802, 7994, 7995 or 9406. Early investigation shows that such transactions since 2023-06-06T19:00:00Z have failed even though our systems returned with status code 20000 (approved). Further investigation will be ongoing in the following hours. All other transaction processing is not impacted.

Mastercard credits failing for specific merchant accounts

Jun <var data-var='date'>12</var>, <var data-var='time'>17:41</var> UTC Resolved - Approval rates are back to normal as of 2023-06-12T14:21:00Z. Jun <var data-var='date'>12</var>, <var data-var='time'>14:39</var> UTC Monitoring - Today after 11:00Z we started seeing low approval rates for all live Mastercard transactions (authorizations and credits). Mastercard are having issues with multiple systems, so unfortunately there is nothing we can do other than to monitor the state.

Is Clearhaus down?

Clearhaus status is UP

Lastest published events

Merchant API: Unavailability due to database maintenance

Transaction gateway: Unavailability due to database maintenance

Transaction gateway: Unavailability due to database maintenance

Clearhaus Services, Components and Regions

Recent Clearhaus events

Merchant API: Unavailability due to database maintenance

Transaction gateway: Unavailability due to database maintenance

Transaction gateway: Unavailability due to database maintenance

Settlements briefly unavailable in Merchant API

Connectivity issue towards upstream

Some subsequent recurring transactions fail upstream

Get your FREE account now,
5 monitors included!

Is Clearhaus down?

Clearhaus status is UP

Lastest published events

Merchant API: Unavailability due to database maintenance

Transaction gateway: Unavailability due to database maintenance

Transaction gateway: Unavailability due to database maintenance

Clearhaus Services, Components and Regions

Recent Clearhaus events

Merchant API: Unavailability due to database maintenance

Transaction gateway: Unavailability due to database maintenance

Transaction gateway: Unavailability due to database maintenance

Settlements briefly unavailable in Merchant API

Connectivity issue towards upstream

Some subsequent recurring transactions fail upstream

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!