Reepay incident

Double captures for transactions processed by Nets to Elavon

Minor Resolved View vendor source →

Reepay experienced a minor incident on October 31, 2024 affecting Elavon (Nets), lasting 22h 53m. The incident has been resolved; the full update timeline is below.

Started
Oct 31, 2024, 09:25 AM UTC
Resolved
Nov 01, 2024, 08:18 AM UTC
Duration
22h 53m
Detected by Pingoru
Oct 31, 2024, 09:25 AM UTC

Affected components

Elavon (Nets)

Update timeline

  1. investigating Oct 31, 2024, 09:25 AM UTC

    We have been made aware that old successful transactions processed by Nets to Elavon are suddenly being deducted from customers again. The oldest transaction we have been made aware of was originally captured in May. We are in contact with Nets processing regarding this issue. We are awaiting a response from Nets on how they will rectify the situation. We urge to not refund the original transactions at this point as we expect Nets to centrally issue refunds of the recent errornous transactions.

  2. investigating Oct 31, 2024, 02:52 PM UTC

    Nets and Elavon are working on a resolution for this issue. We will return as soon as we have any update from them.

  3. resolved Nov 01, 2024, 08:18 AM UTC

    We have received information from Elavon and Nets that in an attempt to rectify previously failed settlement transactions between Nets and Elavon, transactions were erroneously included that were already successfully settled. Elavon informs that the errornous settlements will be refunded to the customers next week. No action is needed from you as a merchant. Elavon can be reached on email [email protected] for further information.