Live / Paysafe / Incident
Paysafe: Service Disruption - Paysafecard Payments
Paysafe · paysafe.comMinor incidentResolved2026-10-23 16:32 UTC
Public — what happened
Summary
Paysafe reported a minor service disruption affecting its paysafecard payment API, which it began investigating on 2026-10-20 at 19:03 UTC. The company said that by 09:34 UTC on 2026-10-21 it had identified the root cause and was working on a fix, and it posted several updates over the next two days saying that work was continuing. Paysafe said a solution was put in place on 2026-10-23 at 12:44 UTC and that it was monitoring the affected services, and the incident was marked resolved at 16:32 UTC that day.
Affected
PSC Payment, Pin On Demand Distribution, PSC Payment myPaysafe, Paysafecash Distribution, PSC Payout & Refund, eCash Reconciliation Files, Paysafecash Payment, eCash PagoEfectivo, eCash SafetyPay, eCash Settlement Report, eCash Store Locator B2B
Timeline
- Started — 2026-10-20 19:03 UTC
- Investigating — 2026-10-20 19:03 UTC
- Identified — 2026-10-21 09:34 UTC (4 updates)
- Monitoring — 2026-10-23 12:44 UTC
- Resolved — 2026-10-23 16:32 UTC · 3 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 44, 2026, our weekly internet health report.