A dishonored return is an R-code entry sent by the ODFI back to the RDFI when an original return was improper; receive dishonored returns (R61–R67 code range) via your ACH operator file within the NACHA-specified window
Parse the dishonored return code to determine the reason: R61 (misrouted return), R67 (duplicate return), R68 (untimely return), R69 (field error in original return), R70 (permissible return not accepted) — each requires a different remediation path
For R61 (misrouted), re-route the original return to the correct RDFI and notify your ACH operator of the error
For R67/R68 (duplicate or untimely return), investigate your return processing pipeline for the defect and do not re-originate the original debit without the originator's instruction
If you choose to contest a dishonored return, file a contested dishonored return within the NACHA window; document the grounds and retain evidence that the original return was proper
Update your payment record status to dishonored_return and route the exception to your ACH operations team for manual resolution; notify the originator of the outcome
Known gotchas
Dishonored return windows are tight — check current NACHA Operating Rules for exact business-day deadlines, as late filing forfeits your rights; do not rely on cached summaries of these deadlines
R69 (field error) means your original return contained a formatting error such as an incorrect amount or account number; do not simply re-send the same return file without correcting the defect
Contested dishonored returns escalate to NACHA arbitration if unresolved; document every step from initial receipt to final disposition in case arbitration is required
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp