Notice September 15, 2026 - Detected by Pingoru
- Sep 15, 2026, 01:12 PM UTC
- Resolved
- Sep 22, 2026, 07:11 AM UTC
- Duration
- 6d 17h
Affected: Settlement
Timeline · 4 updates
-
investigating Sep 15, 2026, 01:12 PM UTC
We would like to inform you about technical issues from a third party affecting settlements for accounts at Nordfyns Bank which have been moved and updated as part of the merger with Middelfart Sparekasse. We have contacted the party involved and will update you as soon as more information becomes available. Due to this, the funds associated with the transactions concerned will be credited to your account with a delay. We are sorry for the inconvenience that this may cause.
-
investigating Sep 18, 2026, 08:20 AM UTC
The root cause remains under investigation. Consequently, settlement funds for these accounts will be delayed. We apologize for the inconvenience and appreciate your patience.
-
monitoring Sep 18, 2026, 01:29 PM UTC
We have received information that the technical issue affecting Nordfyns Bank settlements has been identified and a fix has been implemented. Impacted transactions are currently being processed. We are monitoring the results to confirm stability and will provide a final update once complete. Thank you for your patience.
-
resolved Sep 22, 2026, 07:11 AM UTC
We can now confirm that the technical issue affecting settlements has been fully resolved. The processing of all impacted transactions is now complete. You can expect these settlements to be reflected in your account by September 23, 2026. We apologize for the inconvenience this may have caused and appreciate your patience as we worked to stabilize these payments.
Read the full incident report →
- Detected by Pingoru
- Jul 27, 2026, 07:28 AM UTC
- Resolved
- Jul 28, 2026, 11:58 AM UTC
- Duration
- 1d 4h
Affected: Reports
Timeline · 3 updates
-
monitoring Jul 27, 2026, 07:28 AM UTC
Due to a technical issue, acquiring IC++ for 2026-07-25 and 2026-07-26 will be delayed and is expected to be delivered today 2026-07-27. Settlements are unaffected. We apologise for the inconvenience.
-
monitoring Jul 28, 2026, 07:15 AM UTC
The IC++ report for 2026-07-26 has been successfully delivered late 2026-07-27. The report for 2026-07-25 is still delayed.
-
resolved Jul 28, 2026, 11:58 AM UTC
The IC++ report for 2026-07-25 has been successfully delivered 2026-07-28.
Read the full incident report →
- Detected by Pingoru
- Jul 15, 2026, 04:30 AM UTC
- Resolved
- Jul 15, 2026, 05:01 AM UTC
- Duration
- 31m
Affected: Worldline Instore
Timeline · 4 updates
-
investigating Jul 15, 2026, 04:30 AM UTC
We are currently experiencing a service disruption that is affecting Worldline Instore authorizations. The issue is being investigated as a matter of urgency and the service will be restored at the earliest possible opportunity. Updates will be provided as soon as additional information becomes available.
-
monitoring Jul 15, 2026, 04:53 AM UTC
We confirm that as of 06:51 CET, we have seen improved stability and service has been resumed. We will continue to monitor the services to ensure stability.
-
monitoring Jul 15, 2026, 04:54 AM UTC
We are continuing to monitor for any further issues.
-
resolved Jul 15, 2026, 05:01 AM UTC
Due to a technical problem might have experienced problems to perform transactions using the Worldline Instore platform between 06:06 and 06:51 CET 2026-07-15 The problem has been resolved. We apologise for any inconvenience.
Read the full incident report →
- Detected by Pingoru
- Jun 02, 2026, 09:01 AM UTC
- Resolved
- Jun 03, 2026, 06:06 AM UTC
- Duration
- 21h 4m
Affected: SettlementReports
Timeline · 2 updates
-
monitoring Jun 02, 2026, 09:01 AM UTC
We would like to inform you about third party delays affecting settlements scheduled for the 2026-06-02. As a result, the funds and reports related to the affected transactions for certain merchants will be credited to your account with a delay. The issue has been resolved and we apologize for the inconvenience.
-
resolved Jun 03, 2026, 06:06 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 21, 2026, 07:30 AM UTC
- Resolved
- May 21, 2026, 02:01 PM UTC
- Duration
- 6h 30m
Affected: Worldline Checkout
Timeline · 5 updates
-
investigating May 21, 2026, 07:30 AM UTC
We are currently experiencing a service disruption that is affecting Worldline Checkout authorizations. The issue is being investigated as a matter of urgency and the service will be restored at the earliest possible opportunity.
-
identified May 21, 2026, 07:58 AM UTC
The disturbance is due to operational issues at Nets. This may affect authorizations and other payment operations that rely on Nets acquiring. Worldline’s acquiring service remains operational. We are monitoring the situation closely and will provide an update as soon as more information is available.
-
monitoring May 21, 2026, 12:15 PM UTC
A fix has been implemented by Nets. We will continue to monitor the services to ensure stability.
-
monitoring May 21, 2026, 01:20 PM UTC
The issue appears to be mitigated. We are continuing to monitor closely.
-
resolved May 21, 2026, 02:01 PM UTC
There is an improvement in service operations, and transactions are now proceeding normally. The incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 11, 2026, 09:10 AM UTC
- Resolved
- Mar 11, 2026, 01:07 PM UTC
- Duration
- 3h 57m
Affected: Reports
Timeline · 2 updates
-
monitoring Mar 11, 2026, 09:10 AM UTC
We would like to inform you of a technical issue resulting in a delay of Acquiring IC++ reports scheduled for delivery on 2026-03-11. Reports will be delayed with 1 day. Please note that settlement payouts are not affected by this incident. We apologize for any inconvenience this may cause and appreciate your patience and understanding.
-
resolved Mar 11, 2026, 01:07 PM UTC
This incident has been resolved.
Read the full incident report →
Critical February 25, 2026 - Detected by Pingoru
- Feb 25, 2026, 02:11 PM UTC
- Resolved
- Feb 25, 2026, 05:23 PM UTC
- Duration
- 3h 11m
Affected: Worldline Instore
Timeline · 3 updates
-
investigating Feb 25, 2026, 02:11 PM UTC
We are currently experiencing a service disruption affecting authorizations. The issue is being investigated as a matter of urgency and the service will be fully restored at the earliest possible opportunity. Updates will be provided as soon as additional information becomes available. We apologize for any inconvenience.
-
investigating Feb 25, 2026, 05:00 PM UTC
We are still experiencing a service disruption affecting authorizations. Updates will be provided as soon as additional information becomes available. We apologize for any inconvenience.
-
resolved Feb 25, 2026, 05:23 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 06, 2026, 02:07 PM UTC
- Resolved
- Feb 06, 2026, 02:07 PM UTC
- Duration
- –
Affected: Authorizations
Timeline · 1 update
-
resolved Feb 06, 2026, 02:07 PM UTC
Yesterday, Thursday 15:25 CET a deployment failure in Access Gateway lead to connection problems. This affected many transactions and was responded with error code 500. Issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 12, 2025, 08:23 AM UTC
- Resolved
- Nov 12, 2025, 08:50 AM UTC
- Duration
- 27m
Affected: Worldline Instore
Timeline · 1 update
-
resolved Nov 12, 2025, 08:23 AM UTC
On Saturday, November 8th 2025, Worldline had an incident where some transactions were given the wrong timestamp. The incident lasted for about 27 minutes and was caused by a server error. The issue has been corrected and the error is being investigated. The affected transactions have been cleared and all corrected with the correct time stamp.
Read the full incident report →
- Detected by Pingoru
- Nov 08, 2025, 03:21 PM UTC
- Resolved
- Nov 08, 2025, 03:58 PM UTC
- Duration
- 37m
Affected: Worldline Instore
Timeline · 2 updates
-
investigating Nov 08, 2025, 03:21 PM UTC
We are currently investigating an issue with our terminals and updating our status page continuously with information.
-
resolved Nov 08, 2025, 03:58 PM UTC
We’ve found the issue and an update has been implemented. Please perform a daily settlement and the terminal will work.
Read the full incident report →
- Detected by Pingoru
- Nov 04, 2025, 02:31 PM UTC
- Resolved
- Nov 06, 2025, 12:41 PM UTC
- Duration
- 1d 22h
Affected: Settlement
Timeline · 2 updates
-
investigating Nov 04, 2025, 02:31 PM UTC
We would like to inform you of a technical issue affecting a small number of USD and EUR settlements scheduled for 2025-10-29. The matter is currently under urgent investigation. We apologize for any inconvenience this may cause.
-
resolved Nov 06, 2025, 12:41 PM UTC
We are pleased to inform you that the issue has now been successfully resolved. The settlements originally scheduled for 2025-10-29 have been resent today, 2025-11-06. We apologies for any inconvenience this may have caused.
Read the full incident report →
- Detected by Pingoru
- Sep 22, 2025, 12:59 PM UTC
- Resolved
- Sep 24, 2025, 05:42 AM UTC
- Duration
- 1d 16h
Affected: Mobile terminal connectivity
Timeline · 5 updates
-
investigating Sep 22, 2025, 12:59 PM UTC
We would like to inform you about an ongoing issue with an external mobile connectivity provider as of 12:00 CET on 22 September. Due to this you may experience connectivity disruptions when performing transactions using our mobile terminals in Sweden with Telia network and Essential 1 simcards. We have contacted the party involved and will update you as soon as more information becomes available. Thank you for your patience and understanding.
-
identified Sep 22, 2025, 03:04 PM UTC
This incident has been identified and service degradation is not isolated to Essentials 1.
-
identified Sep 23, 2025, 06:24 AM UTC
We are continuing to work on a fix for this issue.
-
monitoring Sep 23, 2025, 08:40 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 24, 2025, 05:42 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 01, 2025, 07:52 AM UTC
- Resolved
- Aug 01, 2025, 04:00 PM UTC
- Duration
- 8h 8m
Affected: SettlementReports
Timeline · 3 updates
-
identified Aug 01, 2025, 07:52 AM UTC
We would like to inform you about technical issues affecting settlements and reporting scheduled for August 1, 2025. Due to these issues, funds associated with affected transactions may be credited to customer accounts later than expected. Consequently, a delay in reporting of the associated transactions can also be anticipated. Our teams have identified the cause of the technical issues and are assessing the potential impact of this incident. We will provide further updates as more information becomes available. We apologize for any inconvenience this may cause and appreciate your understanding.
-
monitoring Aug 01, 2025, 09:31 AM UTC
We would like to update you regarding the reported technical issues affecting settlements and reporting scheduled for August 1, 2025. Settlements have now been processed, and reports are currently being generated. As a result, the delays are not expected to extend beyond today’s date. The scope of this incident has been reduced to impact only reporting, which is now delayed relative to the normal schedule. We will continue to monitor the situation and provide further updates as needed. We apologize for any inconvenience this may cause and appreciate your understanding.
-
resolved Aug 01, 2025, 09:16 PM UTC
We would like to confirm that settlements were processed on time and reports have now also been processed and delivered in full. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Jul 14, 2025, 05:01 PM UTC
- Resolved
- Jul 14, 2025, 06:42 PM UTC
- Duration
- 1h 40m
Affected: Mobile terminal connectivity
Timeline · 3 updates
-
investigating Jul 14, 2025, 05:01 PM UTC
We would like to inform you about an ongoing issue with an external mobile connectivity provider. Due to this you may experience connectivity disruptions when performing transactions using our mobile terminals. We have contacted the party involved and will update you as soon as more information becomes available. Thank you for your patience and understanding.
-
monitoring Jul 14, 2025, 05:45 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 14, 2025, 06:42 PM UTC
We have been closely monitoring since the corrective action was taken, and have observed no additional impacts. We are considering this issue resolved at this time.
Read the full incident report →
- Detected by Pingoru
- Jul 01, 2025, 07:13 AM UTC
- Resolved
- Jul 02, 2025, 06:53 AM UTC
- Duration
- 23h 40m
Affected: Reports
Timeline · 2 updates
-
identified Jul 01, 2025, 07:13 AM UTC
As a result of a technical error, those expecting today's acquiring reports should anticipate a slight delay in delivery, with reports arriving later than usual. This incident is currently limited to the generation and delivery of reports, settlements are unaffected at this moment. Updates will be shared as more information becomes available. We apologize for the inconvenience this may cause.
-
resolved Jul 02, 2025, 06:53 AM UTC
We would like to provide an update on the previously communicated delays affecting acquiring reports. The affected reports have been generated and delivered. Please note that only the generation and delivery of reports were impacted. We apologize for any inconvenience caused and thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Jun 15, 2025, 06:01 PM UTC
- Resolved
- Jun 16, 2025, 05:23 PM UTC
- Duration
- 23h 22m
Affected: Reports
Timeline · 2 updates
-
identified Jun 15, 2025, 06:01 PM UTC
We would like to inform you of a technical issue resulting in a delay of Acquiring IC++ reports scheduled for delivery on 2025-06-14 and 2025-06-15. Please note that settlement payouts are not affected by this incident. We apologize for any inconvenience this may cause and appreciate your patience and understanding.
-
resolved Jun 16, 2025, 05:23 PM UTC
We would like to provide an update on the previously communicated delays affecting IC++ acquiring reports originally scheduled for delivery on 2025-06-14 and 2025-06-15. The affected reports have been generated and delivered. Please note that settlements remain unaffected; only the generation and delivery of reports were impacted. We apologize for any inconvenience caused and thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- May 23, 2025, 11:03 AM UTC
- Resolved
- May 23, 2025, 12:52 PM UTC
- Duration
- 1h 49m
Affected: Mobile terminal connectivity
Timeline · 3 updates
-
investigating May 23, 2025, 11:03 AM UTC
We would like to inform you about an ongoing issue with an external mobile connectivity provider. Due to this you may experience connectivity disruptions when performing transactions using our mobile terminals. We have contacted the party involved and will update you as soon as more information becomes available. Thank you for your patience and understanding.
-
monitoring May 23, 2025, 12:10 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved May 23, 2025, 12:52 PM UTC
We have been closely monitoring since the corrective action was taken, and have observed no additional impacts. We are considering this issue resolved at this time. We apologize for the service interruption and we thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Apr 30, 2025, 06:49 AM UTC
- Resolved
- Apr 30, 2025, 10:34 AM UTC
- Duration
- 3h 45m
Affected: Reports
Timeline · 3 updates
-
investigating Apr 30, 2025, 06:49 AM UTC
We would like to inform you of a technical issue currently affecting the generation of settlement reports scheduled for April 30, 2025. At this time, no reports have been generated. Our team is actively investigating the issue and working to initiate the report generation process. We will provide further updates as soon as more information becomes available. Please note that settlement payouts are not affected by this incident. We apologize for any inconvenience this may cause and appreciate your patience and understanding.
-
monitoring Apr 30, 2025, 07:44 AM UTC
The root cause has been identified, and report generation is currently in progress. Report delivery today will be approximately 3 hours later than usual. This delay is not expected to affect the delivery of the afternoon IC++ report. We will provide a final update once the reports have been successfully delivered. Thank you for your continued patience and understanding.
-
resolved Apr 30, 2025, 10:34 AM UTC
All settlement reports scheduled for the morning of 2025-04-30 have been successfully delivered. No further delays are expected."
Read the full incident report →
- Detected by Pingoru
- Apr 29, 2025, 07:13 AM UTC
- Resolved
- Apr 29, 2025, 02:30 PM UTC
- Duration
- 7h 17m
Affected: Mobile terminal connectivity
Timeline · 3 updates
-
investigating Apr 29, 2025, 07:13 AM UTC
We would like to inform you about an ongoing issue with an external mobile connectivity provider. Due to this you may experience connectivity disruptions on your mobile terminal. We have contacted the party involved and will update you as soon as more information becomes available. Thank you for your patience and understanding.
-
monitoring Apr 29, 2025, 12:53 PM UTC
A fix has been implemented by our partner but we are still impacted by minor connectivity issues. We will continue to monitor the service to ensure stability.
-
resolved Apr 29, 2025, 02:30 PM UTC
We have been closely monitoring since the corrective action was taken, and have observed no additional impacts. We are considering this issue resolved at this time. We apologize for the service interruption and we thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Apr 27, 2025, 10:10 AM UTC
- Resolved
- Apr 28, 2025, 02:02 PM UTC
- Duration
- 1d 3h
Affected: SettlementReports
Timeline · 4 updates
-
identified Apr 27, 2025, 10:10 AM UTC
We would like to inform you that we have identified a technical issue affecting the processing of certain transactions since 2025-04-25. As a result, transactions associated with this issue may be processed with a delay. The scope of this issue is being investigated as a matter of urgency and corrective actions will be taken at the earliest possible opportunity. We apologize for the inconvenience that this may cause.
-
identified Apr 27, 2025, 12:51 PM UTC
We would like to inform you that the scope of this issue has been determined and the affected transactions are being resubmitted for processing today (2025-04-27). An update will be provided as soon as we know more about the results of the resubmission of the transactions concerned. Thank you for your patience and understanding.
-
monitoring Apr 27, 2025, 08:16 PM UTC
We would like to inform you that the resubmission of the affected transactions was successful. We will continue to monitor processing through tomorrow (2025-04-28). Tomorrow’s (2025-04-28) reports will include the re-processed transactions. Thank you for your patience and understanding.
-
resolved Apr 28, 2025, 02:02 PM UTC
We would like to inform you that the resubmission of the affected transactions was successful. We have not identified any further impact during our monitoring since corrective action was taken. Todays (2025-04-28) reports include the re-processed transactions. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Apr 27, 2025, 07:44 AM UTC
- Resolved
- Apr 28, 2025, 05:46 PM UTC
- Duration
- 1d 10h
Affected: Reports
Timeline · 4 updates
-
investigating Apr 27, 2025, 07:44 AM UTC
We would like to inform you that we are currently investigating an issue related to generating and the delivery of acquiring reporting. This incident is limited to acquiring reporting. Updates will be shared as more information becomes available. We apologize for the inconvenience this may cause.
-
monitoring Apr 27, 2025, 04:47 PM UTC
As a result of a technical error, acquiring reports originally scheduled for delivery on 2025-04-26 and 2025-04-27 have been delayed. The reports will now arrive tomorrow, 2025-04-28. This incident is limited to the generation and delivery of reports; settlements remain unaffected. We will continue to monitor this incident to ensure the reports are delivered successfully. We apologize for any inconvenience caused and thank you for your patience and understanding.
-
monitoring Apr 28, 2025, 02:26 PM UTC
We would like to provide an update on the previously communicated delays affecting reports originally scheduled for delivery on 2025-04-26 and 2025-04-27. The affected reports are currently being generated and delivered throughout the afternoon. As a result of these delays, the delivery of reports scheduled for 2025-04-28, will also be later than usual. Please note that settlements remain unaffected; only the generation and delivery of reports are impacted. We will continue to monitor this incident to ensure all reports are delivered successfully. We apologize for any inconvenience caused and thank you for your patience and understanding.
-
resolved Apr 28, 2025, 05:46 PM UTC
We would like to inform you that the acquiring reports scheduled for dates: 2025-04-26, 2025-04-27 and 2025-04-28 have all been successfully delivered. Thank you for your patience and understanding.
Read the full incident report →
- Detected by Pingoru
- Apr 03, 2025, 07:59 AM UTC
- Resolved
- Apr 04, 2025, 08:27 AM UTC
- Duration
- 1d
Affected: Reports
Timeline · 3 updates
-
monitoring Apr 03, 2025, 07:59 AM UTC
We want to inform you of a delay in the IC++ reports scheduled for today, 2025-04-03. Those expecting today's acquiring IC++ report should anticipate a one-day delay in delivery. This incident only affects the delivery of reporting, settlements are unaffected. We apologize for any inconvenience this may cause and appreciate your patience.
-
monitoring Apr 04, 2025, 06:22 AM UTC
The IC++ reports for settlement date 2025-04-03 were successfully delivered today, 2025-04-04, at 06:00 AM CET.
-
resolved Apr 04, 2025, 08:27 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 31, 2025, 02:40 PM UTC
- Resolved
- Apr 01, 2025, 06:11 AM UTC
- Duration
- 15h 31m
Affected: Reports
Timeline · 2 updates
-
monitoring Mar 31, 2025, 02:40 PM UTC
We want to inform you of a delay in the IC++ reports scheduled for today, 2025-03-31. Those expecting today's acquiring IC++ report should anticipate a slight delay in delivery. This incident only affects the delivery of reporting, settlements are unaffected. The report jobs is expected to complete at 17:30 CET We apologize for any inconvenience this may cause and appreciate your patience.
-
resolved Apr 01, 2025, 06:11 AM UTC
All reports delivered by 19:30 CET
Read the full incident report →
- Detected by Pingoru
- Mar 25, 2025, 11:04 AM UTC
- Resolved
- Mar 26, 2025, 08:51 AM UTC
- Duration
- 21h 46m
Affected: SettlementReports
Timeline · 2 updates
-
investigating Mar 25, 2025, 11:04 AM UTC
We would like to inform about technical issues affecting settlements and reporting scheduled for March 25, 2025. Due to these issues, the funds associated with the relevant transactions may be credited to some customers accounts one day later than expected. As a result, a delay in reporting of the associated transactions may also be anticipated. We are currently investigating the potential impact of this incident and will provide further updates as soon as more information is available. We apologize for any inconvenience this may cause and appreciate your understanding.
-
resolved Mar 26, 2025, 08:51 AM UTC
We would like to inform you that the technical issues affecting settlements and reporting scheduled for March 25, 2025, have been resolved. As a result of the incident, funds associated with the relevant transactions are being credited to affected customers accounts with a delay of one day. Consequently, the reporting of these transactions will be included in todays (March 26, 2025) reporting, also delayed by one day. Thank you for your patience and understanding throughout this process. We apologize for any inconvenience this may have caused.
Read the full incident report →
- Detected by Pingoru
- Feb 28, 2025, 03:16 PM UTC
- Resolved
- Feb 28, 2025, 04:52 PM UTC
- Duration
- 1h 35m
Affected: Reports
Timeline · 2 updates
-
monitoring Feb 28, 2025, 03:16 PM UTC
We’d like to inform you that the IC++ reports scheduled for 2025-02-28 will be slightly delayed. The report job is currently under way, and all reports are expected to be delivered within the next hour. This only impacts report delivery, settlements remain unaffected. Thank you for your patience, and we apologize for any inconvenience.
-
resolved Feb 28, 2025, 04:52 PM UTC
The IC++ report job has now completed, and all reports were successfully delivered by 5:30 PM CET. Thank you for your patience.
Read the full incident report →