Poplapay Outage History

The settlement file for the affected transactions has been corrected and resubmitted for processing. Based on the current information, we expect payouts to be processed one day later than usual. Processing has not yet been confirmed, and we’ll share another update if the expected timing changes. Affected transactions: Amex card transactions, Nets Finland acquirer, October 6th Impact: Delayed settlement payouts; no transactions are lost

Issue resolved around 12.45 CEST

The acquirer implemented a fix and traffic is recovering

The failed settlement file has been reprocessed and delivered, and a mitigation has been applied to prevent recurrence. We apologize for the inconvenience.

We apologize for the inconvenience caused by an issue affecting settlement processing for Npay terminals using Nets Finland acquiring. On June 3rd, a technical issue caused settlement processing to fail, preventing affected settlements from being submitted to the acquirer as scheduled. We corrected that error and submitted the settlements the following day. In correcting the previous error, however, we unfortunately overlooked a detail that then caused the settlement run for June 4th to fail. This has now been corrected, and the settlements have been submitted successfully, but unfortunately payouts for June 4th will be delayed. No action from merchants is required. The underlying issue that caused both problems was fixed earlier, so no further disruption is expected. We sincerely apologize for the disruption. We will be providing more information early next week.

The Nordic acquiring outage has been resolved. Card payments have been going through successfully since approximately 14:43 CEST / 15:43 EEST, and success rates are back to normal. We are continuing to monitor the service to make sure it stays stable before closing the incident. No action is needed from merchants. We apologise for the disruption and will post a final update once monitoring is complete.

Authorizations working again since 17:12 CEST / 18:12 EEST. Monitoring for now, another update will come when incident closed.

working since 18:50 EET

There was an authorization incident 12:11–12:34, which has since resolved. Around 50-80% of authorizations for Finnish acquiring failed during that time. We are still investigating the root cause, but the issue is unlikely to repeat itself – but we will keep monitoring the situation.

We are no longer seeing abnormal connectivity issues. We will continue to monitor the situation.

Upstream provider has applied a fix and authorizations are succeeding again

A fix has been implemented and we are monitoring the results.

Acquirer is reporting issue as resolved, and we are no longer seeing failed authorizations

The acquirer has reported a fix has been implemented and we are seeing transaction failures returning to normal amounts. We'll keep monitoring the situation.

The errors seem to be related to an ongoing incident at Nordea.

There was a brief downtime in Nets Finland authorizations. The issue started at 14:30 EEDT and was resolved at 14:34 EEDT. Cause is not known, but the situation has normalized. We continue to monitor the situation.

Returned to normal since 12:38 Finland local time. Monitoring.

The fix for newly created settlements was confirmed working. Work is still ongoing for resubmitting the failed settlements.

The failed batches have been resubmitted to the acquirer, and we are awaiting confirmation of their successful processing. We apologize for the trouble caused by this.

The issue has been located to a third party service, which now appears to be working normally again. The authorization success rates are back to normal, and we are monitoring the situation.

Yesterday's settlements have now been successfully sent to Nets Finland. They will be processed one day late from the usual. We apologise for the trouble this has caused.

We are seeing no more failing transactions since 9:12. We'll keep monitoring the situation closely for now.

All changes have been rolled back. Our production test devices worked continually, and most metrics were normal, but due to a partial outage of our monitoring related to the change, we could not rule out possible issues.