Solmio-kassa Status - Incident history https://solmio-kassa.instatus.com Solmio-kassa Tue, 19 May 2026 15:18:37 +0000 Useilla maksunvälittäjillä häiriöitä Type: Incident Duration: 2 hours and 25 minutes Affected Components: Viva wallet, Verifone SAIO Intercard, Worldline, Elavon, Nets Finland May 19, 15:18:37 GMT+0 - Investigating - **Update** \- Acquiring side issue affecting multiple PSPs. May 19, 2026 - 17:56 EEST **Investigating** \- We see a degradation in acquiring connection to Finland acquiring, causing failures in payments affecting some Finnish merchants. May 19, 16:02:35 GMT+0 - Monitoring - Monitoring - working since 18:50 EET May 19, 17:43:09 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 hours and 25 minutes

Affected Components: , , , ,

<p><small>May <var data-var='date'> 19</var>, <var data-var='time'>15:18:37</var> GMT+0</small><br><strong>Investigating</strong> - **Update** \- Acquiring side issue affecting multiple PSPs. May 19, 2026 - 17:56 EEST **Investigating** \- We see a degradation in acquiring connection to Finland acquiring, causing failures in payments affecting some Finnish merchants. .</p> <p><small>May <var data-var='date'> 19</var>, <var data-var='time'>16:02:35</var> GMT+0</small><br><strong>Monitoring</strong> - Monitoring - working since 18:50 EET.</p> <p><small>May <var data-var='date'> 19</var>, <var data-var='time'>17:43:09</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 19 May 2026 15:18:37 +0000 https://solmio-kassa.instatus.com/incident/cmpcs2ott011mp9rt5vea0fmi https://solmio-kassa.instatus.com/incident/cmpcs2ott011mp9rt5vea0fmi Nets varmennuksissa häiriöitä Type: Incident Duration: 6 hours and 7 minutes Affected Components: Nets Finland Apr 29, 12:12:04 GMT+0 - Monitoring - **Monitoring** \- 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. Apr 29, 15:52:51 GMT+0 - Resolved - This incident has been resolved. Apr 29, 09:46:03 GMT+0 - Investigating - **Investigating** \- 12:11 Finland time - debit authorization degraded for Finnish acquiring. 12:11 alkaen katevarmennusyhteydessä ongelmia, selvitys käynnissä Type: Incident

Duration: 6 hours and 7 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>12:12:04</var> GMT+0</small><br><strong>Monitoring</strong> - **Monitoring** \- 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..</p> <p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>15:52:51</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>09:46:03</var> GMT+0</small><br><strong>Investigating</strong> - **Investigating** \- 12:11 Finland time - debit authorization degraded for Finnish acquiring. 12:11 alkaen katevarmennusyhteydessä ongelmia, selvitys käynnissä.</p> ]]> Wed, 29 Apr 2026 09:46:03 +0000 https://solmio-kassa.instatus.com/incident/cmojvdyqg00mk1ru572h4bmz5 https://solmio-kassa.instatus.com/incident/cmojvdyqg00mk1ru572h4bmz5 Login & API Disruption Type: Incident Affected Components: Payment Backend Mar 24, 10:45:00 GMT+0 - Resolved - This incident has beOn March 24, 2026 between 12:45–13:00 UTC, users were unable to log in or access the API for approximately 15 minutes. This was caused by a database update that ran during our infrastructure migration and took longer than expected on production. Service was restored immediately once the update completed. No data was lost and the migration itself was successful.en resolved. Mar 24, 11:00:00 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Affected Components:

<p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>10:45:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has beOn March 24, 2026 between 12:45–13:00 UTC, users were unable to log in or access the API for approximately 15 minutes. This was caused by a database update that ran during our infrastructure migration and took longer than expected on production. Service was restored immediately once the update completed. No data was lost and the migration itself was successful.en resolved..</p> <p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 24 Mar 2026 10:45:00 +0000 https://solmio-kassa.instatus.com/incident/cmn4l8lxn07kws5skkugydzzm https://solmio-kassa.instatus.com/incident/cmn4l8lxn07kws5skkugydzzm Viva.com palvelukatko Type: Incident Duration: 1 hour and 46 minutes Affected Components: Viva wallet Feb 24, 14:26:39 GMT+0 - Investigating - We are currently investigating this incident. Feb 24, 14:53:00 GMT+0 - Monitoring - Päätteet käynnistyvät ja maksut menevät läpi Feb 24, 16:12:36 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 hour and 46 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>14:26:39</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>14:53:00</var> GMT+0</small><br><strong>Monitoring</strong> - Päätteet käynnistyvät ja maksut menevät läpi.</p> <p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>16:12:36</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 24 Feb 2026 14:26:39 +0000 https://solmio-kassa.instatus.com/incident/cmm0p8br900casioqz8owdf91 https://solmio-kassa.instatus.com/incident/cmm0p8br900casioqz8owdf91 Nets Finland Mastercard transaction failures Type: Incident Duration: 23 hours and 56 minutes Affected Components: Verifone SAIO Intercard, App, Viva wallet, Worldline, Payment Backend, Nets Finland, Elavon Jan 5, 13:32:52 GMT+0 - Monitoring - ## **Monitoring** 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. Jan 5, 16:28:11 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Jan 6, 08:33:19 GMT+0 - Resolved - This incident has been resolved. Jan 5, 08:37:06 GMT+0 - Investigating - ## **Investigating** We are seeing Mastercard transactions failing with Nets Finland acquiring. VISA seems unaffected. We are investigating. More info -> <https://npaystatus.nexigroup.com/> Type: Incident

