Clearhaus 장애 기록

1. 2026년 10월 14일 오전 8:55 UTCinvestigating

   2026-10-14 07:15 CEST 이후, 우리는 비자 신용 및 직불 거래 (Direct OCT 및 AFT, /credits 및 /debits endpoints를 통해 전송)의 거부 비율을 보았으며, 직불의 환불을 포함하여. 이 문제는 이러한 거래 유형 만, 비자 신용 카드 또는 비자 직불 카드. 불행히도, 우리는 어제로 같은 해소 문제를보고, 우리는 완전히 문제를 해결하려고 비자와 일정한 통신에 있습니다. 일반 비자 허가, 캡처, 환불 및 voids는 모든 Mastercard 거래이기 때문에 비공식적입니다. 우리는 조사에 우리의 상류 공급자와 일하고 우리가 더 알고 있을 때 갱신을 포스트할 것입니다.

2. 2026년 10월 14일 오전 10:38 UTCmonitoring

   Hotfix는 12:03 CEST에 배포되었으며 영향을받는 서비스는 일반적으로 다시 수행됩니다. 우리는 상황을 감시하고 일단 우리가 문제점을 해결한 갱신을 한 번 포스트할 것입니다.

3. 2026년 10월 16일 오전 8:08 UTCresolved

   우리는 2026-10-14 14:09 CEST에 안정적인 수정을 배포했습니다. 우리는 모니터링하고 성공적인 것으로 확인되었습니다. 우리는 여전히 비자 측에 뿌리 원인을 이해하기 위해 비자와 통신, 그러나이 사건의 더 이상 영향이 없기 때문에, 여기에 해결 될 것입니다. 사건 기간 도중 07:15–12:03 CEST, 비자 신용의 86 % 또는 직불은 상태 코드 50000를 받았습니다. Impacted Merchants는 "status unknown"를 나타내는 상태 코드 50000 및 상태 메시지를받은 영향력있는 거래의 실제 상태를 명확하게하기 위해 우리에게 직접 통신을받습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 10월 13일 오후 7:15 UTCresolved

   18:18 및 18:53 UTC 사이, 결제 데이터는 데이터베이스 아웃리지로 인해 Merchant API에서 사용할 수 없습니다. Gateway 거래 처리는 어떤 시점에 영향을 미치지 않았습니다. 우리는 어떤 불편든지를 위해 apologise.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 10월 13일 오전 9:33 UTCinvestigating

   2026-10-13 08:16 CEST, 우리는 비자 신용 및 직불 거래 (Direct OCT 및 AFT, /credits 및 /debits endpoints를 통해 전송)에 대한 거부의 증가율을 보았으며, 직불의 환불을 포함하여. 이 문제는 이러한 거래 유형 만, 비자 신용 카드 또는 비자 직불 카드. 일반 비자 허가, 캡처, 환불 및 voids는 모든 Mastercard 거래이기 때문에 비공식적입니다. 우리는 조사에 우리의 상류 공급자와 일하고 우리가 더 알고 있을 때 갱신을 포스트할 것입니다.

2. 2026년 10월 13일 오전 11:06 UTCmonitoring

   2026-10-13 12:30 CEST, 비자 다이렉트 OCT 및 AFT, /credits 및 /debits endpoints를 통해 전송), 직불의 환불을 포함하여 정상으로 일하고있다. 우리는 케이스에서 상황을 감시하고 있습니다.

3. 2026년 10월 13일 오후 1:10 UTCresolved

   우리는 상황을 모니터링하고 오류율이 정상화되었는지 확인했습니다. 이 사건은 지금 닫힙니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 10월 9일 오전 7:20 UTCinvestigating

   시작 2026-10-09T02:00Z 우리는 권한 및 voids (및 Mastercard debits 및 debit 환불)에 대한 우리의 업스트림 공급 업체에 대한 간헐적 인 연결 문제를 경험하고있다. 자동 장애 및 복구는 크게 영향을 완화하지만, 우리는 2026-10-09T02:00Z – 2026-10-09T07:00Z 사이에 0.75 %의 오류율을 관찰했습니다. 우리는 우리의 업스트림 공급 업체에 투자하고 해결합니다. 캡처 및 캡처 환불 및 비자 직불 및 직불 환불은 영향을받지 않습니다.

