PAY. logo

Is PAY. Down?

SaaSLive status, outages, and incident history

Degraded. PAY. is up but having problems.

PAY. is reporting degraded performance as of November 10, 2026. Expect slower responses or more errors. The affected components are listed below.

DegradedChecked just nowLive · every 60s1 active incident

Don't find out like this next time

You searched to find out PAY. was down. Next time we tell you, usually before your customers do, and always before you think to check.

Free, no password, no card. Unsubscribe in one click.

Official PAY. status page
How we know: the official PAY. status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

PAY. Status Summary

As of 03:51 UTC on 10 November 2026, PAY. is reporting degraded performance. PulsAPI checked PAY.'s official status page and found 64 of 65 components operational, with 1 active incident. Over the last 30 days PulsAPI measured 100.00% uptime for PAY., counting degraded performance as up. The latest incident, "Incident: Transaction processing", was on Nov 5, 2026 and lasted 7 min.

Cite as: PulsAPI, “PAY. status”, checked 10 November 2026, 03:51 UTC. https://www.pulsapi.com/services/pay

PAY. Component Status

1 of 65 PAY. components are impaired. Worst problems listed first.

1degraded64operational
Payment methods » Click 2 Pay
Degraded
Clearing and settlement
Operational
Configuration and operations (Global Management System) » MY.pay.nl
Operational

62 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Configuration and operations (Global Management System) » Operational management, Configuration and operations (Global Management System) » PAY.APP, Configuration and operations (Global Management System) » Registration and configuration, Configuration and operations (Global Management System) » Terminal management, Configuration and operations (Global Management System) » Transaction management, Payment methods » 3DSecure for Strong Customer Authentication, Payment methods » Alipay+, Payment methods » Alma Pay, Payment methods » Apple Pay, Payment methods » Bancontact, Payment methods » Billink, Payment methods » Bizum, and 50 more.

See all of them free

Component statuses may change independently during partial outages.

Recent PAY. Outages & Incidents

Incident history from the official PAY. status page, including resolution updates.

Incident: Transaction processingResolved Nov 5, 2026 · 7 minResolved

The incident has been resolved. The issue affected a single legacy server, which has been restarted. Transaction processing on our platform has returned to normal. --- [2026-11-05T09:32:19.964+01:00] (investigating) Following this morning’s platform issue, we have unfortunately identified some additional issues that are preventing certain transactions from being initiated. We are currently investigating the problem.

Delayed transaction & reporting GMS issuesResolved Nov 5, 2026 · 22 minResolved

This incident has been resolved. --- [2026-11-05T08:41:54.350+01:00] (investigating) We are currently experiencing slow access to our Admin Panel, and merchants may experience difficulties initiating transactions. --- [2026-11-05T08:29:13.695+01:00] (investigating) We see network issues, the multicore processing is available and up. Legacy processing is not available. We update you within 10 minutes

Incident: Delayed transaction processingResolved Nov 4, 2026 · 33 minResolved

This incident has been resolved. Some transactions initiated on our legacy platform experienced longer processing times than usual. However, there was no downtime, and transactions continued to be processed throughout the incident. Transactions processed through our Multicore platform were not affected and experienced no delays. --- [2026-11-04T11:19:37.855+01:00] (investigating) Due to an issue within our network, transactions processed through our legacy platform may experience delays. Transactions processed through our multicore platform are unaffected. Our team is investigating the issue. An update will follow as soon as more information is available.

PAY. Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a PAY. incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 12100.00% average · 22 days with incidentsNov 10

Going further back: PAY. uptime by month and every recorded PAY. outage.

Live PAY. Outage Reports

Problems reported by engineers using PAY.. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No PAY. problems reported yet.

Are you seeing PAY. problems too?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About PAY.

PAY. publishes a public status page at status.pay.nl covering 67 components, including MY.pay.nl, 3DSecure for Strong Customer Authentication and Support Ticket Center. PulsAPI tracks PAY. outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.

Over the past 30 days, PulsAPI has measured PAY. uptime at 100.00%. Response times, incident history, and SLA tracking for PAY. are available on the PulsAPI dashboard.

PAY. Status FAQ

Is PAY. down right now?

The verdict at the top of this page comes from the latest poll of the official PAY. status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if PAY. is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until PAY. recovers.

How do I check PAY. uptime history?

PulsAPI tracks PAY. uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever PAY. changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect PAY. outages?

PulsAPI reads the official PAY. status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual PAY. components?

Yes. PulsAPI monitors 65 individual PAY. components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when PAY. goes down?

Yes. Create a free account and subscribe to PAY.: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with PAY. to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot PAY. problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor PAY.?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so PAY. plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track PAY. with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services