Duration: 23 hours and 56 minutes

Affected Components: , , , , , ,

<p><small>Jan <var data-var='date'> 5</var>, <var data-var='time'>13:32:52</var> GMT+0</small><br><strong>Monitoring</strong> - ## **Monitoring** 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..</p> <p><small>Jan <var data-var='date'> 5</var>, <var data-var='time'>16:28:11</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Jan <var data-var='date'> 6</var>, <var data-var='time'>08:33:19</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jan <var data-var='date'> 5</var>, <var data-var='time'>08:37:06</var> GMT+0</small><br><strong>Investigating</strong> - ## **Investigating** We are seeing Mastercard transactions failing with Nets Finland acquiring. VISA seems unaffected. We are investigating. More info -> <https://npaystatus.nexigroup.com/>.</p> ]]> Mon, 5 Jan 2026 08:37:06 +0000 https://solmio-kassa.instatus.com/incident/cmk0wq72i004111hrf0au26z8 https://solmio-kassa.instatus.com/incident/cmk0wq72i004111hrf0au26z8 Intermittent Connectivity Isuues - Tidypay Type: Incident Duration: 1 minute Aug 20, 12:14:57 GMT+0 - Investigating - We are currently investigating this incident. Aug 20, 12:16:05 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 minute

<p><small>Aug <var data-var='date'> 20</var>, <var data-var='time'>12:14:57</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Aug <var data-var='date'> 20</var>, <var data-var='time'>12:16:05</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 20 Aug 2025 12:14:57 +0000 https://solmio-kassa.instatus.com/incident/cmejxqtj400knmbldbukibfby https://solmio-kassa.instatus.com/incident/cmejxqtj400knmbldbukibfby Elavonin asiakkaalla maksupalvelujen tarjoajasta johtuvaa viivettä Type: Incident Duration: 18 days, 6 hours and 5 minutes Aug 18, 10:00:00 GMT+0 - Investigating - Alla toimittajan viesti: We want to acknowledge the disruption caused by yesterday evening’s processing delays and today's service outage. We understand how critical uninterrupted service is to your business operations, and we take full responsibility for the impact this has had on our joint merchants. Our teams have completed a thorough investigation and identified a single underlying root cause linking both incidents. We are actively implementing changes to ensure that even under the same conditions, the outcome will be different — and service will remain stable. These efforts are part of our broader commitment to building greater resilience and reliability into our systems. As part of our recovery and remediation process, transaction batch processing will proceed with delays. This **may affect settlement** timeline for some merchants by **up to** **one business day**, depending on their settlement configuration with Elavon. We sincerely apologise for the inconvenience and any operational challenges this may have caused. Please know that resolving this fully — and preventing a recurrence — is our top priority. Thank you for your continued patience and partnership. Aug 25, 06:56:33 GMT+0 - Monitoring - Päivitystä viikonlopulta, maksut siiirretty pankkiin ja pitäisi mennä maksuun pian. Valued Customer, We sincerely apologize for the inconvenience caused by the delayed payouts. We understand how crucial timely settlements are for your operations. \*\*What’s happening:\*\* A technical issue led to a delay in transferring funds. Please rest assured we are working closely with our partner bank to finalize all transfers by the end of business today. Once released, funds will process according to the standard timing for bank transfers. \*\*What you might notice:\*\* Some cardholders may have seen a duplicate charge - Good news is that this issue has already been identified and corrected in our systems—duplicates have been refunded automatically. \*\*Next steps:\*\* \* Bank transfers are being finalized today. \* Any duplicate charges are refunded simultaneously as the bank transfer finalization today. \* Expect your funds to arrive following the usual timeframe. We truly appreciate your patience and continue to strive for reliable service. Thank you for your understanding and continued partnership. If you or your customers notice anything unusual, we encourage you to let us know immediately - our team is standing by to help: \[\*\*support@tidypay.com\*\*\](mailto:support@tidypay.com). Aug 22, 10:34:55 GMT+0 - Identified - Heti kun viimeistelyt ovat valmiit toimittajan ja pankin välillä, lähtevät käsittelemättömät tilitykset käsittelyyn. Alla vielä päivitys toimijalta: We want to provide you with an update regarding the ongoing settlement delay. Our team is confident that we have identified the root cause of the issue and are currently in the final stages of confirmation with the bank. As soon as this final verification is complete, we will immediately begin processing all outstanding settlement batches. We sincerely apologize for the continued delay and truly appreciate your patience and understanding as we work to bring this to full resolution. Sep 5, 16:05:20 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 18 days, 6 hours and 5 minutes