2. 2026년 10월 9일 오전 8:26 UTCmonitoring

   06:36Z부터 우리는 ~0.04 %의 낮은 오류율을 본 우리의 업스트림 제공 업체의 이차 데이터 센터에 모든 트래픽을 잠겼습니다. 07:42Z에서 우리는 문제가 우리의 업스트림 공급자에 의해 해결 된 것을 알려졌다. 07:53Z 이후 우리는 트래픽을 1 차 데이터 센터로 이전하고 더 이상 오류가 없습니다.

3. 2026년 10월 9일 오전 9:37 UTCresolved

   우리는 오류가 06 : 36Z 이후 관찰되지 않았기 때문에이 사건을 닫고 문제가 해결되기 위해 확인되었습니다. 1.14 %의 평균 고장률은 2026-10-09T04:01Z와 2026-10-09T06:35Z (첫 번째 및 마지막 오류가 발생했을 때)의 피크 오류율이 31 %의 분 이내에 관찰되었습니다. 또한, 우리는 또한 오류의 작은 컬렉션을 관찰 2026-10-08T22:32Z – 2026-10-08T22:41Z의 평균 고장율에서 ~11 %. 영향 거래 유형에 대한 수정! Authorizations, voids, 캡처 환불 및 Mastercard 크레딧이 영향을 받았습니다. 거래 유형 (현금, 직불, 직불 환불 및 비자 크레딧)은 영향을받지 않았습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 9월 10일 오후 2:47 UTCresolved

   사이 2026-08-27T00:30:35Z 및 2026-08-27T00:48:01Z, 모든 비자 허가는 상태 코드 40400, "백엔드 문제". 몇 가지 비자 거래는 이미 시작 실패 2026-08-27T00:25Z. 모든 캡처, 환불, 공증 및 신용과 함께 마스터 카드 승인은 비공식적이었다. 우리는 2026-08-27T00:48:01Z 이후 더 많은 연결 오류가 없었다. 실패한 허가는 청구되지 않았고 다시 시도 할 수 있습니다. 우리는 우리의 업스트림 공급자와 협력하여 뿌리 원인을 결정하고 미래의 유사한 문제를 방지합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 11일 오후 1:24 UTCinvestigating

   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.

2. 2026년 8월 11일 오후 2:15 UTCidentified

   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.

3. 2026년 8월 12일 오전 3:32 UTCresolved

   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.

1. 2026년 8월 7일 오전 8:33 UTCresolved

   오후 2026-08-06 사이 13:00 과 16:56 UTC, 모든 Google Pay 거래는 상태 코드와 실패 40000, "Google Pay 입력 오류, 중간 키의 유효 서명". Apple Pay 및 일반 카드 거래를 포함한 다른 지불 방법이 없습니다. 우리는 미래의 회귀를 방지하기 위해이 지역에서 경고를 개선하고 있습니다.

