Live / Paysafe / Incident
Paysafe: Service Disruption - Paysafe Acquiring RS2
Paysafe · paysafe.comMinor incidentResolved2026-10-20 10:25 UTC
Public — what happened
Summary
Paysafe said that monthly statements (invoices) for July through September 2026 showed discrepancies for all accounts in its Paysafe Business Experience portal, affecting its Acquiring RS2 service. The company reported this on 16 October 2026 and said the problem came from a technical issue on its processing partner's side, with corrected invoices expected the following week. On 19 October Paysafe said the issue had been identified and a fix was being put in place, and it marked the incident resolved on 20 October 2026.
Affected
Paysafe Acquiring RS2 - Invoices
Timeline
- Started — 2026-10-16 07:54 UTC
- Investigating — 2026-10-16 07:54 UTC
- Identified — 2026-10-19 08:07 UTC
- Resolved — 2026-10-20 10:25 UTC · 4 days 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 43, 2026, our weekly internet health report.