Live  /  PAY.  /  Incident

PAY.: Additional Security Measures Activated Due to Critical PHP Vulnerabilities

PAY. · pay.nlResolved2026-10-21 18:25 UTC
Public — what happened

Summary

PAY said that after a security advisory about serious flaws in PHP, which it uses for some of its applications, it switched on extra protective measures on 21 October 2026 as a precaution. The company said it had no sign the flaws were exploited in its systems, but that some integrations sending unusual content, such as HTML or commands, could get a 403 Forbidden error. PAY described the impact as very limited and asked affected customers to check their payload and email its integrations team if problems continued. The company said it would turn the measures off once a patch was installed and validated, and the incident is marked resolved at 18:24 UTC the same day.

Affected

MY.pay.nl, Multicore Router: connect.pay.nl, PAY.APP, Multicore: achterelkebetaling.nl, Transaction management, Multicore: payments.nl, Single core: pay.nl (legacy), Operational management, Terminal management, Registration and configuration

As listed on PAY.’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 PAY. 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 PAY.: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the PAY. report →

More from PAY.

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

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

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