ACH Return Codes R01–R85: What They Mean and How Developers Should Handle Them

·1 views

The National Automated Clearing House Association (NACHA) defines 85 standardized ACH return codes, ranging from R01 to R85, each indicating a specific reason a bank transfer has failed. Common codes include R01 for insufficient funds, which is recoverable via a retry after a few business days, and R03 for an invalid account number, which requires manual review and recipient contact. Fraud-related codes such as R10 and R29 signal unauthorized transaction disputes and should trigger an immediate halt on further payouts to that account. Developers can automate recovery workflows by mapping each return code to a defined action — such as scheduling retries, escalating to compliance, or revoking ACH authorization — rather than relying on manual intervention. Return codes can arrive within two business days of settlement or as late as 60 days later, meaning reconciliation systems must remain open to late returns before treating a payout as truly final.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

New Cyber-OSINT model released

Article URL: https://twitter.com/0x0SojalSec/status/2104736980768866439 Comments URL: https://news.ycombinator.com/item?id=49890829 Points: 4 # Comments: 0

0 comments Read more at Hacker News

ProgrammingDEV Community ·

Webhook Signature Verification Alone Does Not Guarantee Request Authorization

Verifying an HMAC webhook signature only confirms that a payload originated from a vendor, not that the request is authorized to modify specific resources in your system. Developers must separately map incoming events to internal subjects and apply proper authorization checks — covering tenant, user, and resource — before executing any side effects. A correctly signed payload can still contain a spoofed tenant ID or an action the customer never permitted. Network trust and cryptographic authenticity do not substitute for a defined authorization policy. Experts recommend evaluating subject, action, and resource before mutating any system state.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Splits 2,000-Line Home Assistant Config into 8 Organised Files Using Python

A Home Assistant user refactored a bloated 2,144-line automations.yaml file — spanning 63 automations across heating, alarms, cameras, and more — into eight separate, topic-specific files. The main concern was silently breaking critical automations, such as heating controls managing 11 thermostats, during the refactor. To address this, the developer wrote a 40-line Python script to split the file and a separate verification script to confirm no automations were lost in the process. Classification was handled through substring matching on German-language automation aliases, routing each entry into a named bucket like 'heating' or 'alarm', with unmatched entries falling into a miscellaneous file. The project highlights a practical approach to managing growing smart-home configuration files without relying on metadata tags or manual reorganisation.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Build Identity-Aware AI Agents Using Microsoft Agent Framework and Auth0

A developer built a four-part tutorial series demonstrating how to add proper identity and authorization controls to AI agents using Microsoft Agent Framework and Auth0. The project centers on a fictional expense-approval agent where a manager interacts with an AI that retrieves reports, sends emails, and approves or rejects expenses on their behalf. Each agent capability — from reading expense data to taking actions — required its own distinct identity and authorization decision, rather than a single blanket permission. Auth0's Fine-Grained Authorization was used to filter accessible data before vector search runs, ensuring the underlying language model never processes information a user is not permitted to see. The series, published on the Auth0 blog, aims to address the identity and accountability gaps that most AI agent tutorials overlook entirely.

0 comments Read more at DEV Community