PayPlug Outage History

PayPlug is up right now

PayPlug had 21 outages in the last 2 years totaling 1160h 7m of downtime — averaging 0.9 incidents per month.

There were 21 PayPlug outages since September 12, 2024 totaling 1160h 7m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.payplug.com

Minor August 17, 2026

Incident Portail / Portail unavailable / Portail Indisponibile

Detected by Pingoru
Aug 17, 2026, 08:02 AM UTC
Resolved
Aug 17, 2026, 08:38 AM UTC
Duration
36m
Affected: Paiements e-commerceBackoffice Payplug
Timeline · 3 updates
  1. investigating Aug 17, 2026, 08:02 AM UTC

    FR Nous avons identifié un problème d'affichage des transactions sur notre Portail. Aucun impact processing n'est constaté à l'exception de la fonctionnalité getTransaction. L'incident est en cours d'analyse. EN We have identified an issue affecting the display of transactions in our Portal. No impact on transaction processing has been observed, with the exception of the getTransaction functionality. The incident is currently under investigation. IT Abbiamo identificato un problema di visualizzazione delle transazioni sul nostro Portale. Non si riscontra alcun impatto sul processing, ad eccezione della funzionalità getTransaction. L'incidente è attualmente in fase di analisi.

  2. monitoring Aug 17, 2026, 08:15 AM UTC

    TSR-3623 - Début / Start / Inizio : 17/08/2026 9h50 CEST. - Fin / End /fine : 17/08/2026 10h11 CEST. - Catégorie / Category / Categoria: Production Portail. - Responsabilité / Responsibility / Responsabilità : Payplug - Priorité / Priority / Priorità: P2. FR Les actions correctives ont été réalisées. Le service est revenu à la normale. EN The corrective actions have been completed. The service has returned to normal. IT Le azioni correttive sono state completate. Il servizio è tornato alla normalità.

  3. resolved Aug 17, 2026, 08:38 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 3, 2025

INCIDENT REVERSEMENT | Délai reversement 3 décembre / 3rd of December settlement delay

Detected by Pingoru
Dec 03, 2025, 10:36 AM UTC
Resolved
Dec 05, 2025, 11:20 AM UTC
Duration
2d
Affected: Reversement / Settlement
Timeline · 4 updates
  1. investigating Dec 03, 2025, 10:36 AM UTC

    FR Les reversements du 2 décembre initialement prévus aujourd’hui seront effectués demain. Aucune action n’est requise de votre part, et les fonds seront disponibles sur vos comptes comme habituellement. Les détails des virements correspondants seront mis à disposition aujourd'hui. EN The payouts for 2 December, originally scheduled for today, will be processed tomorrow. No action is required on your part, and the funds will be available in your accounts as usual. The details of the corresponding transfers will be made available today.

  2. monitoring Dec 03, 2025, 10:44 AM UTC

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

  3. monitoring Dec 04, 2025, 10:39 AM UTC

    FR Les reversements du 2 décembre ont bien été effectués. En revanche, les reversements du 3 décembre initialement prévus aujourd’hui seront effectués demain. Aucune action n’est requise de votre part, et les fonds seront disponibles sur vos comptes comme habituellement. Les détails des virements correspondants seront mis à disposition aujourd'hui. EN The payouts for 2 December have been successfully processed. However, the payouts for 3 December, which were originally scheduled for today, will be processed tomorrow. No action is required on your part, and the funds will be available in your accounts as usual. The details of the corresponding transfers will be made available today.

  4. resolved Dec 05, 2025, 11:20 AM UTC

    FR Nous vous confirmons le reversement des transactions 3 décembre. Nous somes à jour sur les reversements. EN We confirm the payouts of the transactions from 3 December. We are up to date with the payouts. IT Vi confermiamo il rimborso delle transazioni del 3 dicembre. Siamo aggiornati sui rimborsi.

Read the full incident report →

Notice November 15, 2024

Prestashop 4.14 – Problème de paiement / Problema di pagamento / Payment issue

Detected by Pingoru
Nov 15, 2024, 02:15 PM UTC
Resolved
Nov 15, 2024, 02:15 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Nov 15, 2024, 02:15 PM UTC

    FR Nous invitons nos marchands utilisant notre module Prestashop 4.14 à le mettre à jour vers la version 4.14.2. Celle-ci corrige des dysfonctionnements impactant le bon fonctionnement des paiements. IT Invitiamo i nostri commercianti che utilizzano il nostro modulo Prestashop 4.14 ad aggiornarlo alla versione 4.14.2. Quest'ultima corregge i malfunzionamenti che incidono sul buon funzionamento dei pagamenti. EN We invite our merchants using our Prestashop 4.14 module to upgrade to version 4.14.2. This corrects malfunctions impacting the payments.

Read the full incident report →

Major September 12, 2024

INCIDENT PROCESSING | Perturbations terminaux de paiement / Payment terminals disruptions

Detected by Pingoru
Sep 12, 2024, 09:57 AM UTC
Resolved
Sep 12, 2024, 10:26 AM UTC
Duration
29m
Timeline · 3 updates
  1. investigating Sep 12, 2024, 09:57 AM UTC

    FR Nous avons identifié des difficultés sur certains terminaux de paiement. Cet incident concerne une route d'acquisition spécifique et vous n'êtes pas tous concernés. L'incident est en cours d'analyse. EN We have identified ongoing difficulties on some payment terminals. This incident affects one acquisition route, not all of you are affected. An investigation is in progress.

  2. monitoring Sep 12, 2024, 10:13 AM UTC

    TSR-436 - Début / Start : 12/09/2024 - Fin / End : 12/09/2024 12.07AM CEST - Catégorie / Category : Production - Terminaux de paiement / Payment terminals - Responsabilité / Responsibility : Payplug - Priorité / Priority : P2 FR L'incident est maintenant résolu et le service est rétabli. Nous continuons à surveiller la reprise du service EN Incident is now resolved and service restored. Service recovery is still under monitoring

  3. resolved Sep 12, 2024, 10:26 AM UTC

    This incident has been resolved.

Read the full incident report →