Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Cronologia delle interruzioni di Clearhaus

    58 Clearhaus incidents · febbraio 2020 — official updates, affected components, duration and resolution details.

    Torna allo stato attuale

    Le transazioni Visa Credit e Debit in mancanza

    Inizio 14 ottobre 2026 alle ore 08:55 UTC · 1d 23h

    OutageIncidente maggiore
    Componenti interessati
    Gateway API (gateway.clearhaus.com)
    1. 14 ottobre 2026 alle ore 08:55 UTCinvestigating

      Dal 2026-10-14 07:15 CEST, abbiamo visto un aumento della velocità dei rifiuti sulle transazioni di credito e debito Visa (Visa Direct OCT e AFT, inviati tramite i endpoint /credits e /debits), inclusi i rimborsi dei debiti. Ciò riguarda solo questi tipi di transazioni, non carte di credito Visa o carte di debito Visa. Purtroppo, vediamo lo stesso problema sottostante come abbiamo fatto ieri, e siamo in costante comunicazione con Visa cercando di risolvere completamente il problema. Le autorizzazioni regolari del visto, le catture, i rimborsi e i vuoti non sono influenzati, come tutte le transazioni di Mastercard. Stiamo lavorando con il nostro provider a monte per indagare e pubblicheremo un aggiornamento quando ne sappiamo di più.

    2. 14 ottobre 2026 alle ore 10:38 UTCmonitoring

      Un hotfix è stato distribuito alle 12:03 CEST, e il servizio interessato si sta eseguendo di nuovo normalmente. Stiamo monitorando la situazione e pubblicheremo un aggiornamento una volta confermato che il problema è risolto.

    3. 16 ottobre 2026 alle ore 08:08 UTCresolved

      Abbiamo implementato una fissa stabile a 2026-10-14 14:09 CEST che abbiamo monitorato e confermato di avere successo. Siamo ancora in comunicazione con Visa per capire la causa principale sul lato Visa, ma siccome non c'è più impatto di questo incidente, sarà considerato risolto. Durante il periodo di incidente 07:15–12:03 CEST, l'86 % dei crediti o dei debiti ricevuti codice di stato 50000. I commercianti colpiti riceveranno comunicazione diretta da noi per chiarire lo stato effettivo delle transazioni incise che hanno ricevuto il codice di stato 50000 e un messaggio di stato che indica "status sconosciuto".

    Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

    Settlements non disponibili in Merchant API

    Inizio 13 ottobre 2026 alle ore 18:00 UTC · 0m

    Pending
    1. 13 ottobre 2026 alle ore 19:15 UTCresolved

      Tra le 18:18 e le 18:53 UTC, i dati di insediamento non erano disponibili nell'API Merchant a causa di un outage del database. L'elaborazione delle transazioni del gateway non è stata influenzata in alcun punto. Ci scusiamo per qualsiasi inconveniente.

    Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

    Le transazioni Visa Credit e Debit in mancanza

    Inizio 13 ottobre 2026 alle ore 09:33 UTC · 3h 37m

    OutageIncidente maggiore
    Componenti interessati
    Gateway API (gateway.clearhaus.com)
    1. 13 ottobre 2026 alle ore 09:33 UTCinvestigating

      Dal 2026-10-13 08:16 CEST, abbiamo visto un aumento della velocità dei rifiuti sulle transazioni di credito e debito Visa (Visa Direct OCT e AFT, inviati tramite i endpoint /credits e /debits), inclusi i rimborsi dei debiti. Ciò riguarda solo questi tipi di transazioni, non carte di credito Visa o carte di debito Visa. Le autorizzazioni regolari del visto, le catture, i rimborsi e i vuoti non sono influenzati, come tutte le transazioni di Mastercard. Stiamo lavorando con il nostro provider a monte per indagare e pubblicheremo un aggiornamento quando ne sappiamo di più.

    2. 13 ottobre 2026 alle ore 11:06 UTCmonitoring

      Dal 2026-10-13 12:30 CEST, Visa Direct OCT e AFT, inviati tramite i endpoint /credits e /debits), compresi i rimborsi dei debiti, ha funzionato come normale. Stiamo monitorando la situazione in caso di ritorno.

    3. 13 ottobre 2026 alle ore 13:10 UTCresolved

      Abbiamo monitorato la situazione e confermato che i tassi di errore sono normalizzati. Questo incidente è ora chiuso.

    Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

    Emissione di connettività verso l'alto

    Inizio 9 ottobre 2026 alle ore 07:20 UTC · 2h 17m

    IssuesIncidente minore
    Componenti interessati
    Gateway API (gateway.clearhaus.com)
    1. 9 ottobre 2026 alle ore 07:20 UTCinvestigating

      A partire da 2026-10-09T02:00Z stiamo vivendo problemi di connettività intermittente verso il nostro fornitore a monte per autorizzazioni e vuoti (e addebiti Mastercard e rimborsi di debito). Il failover automatico e il recupero stanno notevolmente alleviando l'impatto, ma abbiamo osservato i tassi di errore dello 0,75% tra 2026-10-09T02:00Z – 2026-10-09T07:00Z. Stiamo indagando e raggiungendo il nostro fornitore a monte per risolvere. Acquisire e catturare rimborsi e debiti Visa e rimborsi di debito non sono influenzati.

    2. 9 ottobre 2026 alle ore 08:26 UTCmonitoring

      Dal 06:36Z abbiamo bloccato tutto il traffico al centro dati secondario del nostro provider a monte dove abbiamo visto un tasso di errore inferiore di ~0.04 %. Alle 07:42Z siamo stati informati che il problema è stato risolto dal nostro fornitore a monte. Dal 07:53Z abbiamo spostato il traffico indietro al data center primario e non abbiamo visto ulteriori errori.

    3. 9 ottobre 2026 alle ore 09:37 UTCresolved

      Stiamo chiudendo questo incidente in quanto non sono stati osservati errori dal 06:36Z e dal momento che il problema è confermato essere risolto. Un tasso medio di guasto dell'1,4 % è stato osservato tra il 2026-10-09T04:01Z e il 2026-10-09T06:35Z (di quando si è verificato il primo e l'ultimo errore) con un tasso di errore di picco entro un minuto del 31 %. Inoltre, abbiamo anche osservato una piccola raccolta di errori 2026-10-08T22:32Z – 2026-10-08T22:41Z ad un tasso medio di guasto del ~11 %. Correzione sui tipi di transazione interessati! Le autorizzazioni, i vuoti, i rimborsi di cattura e i crediti di Mastercard sono stati colpiti. I tipi di transazione rimanenti (capture, addebiti, rimborsi di debito e crediti Visa) non sono stati colpiti.

    Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

    Autorizzazione del visto per breve tempo in mancanza

    Inizio 27 agosto 2026 alle ore 00:30 UTC · 0m

    Pending
    1. 10 settembre 2026 alle ore 14:47 UTCresolved

      Tra 2026-08-27T00:30:35Z e 2026-08-27T00:48:01Z, tutte le autorizzazioni Visa fallite con codice di stato 40400, "problema backend". Alcune transazioni Visa erano già in fallimento a partire 2026-08-27T00:25:25Z. Le autorizzazioni Mastercard insieme a tutte le catture, i rimborsi, i vuoti e i crediti non sono stati colpiti. Non abbiamo visto altri errori di connettività dal 2026-08-27T00:48:01Z. Le autorizzazioni fallite non sono state addebitate e possono essere ripristinate. Stiamo lavorando con il nostro provider a monte per determinare la causa principale e per prevenire problemi simili in futuro.

    Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

    Mastercard credits failing

    Inizio 11 agosto 2026 alle ore 13:24 UTC · 14h 8m

    OutageIncidente maggiore
    Componenti interessati
    Gateway API (gateway.clearhaus.com)
    1. 11 agosto 2026 alle ore 13: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. 11 agosto 2026 alle ore 14: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. 12 agosto 2026 alle ore 03: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.

    Fallimento delle transazioni di Google Pay

    Inizio 6 agosto 2026 alle ore 01:00 UTC · 0m

    Pending
    1. 7 agosto 2026 alle ore 08:33 UTCresolved

      Il 2026-08-06 tra le 13:00 e le 16:56 UTC, tutte le transazioni di Google Pay sono fallite con il codice di stato 40000, "errore di ingresso Google Pay, nessuna firma valida di chiave intermedia". Nessun altro metodo di pagamento, tra cui Apple Pay e le transazioni regolari della carta, sono stati colpiti. Stiamo migliorando il nostro avviso in questo settore per prevenire future regressioni.

    2. 1 settembre 2026 alle ore 09:42 UTCpostmortem

      ### Che è successo? Una modifica di configurazione ha fatto fallire le transazioni di Google Pay. Il cambiamento è stato fatto per pulire le incongruenze di configurazione tra gli ambienti. Google Pay aveva una dipendenza implicita da una di queste configurazioni. Prima di spostare il traffico in una nuova distribuzione, facciamo sempre operazioni di test automatizzate. Tuttavia, Google Pay non è testato automaticamente ma solo per necessità, in quanto è un metodo di pagamento convoluto e difficile da automatizzare. Dal momento che questa distribuzione non includeva modifiche a Google Pay e non si aspettava di influenzarlo, non è stato fatto alcun ulteriore sforzo per testare Google Pay. ### Perché eravamo lenti a rilevarla? Google Pay ha significativamente meno traffico rispetto ad altri metodi di pagamento quindi colpisce sotto la nostra soglia di avviso, e a causa di questo siamo stati lenti a notare il problema. ## Azioni preventive * Abbiamo esaminato la configurazione rimanente per simili dipendenze implicite e non abbiamo trovato nessuno. * Abbiamo migliorato il nostro avviso \(vedere sotto\). #### Miglioramento dell'avviso Abbiamo migliorato il nostro avviso per catturare i guasti che interessano una piccola parte del traffico. Per evitare un numero significativo di falsi positivi, abbiamo fatto analisi e test approfonditi per creare avvisi avanzati che controllano per confermare che gli errori non avvengono solo su singoli conti mercantili o per singoli emittenti. Questo ci permette di essere avvisati per metodo di pagamento — anche per quelli più piccoli come Google Pay — ma anche per tipo di transazione — anche per quelli più piccoli come crediti. Con questi nuovi avvisi in atto saremmo stati allertati al outage entro, al massimo, 15 minuti.

    Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

    Transazioni non disponibili in Merchant API

    Inizio 6 luglio 2026 alle ore 12:17 UTC · 44m

    OutageIncidente maggiore
    Componenti interessati
    Production (merchant.clearhaus.com)
    1. 6 luglio 2026 alle ore 12:17 UTCinvestigating

      Stiamo indagando sul problema. L'elaborazione delle transazioni Gateway non è interessata.

    2. 6 luglio 2026 alle ore 12:54 UTCmonitoring

      Transazioni disponibili di nuovo in Merchant API Questo problema è stato risolto. Le transazioni sono ora disponibili nell'API Merchant e il servizio funziona normalmente. L'elaborazione delle transazioni del gateway non è stata influenzata in alcun punto. Ci scusiamo per qualsiasi inconveniente.

    3. 6 luglio 2026 alle ore 13:02 UTCresolved

      Questo incidente è stato risolto.

    Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

    Settlements briefly unavailable in Merchant API

    Inizio 4 febbraio 2026 alle ore 12:21 UTC · 0m

    IssuesIncidente minore
    Componenti interessati
    Production (merchant.clearhaus.com)
    1. 4 febbraio 2026 alle ore 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.

    Connectivity issue towards upstream

    Inizio 22 dicembre 2025 alle ore 08:55 UTC · 2h 3m

    OutageIncidente maggiore
    Componenti interessati
    Gateway API (gateway.clearhaus.com)
    1. 22 dicembre 2025 alle ore 08: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. 22 dicembre 2025 alle ore 09: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. 22 dicembre 2025 alle ore 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.

    Some subsequent recurring transactions fail upstream

    Inizio 11 aprile 2025 alle ore 09:00 UTC · 0m

    Pending
    1. 25 aprile 2025 alle ore 07: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.

    Connectivity issue towards upstream

    Inizio 2 marzo 2025 alle ore 04:30 UTC · 0m

    Pending
    1. 3 marzo 2025 alle ore 09: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.

    Connectivity issue towards upstream

    Inizio 20 novembre 2024 alle ore 01:00 UTC · 0m

    Pending
    1. 20 novembre 2024 alle ore 14: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.

    Merchant API: Degraded performance

    Inizio 31 ottobre 2024 alle ore 04:09 UTC · 8d 5h

    IssuesIncidente minore
    Componenti interessati
    My Clearhaus (my.clearhaus.com)Production (merchant.clearhaus.com)
    1. 31 ottobre 2024 alle ore 04: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. 8 novembre 2024 alle ore 09: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.

    Marginally increased error rate for Mastercard authorizations

    Inizio 2 ottobre 2024 alle ore 05:30 UTC · 1d 16h

    IssuesIncidente minore
    1. 4 ottobre 2024 alle ore 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.

    Connectivity issue towards upstream

    Inizio 12 settembre 2024 alle ore 04:42 UTC · 15h 57m

    OutageIncidente critico
    Componenti interessati
    Gateway API (gateway.clearhaus.com)
    1. 12 settembre 2024 alle ore 04: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. 12 settembre 2024 alle ore 05: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. 12 settembre 2024 alle ore 06: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. 12 settembre 2024 alle ore 08: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. 12 settembre 2024 alle ore 09: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. 12 settembre 2024 alle ore 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. 12 settembre 2024 alle ore 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. 12 settembre 2024 alle ore 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. 12 settembre 2024 alle ore 20: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. 2 ottobre 2024 alle ore 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.

    Visa DK issuing BIN6 457153 partly dysfunctional

    Inizio 30 agosto 2024 alle ore 13:34 UTC · 2d 18h

    IssuesIncidente minore
    Componenti interessati
    Gateway API (gateway.clearhaus.com)
    1. 30 agosto 2024 alle ore 13: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. 30 agosto 2024 alle ore 19: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. 2 settembre 2024 alle ore 08: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.

    Transaction gateway: Visa credit and debit transaction outage

    Inizio 2 agosto 2024 alle ore 07:11 UTC · 2h 10m

    OutageIncidente maggiore
    Componenti interessati
    Gateway API (gateway.clearhaus.com)
    1. 2 agosto 2024 alle ore 07: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. 2 agosto 2024 alle ore 07: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. 2 agosto 2024 alle ore 08: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. 2 agosto 2024 alle ore 09: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. 2 agosto 2024 alle ore 09:21 UTCresolved

      This incident has been resolved.

    Transaction gateway: Declined Visa authorizations

    Inizio 25 aprile 2024 alle ore 11:03 UTC · 1d 0h

    OutageIncidente maggiore
    Componenti interessati
    Gateway API (gateway.clearhaus.com)
    1. 25 aprile 2024 alle ore 11:03 UTCinvestigating

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

    2. 25 aprile 2024 alle ore 11:52 UTCmonitoring

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

    3. 25 aprile 2024 alle ore 16: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. 25 aprile 2024 alle ore 18: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. 26 aprile 2024 alle ore 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.

    Merchant API and my.clearhaus.com: Missing references

    Inizio 12 gennaio 2024 alle ore 09:57 UTC · 3d 4h

    Pending
    Componenti interessati
    My Clearhaus (my.clearhaus.com)Production (merchant.clearhaus.com)
    1. 12 gennaio 2024 alle ore 09: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. 15 gennaio 2024 alle ore 14: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.