Live / Paysafe / Incident
Paysafe: Service Disruption - QR Code Partner
Paysafe · paysafe.comMinor incidentResolved2026-11-14 04:20 UTC
Public — what happened
Summary
Paysafe said that a third-party provider of its QR code service began running in a degraded state on 13 November 2026 at 22:55 UTC, and it classed the incident as minor. The company said it was redirecting traffic to a backup solution to bring service back to normal, and that its teams were watching the situation. Paysafe's status page now lists the incident as resolved, with a resolution time of 04:20 UTC on 14 November.
Affected
GMoney, QR Payments
Timeline
- Started — 2026-11-13 22:55 UTC
- Identified — 2026-11-13 22:55 UTC
- Resolved — 2026-11-14 04:20 UTC · 5h 25m after it started
With SquidGrid — where it starts on the route
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 seeCustomers 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 47, 2026, our weekly internet health report.