<p><small>Aug <var data-var='date'> 18</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br><strong>Investigating</strong> - Alla toimittajan viesti: We want to acknowledge the disruption caused by yesterday evening’s processing delays and today's service outage. We understand how critical uninterrupted service is to your business operations, and we take full responsibility for the impact this has had on our joint merchants. Our teams have completed a thorough investigation and identified a single underlying root cause linking both incidents. We are actively implementing changes to ensure that even under the same conditions, the outcome will be different — and service will remain stable. These efforts are part of our broader commitment to building greater resilience and reliability into our systems. As part of our recovery and remediation process, transaction batch processing will proceed with delays. This **may affect settlement** timeline for some merchants by **up to** **one business day**, depending on their settlement configuration with Elavon. We sincerely apologise for the inconvenience and any operational challenges this may have caused. Please know that resolving this fully — and preventing a recurrence — is our top priority. Thank you for your continued patience and partnership..</p> <p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>06:56:33</var> GMT+0</small><br><strong>Monitoring</strong> - Päivitystä viikonlopulta, maksut siiirretty pankkiin ja pitäisi mennä maksuun pian. Valued Customer, We sincerely apologize for the inconvenience caused by the delayed payouts. We understand how crucial timely settlements are for your operations. \*\*What’s happening:\*\* A technical issue led to a delay in transferring funds. Please rest assured we are working closely with our partner bank to finalize all transfers by the end of business today. Once released, funds will process according to the standard timing for bank transfers. \*\*What you might notice:\*\* Some cardholders may have seen a duplicate charge - Good news is that this issue has already been identified and corrected in our systems—duplicates have been refunded automatically. \*\*Next steps:\*\* \* Bank transfers are being finalized today. \* Any duplicate charges are refunded simultaneously as the bank transfer finalization today. \* Expect your funds to arrive following the usual timeframe. We truly appreciate your patience and continue to strive for reliable service. Thank you for your understanding and continued partnership. If you or your customers notice anything unusual, we encourage you to let us know immediately - our team is standing by to help: \[\*\*support@tidypay.com\*\*\](mailto:support@tidypay.com)..</p> <p><small>Aug <var data-var='date'> 22</var>, <var data-var='time'>10:34:55</var> GMT+0</small><br><strong>Identified</strong> - Heti kun viimeistelyt ovat valmiit toimittajan ja pankin välillä, lähtevät käsittelemättömät tilitykset käsittelyyn. Alla vielä päivitys toimijalta: We want to provide you with an update regarding the ongoing settlement delay. Our team is confident that we have identified the root cause of the issue and are currently in the final stages of confirmation with the bank. As soon as this final verification is complete, we will immediately begin processing all outstanding settlement batches. We sincerely apologize for the continued delay and truly appreciate your patience and understanding as we work to bring this to full resolution..</p> <p><small>Sep <var data-var='date'> 5</var>, <var data-var='time'>16:05:20</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 18 Aug 2025 10:00:00 +0000 https://solmio-kassa.instatus.com/incident/cmemqpnhf0001xz9il4f6o5f8 https://solmio-kassa.instatus.com/incident/cmemqpnhf0001xz9il4f6o5f8 Elavon varmennuksissa häiriöitä Type: Incident Duration: 1 hour and 10 minutes Affected Components: App, Verifone SAIO Intercard, Payment Backend, Viva wallet, Worldline, Elavon, Nets Finland Aug 4, 12:20:27 GMT+0 - Postmortem - Tidypayn Euroopan maksuvälityspalvelussa ilmeni 2.–3.8.2025 häiriöitä, jotka aiheuttivat hitautta ja virheitä korttimaksuissa. Häiriö liittyi ulkoisen palvelun istuntohallintaan, joka ylikuormittui käsitellessään suuria korttitietojen tokenointieriä. Tilanne on nyt vakautettu, ja kaikki tapahtumat on käsitelty onnistuneesti. Joillain asiakkailla viikonlopun maksujen tilitys voi viivästyä yhdellä arkipäivällä. Tilapäisesti maksujen käsittelyä ohjataan manuaalisesti. Incident report & RCA Tidypay AS – Incident Report Incident ID TP-2025-07-02-TP-VaultSession Date Saturday 2 – Sunday 3 August 2025 2 August Start to End (CEST) 17:50 to 18:30 CEST, (slow declined transactions) 3 August Start to End (CEST) 13:05 to 15:15 CEST (intermittent slowdowns) Detected by Automated latency alerts & Customer reports Severity High – intermittent payment‑token service degradation Europe region Affected components Tidypay gateway external token vault Customer impact Slower transaction processing; intermittent tokenisation failures for Elavon batch merchants Summary Between 17:50 CEST on 2 August and 15:00 CEST on 3 August 2025, Tidypay’s European gateway experienced elevated latency and intermittent failures when processing large batch tokenisation jobs routed through its new secure‑token vault. About 40 minutes of severe degradation (complete batch processing halt) were observed on Saturday, followed by 70 minutes of recurring slowdowns on Sunday until the underlying issue was identified and mitigated. Timeline (CEST) Time (CEST) Event 17:50 2 August Automated latency alerts and customer reports of transaction slowdowns as an unfinished Elavon batch job was automatically restarted. 18:00 2 August Incident bridge opened; full Tidypay team assembled. 18:30 2 August Batch job manually terminated; traffic restored to normal parameters (root cause still unknown). 13:20 3 August Monitoring detects increased average transaction latency; customer complaints resume. 13:35 3 August Emergency bridge re‑opened; external partners invited. 13:50 3 August External partners joined bridge; live log analysis began. 15:00 3 August Root cause confirmed: Token‑vault session‑exhaustion due to unexpired TLS sessions per request. 15:15 3 August Work‑around applied: large batches split into ≤10 k records each. Root Cause Tidypay’s recently deployed integration towards an external provider introduced a new, dedicated TLS session per tokenisation request. External token provider configuration retained each session in memory for 120 minutes. During high‑volume batch imports (\~45 000 requests in < 2 h) the vault exhausted available memory, ceasing to respond and causing the gateway to queue or fail subsequent requests. The issue recurred whenever a large batch was processed, explaining the Saturday and Sunday degradations. Mitigation & Resolution • Immediate: offending batch terminated and rerun in 30k chunks, preventing further session exhaustion. • External token vault: configuration change requested to reduce idle‑session TTL from 120 minutes to 5 minutes. • Tidypay: gateway hot‑patch to reuse persistent connections and throttle batch concurrency. Corrective & Preventive Actions 1\. Short‑term (August 2025): automate batch‑splitting in gateway; alert on active session count. 2\. Medium‑term (Q3 2025): deploy dedicated in‑datacentre token vault with configurable session limits; evaluate alternate providers. 3\. Long‑term (Q4 2025): implement multi‑region vault fail‑over and load‑shedding on tokenisation path. Customer Communication Affected merchants were notified via email from 18:15 CEST on 2 August and from 13:37 CEST on 3 August with an incident summary and follow up confirmation that all impacted transactions were re‑processed successfully. Some merchants might experience a 1 day delay in the settlement for transactions processed during the weekend. Aug 3, 11:52:00 GMT+0 - Investigating - Alla toimittajan viesti We are currently experiencing some intermittent connectivity issues and want to assure you that our team is fully focused on resolving the situation as quickly as possible. We sincerely apologize for the inconvenience and appreciate your patience and understanding while we work to restore full service. Aug 3, 13:03:00 GMT+0 - Resolved - Odotetaan vielä lopullista kuittausta Tidypaylta, maksut kulkevat normaalisti. Aug 3, 11:53:04 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Transactions getting through now Type: Incident

