- Detected by Pingoru
- Jun 17, 2026, 06:41 PM UTC
- Resolved
- Jun 17, 2026, 07:39 PM UTC
- Duration
- 58m
Affected: QR Payments
Timeline · 2 updates
-
monitoring Jun 17, 2026, 06:41 PM UTC
Please be advised that we have successfully rerouted the traffic to our alternate solution. Affected services are now fully operational. More updates to follow. MIM Paysafe Versión en Español Les informamos que hemos redirigido exitosamente el tráfico a nuestra solución alternativa. Los servicios afectados ya están totalmente operativos. Seguimos informando. MIM Paysafe
-
resolved Jun 17, 2026, 07:39 PM UTC
Please be advised that our partner has successfully restored their services. We have successfully switched traffic back to the primary provider. All services have been confirmed to be fully operational. We value your partnership and appreciate your understanding while our partner was remediating the situation. MIM Paysafe Versión en Español Les informamos que nuestro proveedor de códigos QR ha implementado la solución correspondiente y los servicios se encuentran completamente restablecidos. El tráfico ha sido redirigido exitosamente al proveedor principal y todos los servicios han sido verificados y confirmados como plenamente operativos. Valoramos su confianza y agradecemos su comprensión durante la resolución de esta incidencia. MIM Paysafe Reference ID: INC0310745
Read the full incident report →
- Detected by Pingoru
- Jun 16, 2026, 07:28 PM UTC
- Resolved
- Jun 17, 2026, 12:44 AM UTC
- Duration
- 5h 16m
Affected: Fiserv First Data
Timeline · 3 updates
-
investigating Jun 16, 2026, 07:28 PM UTC
We are investigating potential issues with the service mentioned below and apologize for the impact this might have on your business. Further updates will follow. MIM Paysafe Reference ID: INC0310581
-
identified Jun 16, 2026, 09:08 PM UTC
Our provider Fiserv First Data has identified the root cause and is working on implementing a solution. MIM Paysafe Reference ID: INC0310581
-
resolved Jun 17, 2026, 12:44 AM UTC
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 our partner Fiserv was remediating the situation. MIM Paysafe Reference ID: INC0310581
Read the full incident report →
- Detected by Pingoru
- Jun 16, 2026, 09:34 AM UTC
- Resolved
- Jun 16, 2026, 10:35 AM UTC
- Duration
- 1h 1m
Affected: eps-Payment (PSA)
Timeline · 3 updates
-
investigating Jun 16, 2026, 09:34 AM UTC
We are investigating а potential issue with our eps-Payment (PSAustria) provider and apologize for the impact this might have on your business. Further updates will follow. MIM Paysafe Reference ID: INC0310475
-
monitoring Jun 16, 2026, 09:52 AM UTC
A solution has been implemented and activity on the impacted services is being monitored. We will keep you informed on progress. MIM Paysafe Reference ID:INC0310475
-
resolved Jun 16, 2026, 10:35 AM UTC
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 our partner PSAustria was remediating the situation. MIM Paysafe Reference ID:INC0310475
Read the full incident report →
- Detected by Pingoru
- Jun 16, 2026, 08:20 AM UTC
- Resolved
- Jun 16, 2026, 09:13 AM UTC
- Duration
- 53m
Affected: eps-Payment (PSA)
Timeline · 3 updates
-
investigating Jun 16, 2026, 08:20 AM UTC
We are investigating а potential issue with our eps-Payment (PSAustria) provider and apologize for the impact this might have on your business. Further updates will follow. MIM Paysafe Reference ID: INC0310455
-
monitoring Jun 16, 2026, 08:48 AM UTC
A solution has been implemented and activity on the impacted services is being monitored. We will keep you informed on progress. MIM Paysafe Reference ID: INC0310455
-
resolved Jun 16, 2026, 09:13 AM UTC
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: INC0310455
Read the full incident report →
- Detected by Pingoru
- Jun 15, 2026, 08:31 PM UTC
- Resolved
- Jun 16, 2026, 07:42 PM UTC
- Duration
- 23h 11m
Affected: Merchant Portal (PagoEfectivo)
Timeline · 2 updates
-
identified Jun 15, 2026, 08:31 PM UTC
Please be advised that we are currently experiencing an issue where merchant funds are not displaying correctly on the merchant portal. Please note that funding operations continue to process successfully, and merchants are receiving their funds without interruption. We are actively working on a fix and will provide updates as progress is made. MIM Paysafe Reference ID: INC0310395
-
resolved Jun 16, 2026, 07:42 PM UTC
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: INC0310395
Read the full incident report →
- Detected by Pingoru
- Jun 14, 2026, 09:22 PM UTC
- Resolved
- Jun 14, 2026, 09:43 PM UTC
- Duration
- 20m
Affected: PIXBradesco
Timeline · 3 updates
-
investigating Jun 14, 2026, 09:22 PM UTC
We are investigating (a) potential issue(s) with the service(s) mentioned below and apologize for the impact this might have on your business. Further updates will follow. MIM Paysafe Reference ID: INC0310266
-
monitoring Jun 14, 2026, 09:32 PM UTC
A solution has been implemented and activity on the impacted services is being monitored. We will keep you informed on progress. MIM Paysafe Reference ID: INC0310266
-
resolved Jun 14, 2026, 09:43 PM UTC
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: INC0310266
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 08:08 AM UTC
- Resolved
- Jun 12, 2026, 02:06 PM UTC
- Duration
- 2d 5h
Affected: Paysafe Acquiring RS2 - Financial Reporting
Timeline · 5 updates
-
identified Jun 10, 2026, 08:08 AM UTC
Please be advised that due to a technical issue, merchants and partners may experience a delay in the delivery of Standardized Payment Details and Account Statement Reports. Our teams are working to generate the reports with the highest priority. Thank you for your understanding and apologize for the impact this might have on your business! Further updates will follow. MIM Paysafe Reference ID:INC0309829
-
identified Jun 11, 2026, 07:49 AM UTC
We are continuing to work on a fix for this issue.
-
identified Jun 12, 2026, 07:41 AM UTC
Dear All, Our technical teams have narrowed down the root cause of the issue and the fix is prepared. Once the validation and the testing is done the fix will be released. Our teams are working with the highest priority. Kind Regards,
-
identified Jun 12, 2026, 02:05 PM UTC
We are continuing to work on a fix for this issue.
-
resolved Jun 12, 2026, 02:06 PM UTC
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: INC0309829
Read the full incident report →
- Detected by Pingoru
- Jun 08, 2026, 08:15 AM UTC
- Resolved
- Jun 08, 2026, 10:08 AM UTC
- Duration
- 1h 53m
Affected: OPTIC Portal
Timeline · 3 updates
-
investigating Jun 08, 2026, 08:15 AM UTC
We are investigating an issue with the Skrill Business Portal (OPTIC) and apologize for the impact this might have on your business. Further updates will follow. MIM Paysafe Reference ID: INC0309418
-
monitoring Jun 08, 2026, 09:35 AM UTC
A solution has been implemented and activity on the impacted services is being monitored. We will keep you informed on progress. MIM Paysafe Reference ID:INC0309418
-
resolved Jun 08, 2026, 10:08 AM UTC
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:INC0309418
Read the full incident report →
- Detected by Pingoru
- Jun 04, 2026, 07:49 PM UTC
- Resolved
- Jun 04, 2026, 08:01 PM UTC
- Duration
- 12m
Affected: Express Application
Timeline · 3 updates
-
identified Jun 04, 2026, 07:49 PM UTC
We are investigating an issue with the SafetyPay Express Application mentioned below and apologize for the impact this might have on your business. Further updates will follow. MIM Paysafe Reference ID: INC0309185
-
monitoring Jun 04, 2026, 07:58 PM UTC
A solution has been implemented and activity on the impacted services is being monitored. We will keep you informed on progress. MIM Paysafe Reference ID:INC0309185
-
resolved Jun 04, 2026, 08:01 PM UTC
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: INC0309185
Read the full incident report →
- Detected by Pingoru
- Jun 03, 2026, 06:31 PM UTC
- Resolved
- Jun 03, 2026, 08:09 PM UTC
- Duration
- 1h 37m
Affected: Banco de Crédito del Perú (BCP)QR Payments
Timeline · 2 updates
-
investigating Jun 03, 2026, 06:31 PM UTC
Our partner BCP is investigating a potential issue with their services. We apologize for the impact this might have on your business. Further updates will follow. MIM Paysafe
-
resolved Jun 03, 2026, 08:09 PM UTC
This incident has been resolved. MIM Paysafe
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2026, 07:47 AM UTC
- Resolved
- Jun 01, 2026, 08:03 AM UTC
- Duration
- 15m
Affected: Klarna bank-transfers
Timeline · 2 updates
-
investigating Jun 01, 2026, 07:47 AM UTC
We are investigating (a) potential issue(s) with the service(s) mentioned below and apologize for the impact this might have on your business. Further updates will follow. MIM Paysafe Reference ID:INC0308629
-
resolved Jun 01, 2026, 08:03 AM UTC
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:INC0308629
Read the full incident report →
- Detected by Pingoru
- May 29, 2026, 04:45 AM UTC
- Resolved
- May 29, 2026, 04:45 AM UTC
- Duration
- —
Affected: Worldpay Vantiv
Timeline · 1 update
-
resolved May 29, 2026, 04:45 AM UTC
Please be advised we experienced a degradation with Worldpay Vantiv services between 04:09 UTC and 04:10 UTC. 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: INC0308467
Read the full incident report →
- Detected by Pingoru
- May 28, 2026, 07:33 PM UTC
- Resolved
- May 28, 2026, 07:59 PM UTC
- Duration
- 25m
Affected: BBVA
Timeline · 3 updates
-
investigating May 28, 2026, 07:33 PM UTC
Our partner BBVA is investigating a potential issue with their services. We apologize for the impact this might have on your business. Further updates will follow. MIM Paysafe Reference ID: INC0308440
-
monitoring May 28, 2026, 07:42 PM UTC
Our provider BBVA implemented a solution and we are monitoring the impacted services. MIM Paysafe Reference ID: INC0308440
-
resolved May 28, 2026, 07:59 PM UTC
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 our partner BBVA was remediating the situation. MIM Paysafe Reference ID: INC0308440
Read the full incident report →
- Detected by Pingoru
- May 27, 2026, 04:09 PM UTC
- Resolved
- May 27, 2026, 04:47 PM UTC
- Duration
- 38m
Affected: BBVA
Timeline · 2 updates
-
identified May 27, 2026, 04:09 PM UTC
Our provider BBVA has identified the root cause and is working on implementing a solution. MIM Paysafe Reference ID: INC0308288
-
resolved May 27, 2026, 04:47 PM UTC
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 our partner BBVA was remediating the situation. MIM Paysafe Reference ID: INC0308288
Read the full incident report →
- Detected by Pingoru
- May 21, 2026, 08:23 AM UTC
- Resolved
- May 21, 2026, 01:27 PM UTC
- Duration
- 5h 4m
Affected: Banco del Pichincha
Timeline · 3 updates
-
investigating May 21, 2026, 08:23 AM UTC
Our partner Banco del Pichincha is investigating a potential issue with their services. We apologize for the impact this might have on your business. SafetyPay services remain fully operational. Further updates will follow. MIM Paysafe Reference ID: INC0307751
-
monitoring May 21, 2026, 01:05 PM UTC
Banco del Pichincha implemented a solution and we are monitoring the impacted services. MIM Paysafe Reference ID: INC0307751
-
resolved May 21, 2026, 01:27 PM UTC
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 our partner Banco del Pichincha was remediating the situation. MIM Paysafe Reference ID: INC0307751
Read the full incident report →
- Detected by Pingoru
- May 20, 2026, 04:37 PM UTC
- Resolved
- May 20, 2026, 04:37 PM UTC
- Duration
- —
Affected: Interac e-Transfer
Timeline · 1 update
-
resolved May 20, 2026, 04:37 PM UTC
Please be advised we experienced a degradation with Interac e-Transfer services between 12:15 UTC and 13:25 UTC. 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: INC0307677
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 02:59 PM UTC
- Resolved
- May 19, 2026, 03:59 PM UTC
- Duration
- 59m
Affected: PIXBradesco
Timeline · 3 updates
-
investigating May 19, 2026, 02:59 PM UTC
We are investigating (a) potential issue(s) with the service(s) mentioned below and apologize for the impact this might have on your business. Further updates will follow. MIM Paysafe Reference ID: INC0307463
-
monitoring May 19, 2026, 03:35 PM UTC
A solution has been implemented and activity on the impacted services is being monitored. We will keep you informed on progress. MIM Paysafe Reference ID: INC0307463
-
resolved May 19, 2026, 03:59 PM UTC
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 our partner {PARTNER NAME} was remediating the situation. MIM Paysafe Reference ID: INC0307463
Read the full incident report →
- Detected by Pingoru
- May 18, 2026, 07:16 AM UTC
- Resolved
- May 18, 2026, 05:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved May 18, 2026, 07:16 AM UTC
Please be advised we experienced a degradation with Moneris services between 5:13 UTC and 5:15 UTC. 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: INC0307259
Read the full incident report →
- Detected by Pingoru
- May 16, 2026, 11:35 AM UTC
- Resolved
- May 16, 2026, 04:35 PM UTC
- Duration
- 5h
Affected: Skrill Consumer Wallet
Timeline · 2 updates
-
investigating May 16, 2026, 11:35 AM UTC
We are investigating an issue with user withdrawals from Skrill Consumer Wallets to JP Morgan bank accounts. We are investigating alongside the bank with the highest priority. Further updates will follow. MIM Paysafe Reference ID: INC0307233
-
resolved May 16, 2026, 04:35 PM UTC
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: INC0307233
Read the full incident report →
- Detected by Pingoru
- May 15, 2026, 08:51 PM UTC
- Resolved
- May 15, 2026, 10:34 PM UTC
- Duration
- 1h 42m
Affected: Merchant & Partner Support phone lines
Timeline · 2 updates
-
investigating May 15, 2026, 08:51 PM UTC
Please note that Payment processing email support queues for merchant and technical support are temporarily inaccessible to our support teams. As a result, there might be a delay in our support team's ability to respond to your support tickets. Until further notice for system and processing critical matters, please contact your account manager or dedicated support phone line to have your problem investigated. We apologize for the impact this might have on your business. Further updates will follow. MIM Paysafe Reference ID:
-
resolved May 15, 2026, 10:34 PM UTC
Please note that the Payment processing email support queues for merchant and technical support have been restored and are now fully operational. Our support teams can now respond to tickets through the usual channels. Normal service has been resumed. We apologize for any inconvenience this may have caused to your business. Thank you for your patience. Reference ID: INC0307190
Read the full incident report →
- Detected by Pingoru
- May 12, 2026, 01:59 AM UTC
- Resolved
- May 12, 2026, 02:13 AM UTC
- Duration
- 14m
Affected: PSC PaymentPSC Payment myPaysafe
Timeline · 2 updates
-
investigating May 12, 2026, 01:59 AM UTC
We are investigating issues with our paysafecard payment via myPaysafe account API and apologize for the impact this might have on your business. Our technical teams are working on a solution and will keep you informed on progress. If you have any questions, please don't hesitate to contact us at [email protected] MIM Paysafe
-
resolved May 12, 2026, 02:13 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 11, 2026, 04:30 PM UTC
- Resolved
- May 14, 2026, 03:56 PM UTC
- Duration
- 2d 23h
Affected: Merchant Payments
Timeline · 4 updates
-
investigating May 11, 2026, 04:30 PM UTC
Please be advised that due to a technical issue, some merchants processing with Worldpay Bank via Paysafe (USA) may face a one business day delay on funding of some transactions processed on May 7th, 8th, 9th and 10th. The issue is being investigated with the highest priority. We apologize for the impact this has on your business. Thank you for your understanding. MIM Paysafe Reference ID: INC0306303
-
identified May 11, 2026, 06:43 PM UTC
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: INC0306303
-
monitoring May 12, 2026, 08:53 AM UTC
A solution has been implemented and activity on the impacted services is being monitored. We will keep you informed on progress. MIM Paysafe Reference ID: INC0306303
-
resolved May 14, 2026, 03:56 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 12:24 PM UTC
- Resolved
- May 08, 2026, 12:57 PM UTC
- Duration
- 32m
Affected: Card payments APIUnity Payments API
Timeline · 3 updates
-
investigating May 08, 2026, 12:24 PM UTC
We are investigating a potential issue with our Card & Unity Payments APIs processing services and apologize for the impact this might have on your business. Further updates will follow. MIM Paysafe Reference ID: INC0306292
-
monitoring May 08, 2026, 12:31 PM UTC
A solution has been implemented and activity on the impacted services is being monitored. We will keep you informed on progress. MIM Paysafe Reference ID:INC0306292
-
resolved May 08, 2026, 12:57 PM UTC
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:INC0306292
Read the full incident report →
- Detected by Pingoru
- May 06, 2026, 04:05 PM UTC
- Resolved
- May 06, 2026, 03:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved May 06, 2026, 04:05 PM UTC
Please be advised we experienced a partial outage with RS2 services between 15:03 UTC and 15:14 UTC. 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:INC0306044
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 12:27 AM UTC
- Resolved
- Apr 22, 2026, 03:15 AM UTC
- Duration
- 2h 48m
Affected: Multibanco
Timeline · 4 updates
-
investigating Apr 22, 2026, 12:27 AM UTC
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. MIM Paysafe Reference ID: INC0304519
-
identified Apr 22, 2026, 01:39 AM UTC
Our provider Multibanco has identified the root cause and is working on implementing a solution. MIM Paysafe Reference ID: INC0304519
-
monitoring Apr 22, 2026, 03:06 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 22, 2026, 03:15 AM UTC
This incident has been resolved.
Read the full incident report →
