ACH Payment Disputes, Return Reasons, and Merchant Actions

An ACH payment dispute concerns a bank-account payment handled through ACH rules and the provider’s available return or inquiry workflow. The merchant should identify the account type, return reason, authorization, and case controls before taking action.

It is not a card chargeback. The receiving bank returns the debit to the originating bank under a Nacha return reason code, and what a merchant can do next depends on the case type and the provider. Nacha is the organization that governs the ACH network. This guide covers the return codes merchants see, the clocks that apply, and the authorization record to build before responding.

{{cta}}

What Is an ACH Dispute? ACH Return vs. Card Chargeback

An ACH dispute happens when a bank customer, a business, or a receiving bank flags an ACH debit as unauthorized, inaccurate, or improperly processed. The receiving bank (the RDFI) does not “charge back” the transaction the way a card issuer would. Instead, it returns the entry to the originating bank (the ODFI) using a standardized Nacha return reason code, and the funds move back through the network. For the general idea of a reversed payment, see the payment reversal meaning explainer. A card chargeback, by contrast, is a separate contractual dispute process defined by the card networks (Visa, Mastercard, and similar); see our explainer on what is a chargeback for the full picture.

For merchants who accept ACH as a payment method, whether through a payment service provider, a bank portal, or a billing platform, the practical differences are:

• A return code, not a case number. Every ACH return carries a two-character Nacha code (R05, R07, R10, R11, R29, and others) that states why the funds came back.
• The route depends on the case. A return and an authorization inquiry are handled differently, and the controls your provider displays for the case decide what you can submit, not card-network representment rules.
• Different clocks. The customer’s filing window, the receiving bank’s return deadline, and any provider evidence deadline are separate and should not be merged into one number.
• Evidence starts before the debit. The accepted mandate, timestamp, and IP address need to exist before the debit, not after the return.

How ACH Payments Work

The Automated Clearing House (ACH) is an electronic network for bank-to-bank transfers in the United States. It carries payroll, bill payments, and online purchases, which is why any merchant that debits customer bank accounts needs to understand returns.

“In 2025, the ACH Network processed 35.19 billion payments worth $93.00 trillion, up 4.9% in volume and 7.9% in value year over year, an average of 141 million transactions a day.” Nacha ACH Network Volume Reports

Each ACH entry is identified by a three-letter code for the transaction type, and knowing the type tells you which authorization record to look for when a debit is questioned:

Valid and Invalid Reasons for ACH Disputes

Return reasons under Nacha rules center on whether the debit was authorized, whether it matched the agreed terms, and whether it was processed properly. Common valid grounds include:

1. Unauthorized Transaction: The debit was never authorized, or the authorization was canceled or revoked before a recurring debit was processed.
2. Incorrect Amount or Date: The debit differs from the agreed amount or was processed earlier than agreed.
3. Improper Processing: The debit was processed incorrectly, such as a duplicate payment.

Other complaints do not fit these grounds on their own. Buyer’s remorse, forgetting a recurring payment, or a delivery delay is not an ACH return reason, and product or service quality issues are best resolved directly with the customer. A return code records the reason given, not the customer’s intent, so do not assume friendly fraud from a claim alone.

The Impact of ACH Disputes on Businesses

ACH disputes can have significant consequences for merchants:

• Loss of Revenue: Funds may be withdrawn from the merchant’s account.
• Cash Flow Disruptions: Returns make cash flow harder to forecast.
• Additional Fees: Merchants may incur fees under their provider or bank terms.
• Reputation Damage: High dispute rates can harm relationships with banks and customers.
• Operational Challenges: Banks may impose transaction limits or hold funds longer.

Software and other digital-goods sellers face a card-side version of these disputes as well; see digital goods chargebacks for that process.

Build an ACH Return and Authorization Record

When a debit is returned or questioned, the record you assemble decides what you can do next. Start by identifying whether the case is a return or an authorization inquiry, then match it to the table below. Name one case submission owner for each case, so a manual reply and an automated submission never go out for the same debit.

R11 addresses an entry that does not follow an otherwise valid authorization, such as a wrong date or amount, so treat it as a terms mismatch. A return code is a reason classification, not independent proof of deliberate customer fraud, as Nacha’s guidance on differentiating unauthorized return reasons explains.

A refund can overlap with a return, so reconcile the original debit, the refund credit, and the return references before issuing more credit. The refund vs reversal difference matters here: a refund you initiate does not cancel a return the bank has already initiated on its own. For a broader look at where retained records come from and how they are joined, see chargeback evidence sources.

Keep the Clocks Separate

Several different clocks get mixed together in ACH guidance, and each applies to a different event:

• Customer filing: consumers generally have 60 days to report an unauthorized debit to their bank.
• Receiving-bank return: unauthorized debits to a business account must generally be returned within 2 banking days of settlement.
• Authorization inquiry: where your provider displays an inquiry, answer through that route with the accepted mandate and debit identifiers.
• Provider evidence deadline: follow the evidence_due_by value displayed on the case. Stripe’s ACH Direct Debit documentation describes a 60-calendar-day evidence window counted from dispute creation, which is not the customer’s filing window.