Duration: 1 hour and 10 minutes

Affected Components: , , , , , ,

<p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>12:20:27</var> GMT+0</small><br><strong>Postmortem</strong> - Tidypayn Euroopan maksuvälityspalvelussa ilmeni 2.–3.8.2025 häiriöitä, jotka aiheuttivat hitautta ja virheitä korttimaksuissa. Häiriö liittyi ulkoisen palvelun istuntohallintaan, joka ylikuormittui käsitellessään suuria korttitietojen tokenointieriä. Tilanne on nyt vakautettu, ja kaikki tapahtumat on käsitelty onnistuneesti. Joillain asiakkailla viikonlopun maksujen tilitys voi viivästyä yhdellä arkipäivällä. Tilapäisesti maksujen käsittelyä ohjataan manuaalisesti. Incident report & RCA Tidypay AS – Incident Report Incident ID TP-2025-07-02-TP-VaultSession Date Saturday 2 – Sunday 3 August 2025 2 August Start to End (CEST) 17:50 to 18:30 CEST, (slow declined transactions) 3 August Start to End (CEST) 13:05 to 15:15 CEST (intermittent slowdowns) Detected by Automated latency alerts & Customer reports Severity High – intermittent payment‑token service degradation Europe region Affected components Tidypay gateway external token vault Customer impact Slower transaction processing; intermittent tokenisation failures for Elavon batch merchants Summary Between 17:50 CEST on 2 August and 15:00 CEST on 3 August 2025, Tidypay’s European gateway experienced elevated latency and intermittent failures when processing large batch tokenisation jobs routed through its new secure‑token vault. About 40 minutes of severe degradation (complete batch processing halt) were observed on Saturday, followed by 70 minutes of recurring slowdowns on Sunday until the underlying issue was identified and mitigated. Timeline (CEST) Time (CEST) Event 17:50 2 August Automated latency alerts and customer reports of transaction slowdowns as an unfinished Elavon batch job was automatically restarted. 18:00 2 August Incident bridge opened; full Tidypay team assembled. 18:30 2 August Batch job manually terminated; traffic restored to normal parameters (root cause still unknown). 13:20 3 August Monitoring detects increased average transaction latency; customer complaints resume. 13:35 3 August Emergency bridge re‑opened; external partners invited. 13:50 3 August External partners joined bridge; live log analysis began. 15:00 3 August Root cause confirmed: Token‑vault session‑exhaustion due to unexpired TLS sessions per request. 15:15 3 August Work‑around applied: large batches split into ≤10 k records each. Root Cause Tidypay’s recently deployed integration towards an external provider introduced a new, dedicated TLS session per tokenisation request. External token provider configuration retained each session in memory for 120 minutes. During high‑volume batch imports (\~45 000 requests in < 2 h) the vault exhausted available memory, ceasing to respond and causing the gateway to queue or fail subsequent requests. The issue recurred whenever a large batch was processed, explaining the Saturday and Sunday degradations. Mitigation & Resolution • Immediate: offending batch terminated and rerun in 30k chunks, preventing further session exhaustion. • External token vault: configuration change requested to reduce idle‑session TTL from 120 minutes to 5 minutes. • Tidypay: gateway hot‑patch to reuse persistent connections and throttle batch concurrency. Corrective & Preventive Actions 1\. Short‑term (August 2025): automate batch‑splitting in gateway; alert on active session count. 2\. Medium‑term (Q3 2025): deploy dedicated in‑datacentre token vault with configurable session limits; evaluate alternate providers. 3\. Long‑term (Q4 2025): implement multi‑region vault fail‑over and load‑shedding on tokenisation path. Customer Communication Affected merchants were notified via email from 18:15 CEST on 2 August and from 13:37 CEST on 3 August with an incident summary and follow up confirmation that all impacted transactions were re‑processed successfully. Some merchants might experience a 1 day delay in the settlement for transactions processed during the weekend..</p> <p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>11:52:00</var> GMT+0</small><br><strong>Investigating</strong> - Alla toimittajan viesti We are currently experiencing some intermittent connectivity issues and want to assure you that our team is fully focused on resolving the situation as quickly as possible. We sincerely apologize for the inconvenience and appreciate your patience and understanding while we work to restore full service..</p> <p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>13:03:00</var> GMT+0</small><br><strong>Resolved</strong> - Odotetaan vielä lopullista kuittausta Tidypaylta, maksut kulkevat normaalisti..</p> <p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>11:53:04</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result. Transactions getting through now.</p> ]]> Sun, 3 Aug 2025 11:52:00 +0000 https://solmio-kassa.instatus.com/incident/cmdvmfv1u01tcj2t2p7ka318u https://solmio-kassa.instatus.com/incident/cmdvmfv1u01tcj2t2p7ka318u Elavon varmennuksissa häiriöitä Type: Incident Duration: 46 minutes Affected Components: Elavon Aug 2, 18:15:00 GMT+0 - Resolved - This incident has been resolved. Aug 2, 17:29:00 GMT+0 - Investigating - We are currently investigating this incident. Alla toimittajan viesti We are currently experiencing some intermittent connectivity issues and want to assure you that our team is fully focused on resolving the situation as quickly as possible. We sincerely apologize for the inconvenience and appreciate your patience and understanding while we work to restore full service. Type: Incident

