The incident has been resolved successfully and the impacted services are fully restored. We apologize for the impact this issue had on your business. We value your partnership and appreciate your understanding while the situation was being remediated.
MIM Paysafe
Reference ID: INC0299932
Posted Mar 10, 2026 - 22:34 UTC
Identified
The root cause of this incident has been identified and our technical teams are working on implementing a solution. We will keep you informed on the progress.
MIM Paysafe
Reference ID: INC0299932
Posted Mar 10, 2026 - 22:17 UTC
Investigating
We are investigating a potential issue with the service mentioned below and apologize for the impact this might have on your business. Further updates will follow.
Reference ID: INC0299932
Posted Mar 10, 2026 - 21:01 UTC
Monitoring
We are investigating a potential issue with the service mentioned below and apologize for the impact this might have on your business. Further updates will follow.
Reference ID: INC0299932
Posted Mar 10, 2026 - 20:57 UTC
Identified
New incident: Investigating
Please be advised that our QR code partner is currently experiencing service degradation. We are initiating mitigation measures to reroute the traffic to our alternate solution in order to restore normal service operation. Our teams remain actively engaged and are closely monitoring the situation. We apologize for the impact this might have on your business. Further updates will follow.
MIM Paysafe
Versión en Español
Les informamos que nuestro proveedor de códigos QR presenta actualmente una degradación en el servicio. Estamos implementando medidas de mitigación para redirigir el tráfico hacia nuestra solución alternativa y así restablecer el funcionamiento normal lo antes posible. Nuestros equipos continúan trabajando activamente y monitoreando la situación de cerca. Lamentamos profundamente las molestias e impacto que esto pueda estar causando en su negocio. Publicaremos nuevas actualizaciones a medida que tengamos más información.
MIM Paysafe
Posted Mar 10, 2026 - 20:41 UTC
This incident affected: PagoEfectivo (CIP Generation, Merchant Notification (PagoEfectivo)).