TL;DR: Ach Payments Not Working — most cases trace to a config mismatch, a hidden assumption, or a step skipped during setup. The fix path below covers the high-percentage causes first. If you're still stuck after 10 minutes, text PJ — most issues answered in one reply. 858-461-8054.
Operator Problem Guide
Ach Payments Not Working
ACH payments stop working in 2026 for one of four reasons: the bank account details were entered incorrectly (wrong routing or account number), the account was recently closed or changed, the customer's bank returned the payment (look for an R-code in your processor dashboard), or your processor put a hold on ACH transactions due to elevated return rates.
Why This Happens
Configuration gaps between tools or services
Missing integrations or manual workarounds that weren't designed to scale
Changes in vendor behavior, pricing, or API that weren't communicated clearly
What To Check First
Verify your current setup matches the vendor's latest documentation
Look for recent changes — platform updates, new team members, configuration drift
Check if the problem is consistent or intermittent (different root causes, different fixes)
When To Escalate
The problem is costing you money or customers per week
You've spent more than 2 hours on it without progress
A vendor quoted you more than $500 and you're not sure if it's necessary
Dealing with this right now?
Start with your payment processor's transaction dashboard. Find the failed payment and look for the return reason code. R01–R09 are bank-side issues the customer needs to resolve (wrong account, insufficient funds, closed account). R10–R29 are authorization issues your processor can help with. R61–R85 are rare technical errors. If you see no return code at all, the payment is still processing.
