Monitor ACH return rates against NACHA thresholds using the Unit platform
domain: docs.unit.co · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Enable ACH origination on your Unit application and configure webhooks for `payment.returned` events.
For each returned payment event, capture the return reason code from the webhook payload.
Calculate your **unauthorized return rate** using codes R05, R07, R10, R29, and R51 over the preceding 60 days as a percentage of total ACH debits; the NACHA threshold is **0.5%**.
Calculate your **administrative return rate** using codes R02, R03, and R04 over the preceding 60 days; the NACHA threshold is **3.0%**.
Calculate your **overall return rate** using all return codes over the preceding 60 days; the NACHA threshold is **15%**. Alert your team if any rate approaches 80% of the respective threshold.
The calculation window is the **preceding 60 days**, not calendar month; use a rolling window in your monitoring logic.
R02 (account closed), R03 (no account), and R04 (invalid account) are administrative returns — they indicate data quality issues, not unauthorized transactions, and must be tracked separately from the unauthorized return bucket.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?