Chemical Bank ATM double-debit software bug
A software bug at Chemical Bank caused roughly 100,000 customer accounts to be debited twice for the same ATM and debit-card transactions over a single day.
The damage was public. The root cause was preventable.
A software bug at Chemical Bank caused roughly 100,000 customer accounts to be debited twice for the same ATM and debit-card transactions over a single day.
What the software actually got wrong
A bug in an updated version of the bank's account-processing software caused it to apply certain transactions to customer accounts twice instead of once during an overnight batch run, and the error was not caught until customers began reporting the duplicate charges the next morning.
A bug in an updated version of the bank's...
A bug in an updated version of the bank's account-processing software caused it to apply certain transactions to customer accounts twice instead of once during an overnight batch run
Requs AI Edge Case flags this exact pattern at the requirements and architecture stage — before a single line of code implementing it exists — so the assumption behind it gets challenged while it is still cheap to fix.
The error was not caught until customers began reporting...
the error was not caught until customers began reporting the duplicate charges the next morning
Requs AI Software FMEA traces this failure mode back to the system-level hazard it feeds, tagging it against the Common Defect Enumeration so it surfaces in review instead of in the field.
Beyond code coverage and "shall" testing
Root causes like this one rarely show up in code coverage or requirements-compliance testing, because nobody wrote a requirement anticipating the specific edge case that broke. Requs AI Edge Case and Requs AI Software FMEA are built to surface exactly this class of overlooked failure mode — before the software is written.
Surfaces this before code exists
Identifies edge cases like this one at requirements and architecture time, using the Common Defect Enumeration to catalog failure patterns seen across hundreds of real-world software failures — including this one.
Connects the failure mode to the hazard
Traces this class of root cause directly to the system-level hazard it can produce, so a defect pattern like this one gets flagged during design review instead of after it ships.
Find the overlooked root causes before they ship.
Schedule a demonstration, or explore how Requs AI Edge Case and Software FMEA use the Common Defect Enumeration.