That same documentation also calls timely ACH disputes final in one section and describes a Counter dispute control in another. Because provider guidance can conflict, rely on the controls shown for your case rather than on a general rule.

Worked Example

Steps for Merchants

Deciding to Retry a Payment

An ACH return occurs when a payment fails to process or is reversed. Reasons include insufficient funds, a closed account, incorrect information, or an unauthorized transaction, and the bank sends a return code indicating which. Any fee depends on your provider and bank terms.

Use the following table to determine if you can retry a returned ACH Direct Debit payment:

Common ACH Return Reason Codes

Note: Repeatedly retrying transactions that cannot succeed may result in fines from Nacha and could lead to being blocked from sending new ACH transactions. Follow ACH network guidelines on retries.

ACH vs. Chargebacks

ACH disputes and card chargebacks differ in their governing rules, in who sets the clocks, and in the response route. On the card side, merchants answer with compelling evidence, often organized in a chargeback response template. For the wider card-side picture, see our chargeback statistics report. For issuer and network routes on card payments, use our directory of card network and bank disputes.

Merchants who accept both cards and ACH often pair this playbook with a chargeback alert service on the card side, since an early alert can stop a card dispute before it escalates.

New Nacha Rules Merchants Must Know in 2026

Nacha oversees the ACH network and its Operating Rules, and compliance is mandatory. It is also phasing in a fraud monitoring rule that reaches more ACH participants than banks.

These expectations sit alongside Nacha’s WEB debit account validation rule, in force since March 2021, which requires originators to verify that an account number belongs to an open, ACH-eligible account before the first debit and after any account change. Together they are part of a broader shift toward proactive ecommerce fraud prevention.

Compliance Tips for Businesses

For merchants to remain compliant, they should:

1. Obtain Proper Authorization: Secure clear, verifiable consent.
2. Maintain Accurate Records: Keep detailed transaction documentation.
3. Provide Transparent Information: Clearly state terms, pricing, and policies.
4. Assign One Case Owner: Give each return or inquiry a single case submission owner, whether the response is manual or automated.
5. Stay Informed: Regularly update knowledge of Nacha rules.

{{cta}}

ACH Disputes and Chargebacks FAQs

Is an ACH dispute the same as a chargeback?

No. An ACH dispute is processed as a return under the Nacha Operating Rules, using a return reason code such as R05, R07, R10, R11, or R29. A chargeback is a separate process run by the card networks, with representment rules specific to cards. The mechanics, timelines, and evidence a merchant can submit differ, so check the route your provider shows for the ACH case.

Can an ACH payment be disputed?

Yes. ACH payments have bank and provider dispute or return procedures. The available route depends on the payment and case type; it should not be assumed to follow card-network representment rules.

What is an ACH chargeback?

An ACH chargeback is the everyday name for an ACH return or reversal: the customer’s bank pulls back an ACH debit under a Nacha reason code, most often because the debit was unauthorized (R05, R07, R10, R29). Unlike a card chargeback, it should not be assumed to follow card-network representment rules, and the route available depends on the case.

What is an ACH claim?

An ACH claim is a customer’s formal report to their bank that an ACH transaction was unauthorized, duplicated, or processed for the wrong amount or date. If the bank accepts the claim within the allowed window, it returns the debit to the merchant’s bank and the funds are reversed.

How long do you have to dispute an ACH transaction?

Consumers generally have 60 days to report an unauthorized debit to their bank, and unauthorized debits to a business account must generally be returned within 2 banking days of settlement. A provider’s evidence deadline is a separate clock: use the evidence_due_by value shown on the case.

Can a merchant respond to an ACH dispute?

Sometimes. The available response depends on the return or inquiry type and the controls your provider displays. Use the displayed route and deadline, assemble the accepted mandate, debit identifiers, and return code, and resolve complaints directly with the customer where that is appropriate.

Can a merchant reuse an ACH mandate after a dispute?

Do not automatically reuse disputed or invalid authorization. Check the provider’s mandate state, resolve the issue with the customer, and collect new authorization where required before another debit.

What are the most common ACH return codes?

The most common are R01 (insufficient funds), R02 (account closed), R05 and R10 (unauthorized consumer debit), R07 (authorization revoked), R11 (entry not in accordance with the authorization terms), and R29 (corporate customer advises not authorized). Insufficient-funds returns may be retried within Nacha’s reinitiation limits; R11 can be corrected and resubmitted without new authorization; the unauthorized-return codes require new authorization before another debit.

Protect Your Business From Costly ACH Returns

Telling ACH returns apart from card chargebacks, and keeping an authorization record ready, helps merchants who accept bank debits limit operational disruption and revenue loss. Assign one case submission owner so manual and automated work never overlap.

For supported card-payment workflows, connect relevant evidence collection and response submission with Chargeflow Automation. Get started now.