Tool 20 · Payment Operations

A2A Payment Failure
Analyser + RCA Generator

Paste a list of NACHA return codes or open banking error codes and receive a structured root-cause analysis report with recovery recommendations and pattern detection.

Processed entirely in your browser · No data retained NACHA R-codes · FedNow · RTP · SEPA · Rule-based RCA
Input: Payment Log Data
📂
Drop CSV here or click to browse
CSV · max 50,000 rows · columns auto-detected
Rail
Date column
Amount column
Paste or upload payment data, then click Analyse.
Total Records
parsed
Failure Rate
of all records
Failed / Returned
records
Unique R-Codes
distinct codes
Top Failure
by volume
Failed Value
sum of failures
Code Reason Category Count % of Failures Distribution Failed Value

Failure frequency by hour-of-day (columns) and day-of-week (rows). Darker red = more failures. Requires timestamp data in your input.

Low
High Grey = no data for this cell

What this tool does: This analyser parses raw A2A payment log data (CSV, JSON, or plain text), extracts failure and return-code signals, clusters them into root-cause categories using rule-based JS conditionals, renders a time-of-day failure heatmap, and generates a structured markdown RCA report with recommended remediation actions — all in your browser with zero data retained after the session.

Accepted input formats:
CSV — with or without headers. Auto-detects columns: return_code, status, amount, timestamp, rail. Column names configurable above.
JSON — array of payment objects. Same field names.
Plain text — one record per line. NACHA return codes (R01–R85) extracted via regex. Status words (FAILED, RETURNED, SETTLED, PENDING) extracted via regex.

RCA clustering logic (transparent JS conditionals): Each failure is assigned to a root-cause cluster based on its return code:
NSF / Insufficient Funds → R01, R09
Account Issues → R02, R03, R04, R15, R16
Authorisation / Consumer Dispute → R05, R07, R10, R29
Routing / Technical → R13, R17, R18, R19, R25, R26, R27, R28
Operations / Timing → R06, R08, R20, R21, R24, R68
Cross-border → R80–R85

Heatmap: Requires a parseable timestamp column. Failures are bucketed by ISO weekday (Mon–Sun) and hour-of-day (0–23 UTC). Cells with zero failures are greyed. The darkest red cell represents the peak failure concentration — a useful signal for batch-window timing issues common in ACH.

Data privacy: No data leaves your browser. The tool does not log, store, or transmit any payment records, return codes, entity names, or amounts. All analysis runs locally. The session is cleared on page refresh.

Source: Built by AINumbers.co · Tool 20 · MIT License.