Duration: 46 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 2</var>, <var data-var='time'>18:15:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Aug <var data-var='date'> 2</var>, <var data-var='time'>17:29:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. Alla toimittajan viesti We are currently experiencing some intermittent connectivity issues and want to assure you that our team is fully focused on resolving the situation as quickly as possible. We sincerely apologize for the inconvenience and appreciate your patience and understanding while we work to restore full service..</p> ]]> Sat, 2 Aug 2025 17:29:00 +0000 https://solmio-kassa.instatus.com/incident/cmdwybo0o007waku2tvu5omqd https://solmio-kassa.instatus.com/incident/cmdwybo0o007waku2tvu5omqd Nets: Acquiring connectivity Type: Incident Duration: 2 hours and 8 minutes Affected Components: Nets Finland May 7, 12:37:56 GMT+0 - Resolved - This incident has been resolved. May 7, 10:30:17 GMT+0 - Investigating - New incident: Investigating Since 11:26 local time in Finland, connectivity issue between PSP and acquiring system affecting payments for Finnish merchants. May 7, 10:32:00 GMT+0 - Monitoring - Returned to normal since 12:38 Finland local time. Monitoring. Type: Incident

Duration: 2 hours and 8 minutes

Affected Components:

<p><small>May <var data-var='date'> 7</var>, <var data-var='time'>12:37:56</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>May <var data-var='date'> 7</var>, <var data-var='time'>10:30:17</var> GMT+0</small><br><strong>Investigating</strong> - New incident: Investigating Since 11:26 local time in Finland, connectivity issue between PSP and acquiring system affecting payments for Finnish merchants..</p> <p><small>May <var data-var='date'> 7</var>, <var data-var='time'>10:32:00</var> GMT+0</small><br><strong>Monitoring</strong> - Returned to normal since 12:38 Finland local time. Monitoring..</p> ]]> Wed, 7 May 2025 10:30:17 +0000 https://solmio-kassa.instatus.com/incident/cmadsrqsq002aj4quf7ho0bbl https://solmio-kassa.instatus.com/incident/cmadsrqsq002aj4quf7ho0bbl Viva.com payments failing Type: Incident Duration: 12 days, 22 hours and 31 minutes Affected Components: Viva wallet Mar 24, 09:49:29 GMT+0 - Investigating - We are currently investigating this incident. possible fix might be restarting device/router network. Waiting more information from Viva Clearing DNS cache might fix the probrelm, you can try: Open Chrome. In the URL bar, type in chrome://net-internals/#dns: In the left pane, select DNS. In the right pane, tap the Clear host cache button. Mahdollinen korjaus laitteen/reitittimen uudelleenkäynnistys tai DNS-asetusten nollaus. Odotamme lisätietoa Vivalta Mar 24, 11:20:46 GMT+0 - Investigating - Works now with most of the devices. If problems still persist, please restart router and payment terminal Mar 24, 15:00:00 GMT+0 - Resolved - Got info from Viva, if the terminal still failes to connect try this fix: On payment terminal -> Go to **Settings** \> **Network & Internet** \> **Private DNS** * Select **Private DNS provider hostname** * Enter a provider (e.g.): * [dns.google](http://dns.google) for Google DNS * [one.one.one.one](http://one.one.one.one) for Cloudflare DNS * Tap **Save** Type: Incident

