PayPlug incident
Incident plateforme de paiement / Payment platform incident / Incidente della piattaforma di pagamento
PayPlug experienced a critical incident on June 7, 2026 affecting Paiements e-commerce and Paiements en magasin Nexo and 1 more component, lasting 44m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 07, 2026, 04:43 AM UTC
FR Nous avons identifié des difficultés sur les paiements en ligne et en magasins. L'incident est en cours d'analyse. EN We have identified issues affecting online and in-store payments. An investigation is in progress. IT Abbiamo identificato delle difficoltà nei pagamenti online e nei punti vendita. L'incidente è in fase di analisi.
- investigating Jun 07, 2026, 05:05 AM UTC
FR Nous avons identifié des difficultés sur la plateforme de paiement. Après analyse, il apparaît que l’incident est externe à notre plateforme. Nous vous tiendrons informés de l’évolution dès que de nouvelles informations seront disponibles. EN We have identified issues on the payment platform. Following analysis, it appears that the incident is external to our platform. We will keep you informed of any developments as soon as further information becomes available. IT Abbiamo identificato delle difficoltà sulla piattaforma di pagamento. Dopo un’analisi, risulta che l’incidente è esterno alla nostra piattaforma. Vi terremo aggiornati sugli sviluppi non appena saranno disponibili nuove informazioni.
- resolved Jun 07, 2026, 05:28 AM UTC
TSR-XXXX - Début / Start : 07/06/2026 06:15:00 CEST - Fin / End : 07/06/2026 06:58:00 CEST - Catégorie / Category : Production/ Processing - Responsabilité / Responsibility : Externe - Priorité / Priority : P1 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.
- postmortem Jul 24, 2026, 09:23 AM UTC
# _English version below_ # Post Mortem **Service concerné** Paiements en magasin, e-commerce et 3DS. **Impact client** Impossibilité d’effectuer des paiements pour les porteurs. **Synthèse de l’incident** * **7 juin 6h02 :** remontée d’alerte. * **7 juin 6h15 : début de l’incident.** * **7 juin 6h27 :** création d’une cellule de crise dédiée. Début des investigations. * **7 juin 6h28 : identification d’un serveur défectueux chez un prestataire externe.** * **7 juin 6h29 :** contact du prestataire externe. * **7 juin 6h54 :** confirmation du prestataire externe que l’incident est bien chez eux. * **7 juin 6h57 : fin de l’incident.** **Root cause** Incident externe chez un prestataire. ==============ENGLISH VERSION============== # Post Mortem **Payment services affected by the incident** In-store payments, e-commerce payments and 3DS. **Client impact** Cardholders were unable to make payments. **Incident Overview** * **7 June, 6:02 am:** alert raised. * **7 June 6:15am: incident began.** * **7 June 6:27am:** a dedicated crisis management team was established. Investigations commenced. * **7 June 6:28am: a faulty server was identified at an external service provider.** * **7 June 6:29am:** the external service provider was contacted. * **7 June 6:54am:** the external service provider confirmed that the incident originated on their side. * **7 June 6:57am: Incident resolved.** **Root cause** External incident at a service provider.