2. 2026년 9월 1일 오전 9:42 UTCpostmortem

   ## 무슨 일이 있었습니까? 설정 변경은 Google Pay 트랜잭션이 실패했습니다. 변화는 환경간의 구성을 정리하기 위해 만들어졌습니다. Google Pay는 이러한 구성 중 하나에 의존하지 않았습니다. 새로운 배포에 트래픽을 이동하기 전에, 우리는 항상 자동화된 테스트 거래를 실행합니다. 그러나 Google Pay는 자동으로 테스트되지 않지만 필요에 따라 복잡한 지불 방법이며 자동화가 어렵습니다. 이 배포는 Google Pay의 변경 사항이 포함되지 않았기 때문에 영향을받지 못했습니다. 추가 노력은 Google Pay를 테스트하기 위해 만들어졌습니다. ## 왜 우리가 그것을 감지하는 것이 느려졌습니까? Google Pay는 다른 지불 방법보다 훨씬 적은 트래픽을 가지고 있으므로 경고 임계값 아래를 보았고,이 때문에 우리는 문제가 늦어졌습니다. ### 예방 조치 * 우리는 유사한 implicit 의존성을 위한 잔여 윤곽을 검토하고 아무도를 발견했습니다. * 우리는 우리의 alerting \ (아래 참조)를 개선했습니다. #### 향상된 경고 우리는 트래픽의 작은 공유에 영향을 미치는 실패를 잡기 위해 경고를 개량했습니다. 잘못된 긍정적 인 수를 피하기 위해, 우리는 오류가 개별 판매자 계정 또는 개별 발행인에게만 발생할 수 없다는 것을 확인하는 고급 경고를 생성하기 위해 철저한 분석 및 백업을 수행했습니다. 이것은 지불 방법 당 경고 할 수 있습니다. Google Pay와 같은 작은 것조차도 거래 유형 당 - 심지어 신용과 같은 작은 것들에 대해. 이 새로운 알림으로, 우리는 최대 15 분 동안 정전에 경고했습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 6일 오후 12:17 UTCinvestigating

   우리는 현재 문제를 조사하고 있습니다. Gateway 거래 처리는 영향을 미치지 않습니다.

2. 2026년 7월 6일 오후 12:54 UTCmonitoring

   Merchant API에서 다시 거래 가능 이 문제는 해결되었습니다. 거래는 이제 Merchant API에서 사용할 수 있으며 서비스는 일반적으로 운영됩니다. Gateway 거래 처리는 어떤 시점에 영향을 미치지 않았습니다. 우리는 어떤 불편든지를 위해 apologise.

3. 2026년 7월 6일 오후 1:02 UTCresolved

   이 사건은 해결되었습니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 2월 4일 오후 12:21 UTCresolved

   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.

1. 2025년 12월 22일 오전 8:55 UTCinvestigating

   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.

2. 2025년 12월 22일 오전 9:45 UTCmonitoring

   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.

3. 2025년 12월 22일 오전 10:57 UTCresolved

   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.

1. 2025년 4월 25일 오전 7:15 UTCresolved

   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.

1. 2025년 3월 3일 오전 9:28 UTCresolved

   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.

1. 2024년 11월 20일 오후 2:03 UTCresolved

   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.

1. 2024년 10월 31일 오전 4:09 UTCinvestigating

   Due to a service provider we are experiencing degraded performance in the Merchant API. This does not affect our ability to process transactions.

2. 2024년 11월 8일 오전 9:16 UTCresolved

   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.

1. 2024년 10월 4일 오전 11:27 UTCresolved

   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.

1. 2024년 9월 12일 오전 4:42 UTCinvestigating

   Since 2024-09-12T03.39Z we have observed connectivity issues towards an upstream provider. We have reached out and are investigating with the provider.

2. 2024년 9월 12일 오전 5:05 UTCinvestigating

   Our upstream provider has confirmed and is aware of a connectivity issue. Currently almost all authorizations, voids and Mastercard credits are impacted.

3. 2024년 9월 12일 오전 6:34 UTCidentified

   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.

4. 2024년 9월 12일 오전 8:41 UTCidentified

   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.

5. 2024년 9월 12일 오전 9:06 UTCidentified

   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 %.

6. 2024년 9월 12일 오전 10:47 UTCidentified

   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.

7. 2024년 9월 12일 오전 11:51 UTCidentified

   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.

8. 2024년 9월 12일 오후 12:04 UTCmonitoring

   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.

9. 2024년 9월 12일 오후 8:39 UTCresolved

   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!

