PAY. logo

Is PAY. Down?

SaaSLive status, outages, and incident history

No. PAY. is up right now.

Every monitored PAY. system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · 60s while moving

Know the moment PAY. breaks

PAY. is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

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 while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

PAY. Component Status

The main PAY. systems on this page. All 64 are operational right now.

64operational
Clearing and settlement
Operational
Configuration and operations (Global Management System) » MY.pay.nl
Operational
Configuration and operations (Global Management System) » Operational management
Operational

61 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) » 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, Payment methods » Blik, and 49 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.

External incident: instant paymentsResolved Sep 24, 2026 · 4h 17mResolved

The payouts have been processed instantly. This incident has been resolved --- [2026-09-24T19:26:19.126+02:00] (identified) Rabobank has been experiencing issues since approximately **17:00**, impacting the availability of both **iDEAL and Pay by Bank**. Rabobank customers may experience failed or delayed transactions when making payments. Since approximately 18:30, we have seen improvements in the availability and processing of payments. However, the situation is **not yet fully stable**, and intermittent issues may still occur. We are continuing to monitor the situation closely. --- [2026-09-24T17:03:13.853+02:00] (investigating) Due to an outage at Rabobank, instant payments are currently unavailable. For more information, please visit: https://developer.rabobank.com/status

External: Increased decline rate for ABN AMRO card transactionsResolved Sep 22, 2026 · 35 minResolved

This incident has been resolved. --- [2026-09-22T08:36:15.541+02:00] (identified) We are actively monitoring the situation. --- [2026-09-22T08:31:41.088+02:00] (identified) We are actively monitoring the situation. --- [2026-09-22T08:31:34.398+02:00] (monitoring) We are actively monitoring the situation. --- [2026-09-22T08:29:39.250+02:00] (investigating) We are currently receiving reports that transactions with ABN AMRO payment cards are being declined at physical payment terminals. The cause is currently under investigation. At this time, the issue appears to be specifically affecting transactions with ABN AMRO payment cards. We will update this status message as soon as more information becomes available. See more: https://allestoringen.nl/en/status/abn-amro/

Delayed Submission of Domestic Mastercard POS TransactionsResolved Sep 21, 2026 · 0 minResolved

A limited number of domestic Mastercard POS transactions from September 12 experienced delayed processing. The incident did not impact the processing or acceptance of the payments themselves. Transactions were successfully completed at the point of sale. The issue was limited to the subsequent submission of these transactions to Mastercard. Domestic Mastercard POS transactions must be submitted within five days. Due to the delay, some of the affected transactions from September 12 were submitted shortly after this processing window. All affected transactions have since been successfully recovered and processed. Merchants have received settlement of these transactions through the regular settlement process. For some cardholders, depending on their issuing bank, the original transaction may first appear as a correction or reversal, followed by a new debit for the same transaction amount. This is an expected result of the recovery process and does not represent a duplicate charge. The incident has been fully resolved. We have also enhanced our monitoring to detect similar processing delays at an earlier stage and prevent recurrence. No action is required from merchants or partners.

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 history49 days observed
Aug 8100.00% average · 6 days with incidentsSep 25

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.

Something wrong with PAY. on your end?

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 99.96%. 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 a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

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 99.96%. 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 a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual PAY. components?

Yes. PulsAPI monitors 64 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

2463+ 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