Duration: 12 days, 22 hours and 31 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>09:49:29</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. possible fix might be restarting device/router network. Waiting more information from Viva Clearing DNS cache might fix the probrelm, you can try: Open Chrome. In the URL bar, type in chrome://net-internals/#dns: In the left pane, select DNS. In the right pane, tap the Clear host cache button. Mahdollinen korjaus laitteen/reitittimen uudelleenkäynnistys tai DNS-asetusten nollaus. Odotamme lisätietoa Vivalta.</p> <p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>11:20:46</var> GMT+0</small><br><strong>Investigating</strong> - Works now with most of the devices. If problems still persist, please restart router and payment terminal.</p> <p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br><strong>Resolved</strong> - Got info from Viva, if the terminal still failes to connect try this fix: On payment terminal -> Go to **Settings** \> **Network & Internet** \> **Private DNS** * Select **Private DNS provider hostname** * Enter a provider (e.g.): * [dns.google](http://dns.google) for Google DNS * [one.one.one.one](http://one.one.one.one) for Cloudflare DNS * Tap **Save**.</p> ]]> Mon, 24 Mar 2025 09:49:29 +0000 https://solmio-kassa.instatus.com/incident/cm8mvxsxv001jjjf2wllwuskd https://solmio-kassa.instatus.com/incident/cm8mvxsxv001jjjf2wllwuskd Nets Vega Mobile network connection problems with SIM-card Type: Incident Duration: 3 hours and 2 minutes Affected Components: Nets Finland Jan 31, 10:27:01 GMT+0 - Investigating - Until the issue is resolved, Wi-Fi connection is possible to use. Jan 31, 13:29:18 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 3 hours and 2 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 31</var>, <var data-var='time'>10:27:01</var> GMT+0</small><br><strong>Investigating</strong> - Until the issue is resolved, Wi-Fi connection is possible to use. .</p> <p><small>Jan <var data-var='date'> 31</var>, <var data-var='time'>13:29:18</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. .</p> ]]> Fri, 31 Jan 2025 10:27:01 +0000 https://solmio-kassa.instatus.com/incident/cm6kmdrix003914nf7e1knvqh https://solmio-kassa.instatus.com/incident/cm6kmdrix003914nf7e1knvqh Nets Finland settlements are delayed Type: Incident Duration: 5 hours and 11 minutes Affected Components: Nets Finland Jan 14, 07:41:15 GMT+0 - Investigating - Monday Jan 13th settlements for Nets Finland failed due to a network configuration issue. We are working on it. Jan 14, 10:46:50 GMT+0 - Monitoring - 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. Jan 14, 12:52:19 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 5 hours and 11 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 14</var>, <var data-var='time'>07:41:15</var> GMT+0</small><br><strong>Investigating</strong> - Monday Jan 13th settlements for Nets Finland failed due to a network configuration issue. We are working on it..</p> <p><small>Jan <var data-var='date'> 14</var>, <var data-var='time'>10:46:50</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>Jan <var data-var='date'> 14</var>, <var data-var='time'>12:52:19</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 14 Jan 2025 07:41:15 +0000 https://solmio-kassa.instatus.com/incident/cm5w5z4bp003zhwse9vdokfwg https://solmio-kassa.instatus.com/incident/cm5w5z4bp003zhwse9vdokfwg Nets Authorization connection problems Type: Incident Duration: 55 minutes Affected Components: Nets Finland Jan 10, 08:17:39 GMT+0 - Resolved - This incident has been resolved. Jan 10, 07:23:02 GMT+0 - Investigating - Nets is currently investigating this incident. Jan 10, 07:29:26 GMT+0 - Identified - Incident status: Identified There were network connectivity problems at Nets Finland acquirer side. The connections were completely down between 8:44 (UTC+2) and 9:12. Type: Incident

Duration: 55 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 10</var>, <var data-var='time'>08:17:39</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jan <var data-var='date'> 10</var>, <var data-var='time'>07:23:02</var> GMT+0</small><br><strong>Investigating</strong> - Nets is currently investigating this incident..</p> <p><small>Jan <var data-var='date'> 10</var>, <var data-var='time'>07:29:26</var> GMT+0</small><br><strong>Identified</strong> - Incident status: Identified There were network connectivity problems at Nets Finland acquirer side. The connections were completely down between 8:44 (UTC+2) and 9:12..</p> ]]> Fri, 10 Jan 2025 07:23:02 +0000 https://solmio-kassa.instatus.com/incident/cm5qfka1y003aci3lfvhcp1h1 https://solmio-kassa.instatus.com/incident/cm5qfka1y003aci3lfvhcp1h1 Acquirer Connections - Nets Finland Type: Incident Duration: 1 hour and 30 minutes Affected Components: Nets Finland Oct 10, 05:49:14 GMT+0 - Investigating - Nets Finland acquiring connection problems Nets is currently investigating this issue. Oct 10, 07:11:38 GMT+0 - Monitoring - ## Nets Finland acquiring connection problems Incident status: Monitoring A fix has been implemented and we are monitoring the results. Oct 10, 07:19:32 GMT+0 - Resolved - Issue is fixed and authorizations have returned to normal since 10:00 Finland time Type: Incident

