pinvandaag - Notice history

All systems operational

Notice history

Aug 2026

Jul 2026

WIPAY DISTURBANCE
  • Resolved
    UTC
    Resolved

    Uit ons onderzoek is gebleken dat de WIPay-applicatie tijdens een aantal piekmomenten met een hoog transactievolume moeilijkheden ondervond bij het beheren van bestaande verbindingen, waardoor inkomende berichten niet altijd tijdig konden worden verwerkt. De impact hiervan werd vergroot door uitzonderlijk hoge activiteit van een beperkt aantal terminals.

     

    Onze technische teams hebben een eerste workaround geïmplementeerd om specifieke activiteitspatronen aan te pakken, gevolgd door een bredere oplossing om de robuustheid van het platform bij onverwacht hoge berichtvolumes te vergroten. Daarnaast hebben we onze monitoring- en waarschuwingsmechanismen verfijnd om snellere detectie en interventie te faciliteren mocht dergelijk gedrag zich opnieuw voordoen.

     

    Onze teams blijven onverminderd werken aan een permanente oplossing. We blijven de omgeving nauwlettend monitoren en zullen u, waar nodig, verder informeren.

     

    Wij onderkennen het belang van een stabiele dienstverlening voor uw bedrijf en betreuren de eventuele hinder die u zou kunnen ondervinden. We danken u voor uw geduld en het vertrouwen dat u in ons stelt.

  • Update
    UTC
    Update

    Affected system: WIPay host (ECR protocol)


    Status: We keep monitoring the service and will act directly when disruptions are occurring. No need to report this.

    Next step: An intervention is scheduled for tomorrow morning July 24, 2026, at 05:30 AM. You may experience a brief service interruption during this time.

  • Monitoring
    UTC
    Monitoring

    Affected system: WIPay host (ECR protocol)


    Status: No errors to report after 12:00 AM till now. Steady for more than 1 hour. We keep monitoring and will act directly as disruptions are recurring. No need to report this.

    Extra information: A possible root cause has been found. Tests are carried out on the WIPay acceptance environment. When OK, the fix will be rolled out (as soon as possible) on our production environment. This may be done during merchant opening hours. Time and duration of the roll out on production will be communicated duly.   

     

    Next update notification: Thursday, 23 July, 15:30 PM (or sooner when needed)

  • Update
    UTC
    Update

    Affected system: WIPay host (ECR protocol)

     

    Impact: Recurring interruptions of Callback service. Still partly persisting. Transactions are still possible, but feedback with transaction result may be correctly received, delayed, or not received at all. This differs per terminal. When the system is 100% up, the not received transaction results can be requested via a status request (accompanied by a SSAI, reference or transaction ID).


    Extra information: The rollback last night was successful. Apparently, this action failed to provide the expected solution, despite positive initial indicators. Analyses are ongoing to identify a structural fix.

     

    Next update notification: Thursday, 23 July, 14:00 PM

  • Identified
    UTC
    Identified

    Affected system: WIPay host (ECR protocol)

     

    Impact: Recurring interruptions of Callback service.

    Planned action: ROLLBACK to the previous WIPay version, as a new WIPay version was installed on Sunday, 19 July.


    When: Services will be down for 30 minutes on Thursday, 23 July, starting at 05:30 AM.

    Extra information: In the meantime, our engineers are continuously monitoring the system. Should any disruptions occur, services will be restarted as soon as possible. Please note that short interruptions may be noticeable from now until the rollback is complete. No need to report further issues between now and tomorrow 06:00 AM.

     

    Next update notification: Thursday, 23 July.

  • Monitoring
    UTC
    Monitoring

    Affected system: WIPay host (ECR protocol)

     

    Impact: Partially down. Transactions are possible, Callbacks are not sent to ECR/POS server.

     

    Resolve time: to be determined

     

    Next update notification: within 2 hours (or sooner when more additional information is available and/or the situation has changed)

Jun 2026

No notices reported this month

Jun 2026 to Aug 2026

Next