Live  /  Paysafe  /  Incident

Paysafe: Service Disruption - PagoEfectivo

Paysafe · paysafe.comCritical outageResolved2026-11-01 10:31 UTC
Public — what happened

Summary

Paysafe said its PagoEfectivo services were disrupted starting 29 October 2026 at 21:01 UTC, and the incident was rated critical. The company said it identified the root cause that evening, and that the services stayed temporarily suspended for about two days while it carried out recovery and safety checks. On 31 October Paysafe said the services were being brought back online after a review with outside cybersecurity experts, and that some existing API credentials had been permanently deactivated, with affected customers to be contacted and issued new ones. Later that day it reported a separate slowdown at a QR code partner, said it rerouted traffic, and the incident was marked resolved on 1 November at 10:31.

Affected

CCE - Cámara de Compensación Electrónica, CIP Generation, Merchant Portal (PagoEfectivo), Merchant Notification (PagoEfectivo), PagoEfectivo Wallet, Niubiz, GMoney, Banco de Crédito del Perú (BCP), QR Payments, BBVA

As listed on Paysafe’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Paysafe against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Paysafe: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Paysafe report →

More from Paysafe

Covered in The Squid’s Ink, Week 45, 2026, our weekly internet health report.

The full archive is on the Paysafe status & history page.

Related: Paysafe status & history. SquidGrid is not affiliated with Paysafe.