Mercury: Duplicated incoming ACH transactions
Affected components: Money Movement
Timeline of updates
- investigating
We're investigating reports of duplicated incoming ACH transactions that may be impacting some customers. We are aware of this issue and our team is actively looking into it.
We'll share an update as soon as we have more information. No action is needed from you at this time.
- identified
We've identified the cause of the duplicate transaction display issue affecting some incoming ACH payments.
Our team is currently removing the duplicated incoming ACH entries. We will update this page as we make progress.
We'll confirm once the fix has been fully deployed.
- monitoring
The issue affecting the duplicate display of incoming ACH appears to be resolved. Our team is closely monitoring recovery to confirm full stability before closing this incident.
We'll post a final update once we've confirmed everything is back to normal.
- resolved
This incident has been resolved. Affected incoming ACH transactions are fully restored and operating normally.
What happened:
A processing error on our end caused duplicate ACH transactions to appear in some Mercury accounts. During this time, the balance may have temporarily appeared higher or lower than it should have, and may have received duplicate transaction notifications.
No further action is needed. Thank you for your patience.
Changes Rewindex caught on this incident
- Incident updated: Duplicated incoming ACH transactions
- Incident updated: Duplicated incoming ACH transactions
- Incident updated: Duplicated incoming ACH transactions
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-11-02 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
9b680f6cc0bd3b38…Version 2 captured
In the 2026-11-02 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
fee064519dcaa377…Version 3 captured
In the 2026-11-03 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
d73a96463ebee065…Version 4 captured
In the 2026-11-03 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
c4443e9229f2c1e3…
Impact, status and times are the vendor’s own, as last archived. View on status.mercury.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Mercury, started 2026-11-02 20:34 UTC, resolved after 23 h, 4 update(s); edited after publishing.
- Title
- Duplicated incoming ACH transactions
- Vendor
- Mercury
- Date
- URL
- https://rewindex.com/company/mercury/incidents/01M6EZGSCQJHJF3M6WZS10EXAW
Mercury profileRecent Mercury incidentsAll outages on November 2, 2026Mercury in November 2026MarkdownJSON