Diagnose Duplicate Payments With FMEA
Analyze a duplicate-payment failure mode and identify controls that reduce occurrence and detection gaps.
A timeout on a bill-payment request lets users retry. Some retries create a second payment instruction and a second ledger posting. FMEA: failure mode, cause, effect, detection, control. Treating duplicate payments as a support issue misses the system failure: retries were not recognized as the same intended operation. Failure mode Duplicate payment is created when the same customer retries the same bill-payment request after timeout. This defines the financial failure, not just the API symptom. Cause Client retry lacks a stable idempotency key and the ledger allows two settled states for the same external reference. Cause points to prevention controls.…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in