Duration: 1 hour and 30 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>05:49:14</var> GMT+0</small><br><strong>Investigating</strong> - Nets Finland acquiring connection problems Nets is currently investigating this issue..</p> <p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>07:11:38</var> GMT+0</small><br><strong>Monitoring</strong> - ## Nets Finland acquiring connection problems Incident status: Monitoring A fix has been implemented and we are monitoring the results..</p> <p><small>Oct <var data-var='date'> 10</var>, <var data-var='time'>07:19:32</var> GMT+0</small><br><strong>Resolved</strong> - Issue is fixed and authorizations have returned to normal since 10:00 Finland time.</p> ]]> Thu, 10 Oct 2024 05:49:14 +0000 https://solmio-kassa.instatus.com/incident/cm22vpamj00017mxzajl6fey9 https://solmio-kassa.instatus.com/incident/cm22vpamj00017mxzajl6fey9 Elavon cardpayment issue Type: Incident Duration: 6 minutes Affected Components: Payment Backend, Elavon Oct 7, 09:00:31 GMT+0 - Investigating - Elavon has confirmed that they are facing problems right now. Card payments doesn't go through and will give error code E02\. Elavon is currently investigating this incident and this will be fixed as soon as possible. Oct 7, 09:06:55 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 6 minutes

Affected Components: ,

<p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>09:00:31</var> GMT+0</small><br><strong>Investigating</strong> - Elavon has confirmed that they are facing problems right now. Card payments doesn't go through and will give error code E02\. Elavon is currently investigating this incident and this will be fixed as soon as possible..</p> <p><small>Oct <var data-var='date'> 7</var>, <var data-var='time'>09:06:55</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 7 Oct 2024 09:00:31 +0000 https://solmio-kassa.instatus.com/incident/cm1ys7rj20005p6093pwap323 https://solmio-kassa.instatus.com/incident/cm1ys7rj20005p6093pwap323 Authorization failures are on the rise Type: Incident Affected Components: Nets Finland Oct 6, 10:59:40 GMT+0 - Resolved - We are monitoring more than business as usual amount of failing purchase transactions. Approximately 15% of the purchases are failing while most succeed. We are investigating. Type: Incident

Affected Components:

<p><small>Oct <var data-var='date'> 6</var>, <var data-var='time'>10:59:40</var> GMT+0</small><br><strong>Resolved</strong> - We are monitoring more than business as usual amount of failing purchase transactions. Approximately 15% of the purchases are failing while most succeed. We are investigating..</p> ]]> Sun, 6 Oct 2024 10:59:40 +0000 https://solmio-kassa.instatus.com/incident/cm1xh134y000413nysy6jg2b7 https://solmio-kassa.instatus.com/incident/cm1xh134y000413nysy6jg2b7 Authorizations failing due to no connection to issuer at acquirer side Type: Incident Duration: 33 minutes Affected Components: Nets Finland Sep 4, 10:21:28 GMT+0 - Investigating - We are currently investigating this incident. More information <https://npaystatus.nexigroup.com/incidents/jv2xf8fx6f81> Sep 4, 10:33:30 GMT+0 - Monitoring - Transactions are no longer failing. There were problems during 13:03 to 13:22 EEST (Finnish time). We're monitoring for further problems and are still investigating the impact. We'll update once we have the details what was the impact. Sep 4, 10:54:21 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 33 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>10:21:28</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. More information <https://npaystatus.nexigroup.com/incidents/jv2xf8fx6f81>.</p> <p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>10:33:30</var> GMT+0</small><br><strong>Monitoring</strong> - Transactions are no longer failing. There were problems during 13:03 to 13:22 EEST (Finnish time). We're monitoring for further problems and are still investigating the impact. We'll update once we have the details what was the impact..</p> <p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>10:54:21</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 4 Sep 2024 10:21:28 +0000 https://solmio-kassa.instatus.com/incident/cm0npkok400107hw6jdzq57eg https://solmio-kassa.instatus.com/incident/cm0npkok400107hw6jdzq57eg Varmennusvirheitä Nordealla, vaikuttaa Netsin maksunvälitykseen Type: Incident Duration: 39 minutes Affected Components: Nets Finland May 21, 12:00:29 GMT+0 - Investigating - **Investigating** \- We are experiencing an elevated level of authorization errors. There is an ongoing upstream incident affecting Nordea authorizations that we are tracking. May 21, 12:39:37 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 39 minutes

Affected Components:

<p><small>May <var data-var='date'> 21</var>, <var data-var='time'>12:00:29</var> GMT+0</small><br><strong>Investigating</strong> - **Investigating** \- We are experiencing an elevated level of authorization errors. There is an ongoing upstream incident affecting Nordea authorizations that we are tracking..</p> <p><small>May <var data-var='date'> 21</var>, <var data-var='time'>12:39:37</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 21 May 2024 12:00:29 +0000 https://solmio-kassa.instatus.com/incident/clwgcfqc339799bcoqks8rdtf1 https://solmio-kassa.instatus.com/incident/clwgcfqc339799bcoqks8rdtf1 Network connection issues with Nets/Vega terminals Type: Incident Duration: 3 hours and 6 minutes Affected Components: Nets Finland Jan 14, 10:56:04 GMT+0 - Identified - Identified - Fix has been attempted and looks initially positive, but continuing investigation Link to nets incident https://npaystatus.nexigroup.com/incidents/cxrbbzvpwymg Jan 14, 11:35:00 GMT+0 - Monitoring - Monitoring - Fix seems to have worked, but we'll attempt to see if there are still other problems. More info to follow shortly. Jan 14, 13:10:04 GMT+0 - Resolved - This incident has been resolved. Jan 14, 10:03:54 GMT+0 - Investigating - We are currently investigating this incident. Type: Incident

Duration: 3 hours and 6 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 14</var>, <var data-var='time'>10:56:04</var> GMT+0</small><br><strong>Identified</strong> - Identified - Fix has been attempted and looks initially positive, but continuing investigation Link to nets incident https://npaystatus.nexigroup.com/incidents/cxrbbzvpwymg.</p> <p><small>Jan <var data-var='date'> 14</var>, <var data-var='time'>11:35:00</var> GMT+0</small><br><strong>Monitoring</strong> - Monitoring - Fix seems to have worked, but we'll attempt to see if there are still other problems. More info to follow shortly..</p> <p><small>Jan <var data-var='date'> 14</var>, <var data-var='time'>13:10:04</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jan <var data-var='date'> 14</var>, <var data-var='time'>10:03:54</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> ]]> Sun, 14 Jan 2024 10:03:54 +0000 https://solmio-kassa.instatus.com/incident/clrdbwsy63209bcoh3fkbrubv https://solmio-kassa.instatus.com/incident/clrdbwsy63209bcoh3fkbrubv Network connection issues with Vega Mobile payment terminals Type: Incident Duration: 2 days, 19 hours and 19 minutes Affected Components: Worldline Oct 20, 11:32:43 GMT+0 - Investigating - This issue effects several devices at the moment but not all of them. We are currently investigating this incident with Poplapay. Oct 20, 11:50:10 GMT+0 - Identified - Issue has been found and it is in Telia and Telenor connections. Telia and Telenor are continuing to work on a fix for this incident. Oct 23, 06:51:15 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 days, 19 hours and 19 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>11:32:43</var> GMT+0</small><br><strong>Investigating</strong> - This issue effects several devices at the moment but not all of them. We are currently investigating this incident with Poplapay..</p> <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>11:50:10</var> GMT+0</small><br><strong>Identified</strong> - Issue has been found and it is in Telia and Telenor connections. Telia and Telenor are continuing to work on a fix for this incident..</p> <p><small>Oct <var data-var='date'> 23</var>, <var data-var='time'>06:51:15</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 20 Oct 2023 11:32:43 +0000 https://solmio-kassa.instatus.com/incident/clnyj7qlo172775c7ojvjwzasv9 https://solmio-kassa.instatus.com/incident/clnyj7qlo172775c7ojvjwzasv9 Verifone CM5 refusing card payments Type: Incident Duration: 2 days, 22 hours and 38 minutes Affected Components: Verifone SAIO Intercard Sep 29, 09:23:58 GMT+0 - Investigating - Verifone is currently investigating this incident. Gives error t003 Sep 29, 12:21:15 GMT+0 - Investigating - Verifone is still investigating the issue. Oct 2, 08:01:40 GMT+0 - Resolved - This incident has been resolved on 30.9 at 8pm. Type: Incident

Duration: 2 days, 22 hours and 38 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>09:23:58</var> GMT+0</small><br><strong>Investigating</strong> - Verifone is currently investigating this incident. Gives error t003 .</p> <p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>12:21:15</var> GMT+0</small><br><strong>Investigating</strong> - Verifone is still investigating the issue. .</p> <p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>08:01:40</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved on 30.9 at 8pm..</p> ]]> Fri, 29 Sep 2023 09:23:58 +0000 https://solmio-kassa.instatus.com/incident/cln4edado245060bhon4qay7q7a https://solmio-kassa.instatus.com/incident/cln4edado245060bhon4qay7q7a Worldline settlements delayed Type: Incident Duration: 2 days, 3 hours and 21 minutes Affected Components: Worldline Sep 18, 09:19:00 GMT+0 - Investigating - Investigating - This affects every merchant that is routed via TietoEvry. We are currently investigating the issue. Sep 20, 12:40:07 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 days, 3 hours and 21 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 18</var>, <var data-var='time'>09:19:00</var> GMT+0</small><br><strong>Investigating</strong> - Investigating - This affects every merchant that is routed via TietoEvry. We are currently investigating the issue..</p> <p><small>Sep <var data-var='date'> 20</var>, <var data-var='time'>12:40:07</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 18 Sep 2023 09:19:00 +0000 https://solmio-kassa.instatus.com/incident/clmrqb99s410891bqobsaq8eplk https://solmio-kassa.instatus.com/incident/clmrqb99s410891bqobsaq8eplk