Pagero incident

Pagero Online - Duplicate reconciliation files in our E-banking service

Notice Resolved View vendor source →

Pagero experienced a notice incident on October 20, 2025 affecting Pagero Online, lasting 3h 21m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 09:56 AM UTC
Resolved
Oct 20, 2025, 01:18 PM UTC
Duration
3h 21m
Detected by Pingoru
Oct 20, 2025, 09:56 AM UTC

Affected components

Pagero Online

Update timeline

  1. investigating Oct 20, 2025, 09:56 AM UTC

    We’re currently investigating reports of duplicate reconciliation files received by our customers for our E-banking service in Pagero Online. We are working on identifying the cause and impact on customers. We apologize for any inconvenience and will post new updates as soon as we learn anything more. If you have any questions, please contact our Support team

  2. identified Oct 20, 2025, 11:12 AM UTC

    We have identified that the duplicate reconciliation files is limited to files from SEB and transactions with execution date 2025-10-17. The duplicates will either show up as if the same transaction would have been executed several times when checking the reconciliation file(s) or as separate identical reconciliation file(s). Please note that it is only the reporting that is affected, the actual transactions has NOT been executed incorrectly (multiple times). We are still investigating the cause of this issue. If you have any questions, please contact our Support team

  3. resolved Oct 20, 2025, 01:18 PM UTC

    We have identified the root cause of the duplicate reconciliation files issue. The problem occurred when our services were restarted following the infrastructure incident reported previously in https://status.pagero.com/incidents/fndbwr5xcn5c. During the restart, the same files were processed multiple times before the system had fully synchronized, resulting in duplicate reconciliation files appearing in the service. The duplicates will either show up as if the same transaction would have been executed several times when checking the reconciliation file(s) or as separate identical reconciliation file(s). Please note that it is only the reporting that is affected - the actual transactions has NOT been executed incorrectly (multiple times). If you have any questions, please contact our Support team