10. 2024년 10월 2일 오후 12:35 UTCpostmortem

    ## Introduction As a follow-up on the incident on 2024-09-12, this is our findings from analyzing the sequence of events. Again, we sincerely apologize for the disruption, downtime and inconvenience. ## The issue During the timespan 2024-09-12T03:30Z - 2024-09-12T11:45Z, we experienced connection failures and timeouts to an upstream provider. This affected live transactions: authorizations and voids for both Visa and Mastercard as well as credits for Mastercard. After confirming that the issue was entirely external, and that we were thus unable to mitigate it ourselves, we reached out to our provider, opened an issue with them and escalated immediately. Our automated failover moved traffic to the provider’s secondary data center when the first transactions failed towards their primary data center. While this is normally sufficient to mitigate small hiccups, this showed that the secondary data center was also affected by the incident. No transactions towards the second data center were approved and we therefore decided to only target the primary data center as we saw upwards of 10-15 % of the transactions going through there. We periodically sent small bursts of transactions to the secondary data center to monitor availability. There was a small window of 10 minutes where transactions were processed through the secondary data center before it became dysfunctional again. We contacted our provider to inform them that the secondary data center had been in a working state. After approximately 8 hours, our provider was able to mitigate the issue in both data centers, which resolved the incident, and approval rates went back to normal. For a short period of time during the incident our services were exhausted which exacerbated the condition. This resulted in the transaction gateway responding HTTP 504 Gateway Timeout which affected all transaction types. We are sincerely sorry for the inconvenience and we are working to prevent this from happening in the future. ## Remediation While we do not have any direct involvement in the incident at our provider we have learned a thing or two to take with us: 1. We will investigate the possibility to void authorizations with status code 50000 such that clients can void these transactions to ensure the state at upstream is the same representation as at the client. At the same time we will highlight that the transaction representation in the Merchant API will help in this regard to understand the state of a transaction. For critical transactions \(e.g. credits or “large enough” authorizations\) we recommend to use the [Merchant API](https://developer.clearhaus.com) to check the state of a transaction when you did not receive a response \(no matter if the failure happened on our end, somewhere in the middle, or on your end\). 2. To avoid HTTP 504 responses, we will go over our resource allocation and adjust to have a better tolerance. In addition we will improve alerting on our application load balancer to highlight when our internal systems are responding slowly and thus indicating a resource exhaustion in our system. 3. Investigate if we can improve upon the automated failover mechanism to balance traffic so we do not need to manually send small bursts to test availability. This could potentially have made us earlier aware when the secondary came up both for midways in the incident and in the very end of the incident. Already implemented improvements: 1. Extend internal dashboards to give improved visibility in the continuous success rates on the individual upstream data centers.

1. 2024년 8월 30일 오후 1:34 UTCidentified

   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.

2. 2024년 8월 30일 오후 7:46 UTCidentified

   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.

3. 2024년 9월 2일 오전 8:18 UTCresolved

   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.

1. 2024년 8월 2일 오전 7:11 UTCidentified

   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.

2. 2024년 8월 2일 오전 7:27 UTCidentified

   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.

3. 2024년 8월 2일 오전 8:45 UTCmonitoring

   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.

4. 2024년 8월 2일 오전 9:21 UTCmonitoring

   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.

5. 2024년 8월 2일 오전 9:21 UTCresolved

   This incident has been resolved.

1. 2024년 4월 25일 오전 11:03 UTCinvestigating

   We are currently seeing an increase in declined Visa Authorizations and are currently investigating.

2. 2024년 4월 25일 오전 11:52 UTCmonitoring

   The issue started 2024-04-25T10:35:00Z and ended 2024-04-25T11:48:00Z when we applied a hotfix.

3. 2024년 4월 25일 오후 4:51 UTCmonitoring

   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.

4. 2024년 4월 25일 오후 6:23 UTCmonitoring

   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.

5. 2024년 4월 26일 오전 11:13 UTCresolved

   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.

1. 2024년 1월 12일 오전 9:57 UTCidentified

   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.

2. 2024년 1월 15일 오후 2:05 UTCresolved

   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.