# ACH Fraud
Source: https://paymentsandrisk.com/docs/fraud/types/ach-fraud

Last updated 4 November 2026.

TL;DR

-   **ACH fraud** means unauthorized bank debits or fraudulent payment redirects
-   Different from card fraud: a return can arrive the same day or weeks later, liability rules differ, no chargeback system
-   **BEC (Business Email Compromise)** can redirect ACH payments. IC3 recorded about $3.05B in BEC losses across payment methods in 2025
-   Account checks help, and one is required on online consumer debits. They don't prove the payee is who they claim to be
-   Return deadlines depend on the entry and the account: about 60 days after settlement for an unauthorized consumer debit (R10), 2 banking days for a CCD or CTX debit on a business account (R29). Late returns and warranty claims can follow; see [return timeframes](https://paymentsandrisk.com/docs/payments/payment-methods/bank-transfers/#return-timeframes)
-   Prevention: check a bank account before you debit it, confirm a new payee through a contact you already know, and have two people approve each payment (dual authorization)

A customer's bank payment came back as unauthorized? Start with [the R10 options](https://paymentsandrisk.com/docs/fraud/types/ach-fraud/#r10-deep-dive). A supplier asked you to pay a new bank account? [Verify it by phone first](https://paymentsandrisk.com/docs/fraud/types/ach-fraud/#1-business-email-compromise-bec). Already sent money to the wrong account? [Call your bank now](https://paymentsandrisk.com/docs/fraud/types/ach-fraud/#when-you-discover-bec).

ACH fraud works differently than card fraud. The timing's different, the liability depends on the entry and the account, and a fraudster can get paid by fooling your staff without breaking into anything.

## ACH vs. Card Fraud

```mermaid
flowchart LR
    subgraph Card["Card Fraud"]
        C1[Transaction] --> C2[Instant decline<br/>or approval]
        C2 --> C3[Chargeback weeks<br/>or months later]
    end
    subgraph ACH["ACH Fraud"]
        A1[Entry submitted] --> A2[Settlement<br/>same day or later]
        A2 --> A3[Return timing depends<br/>on the entry and account]
    end

    style C2 fill:#1f6f4a,color:#fff
    style A2 fill:#9a5b00,color:#fff
```

| Factor | Card Fraud | ACH Fraud |
| --- | --- | --- |
| Real-time authorization | Yes | No |
| Instant decline possible | Yes | No issuer decline at checkout. You can check the account first, and a return comes later |
| Dispute timeline | Varies by network and reason code | Depends on the return and the account ([timeframes](https://paymentsandrisk.com/docs/payments/payment-methods/bank-transfers/#return-timeframes)). Later warranty claims are separate |
| Liability framework | Network rules | Depends on the entry: Reg E, UCC, Nacha rules, your bank agreement |
| Fraud detection tools | Network and vendor tools | Account checks, payee confirmation and risk-based monitoring |
| Liability shift available | On eligible 3DS payments | No |

* * *

## Types of ACH Fraud

### 1\. Business Email Compromise (BEC)

**Check payment-change requests carefully.** [FBI IC3 recorded about $3.05 billion in reported BEC losses in 2025](https://www.ic3.gov/AnnualReport/Reports/2025_IC3Report.pdf). That covers BEC across payment methods, not just ACH.

BEC can work without touching your payment system. It tricks your employees into making legitimate-looking payments to fraudsters.

| BEC Variant | How It Works |
| --- | --- |
| **Invoice fraud** | Fake or modified vendor invoice with fraudster's bank details |
| **CEO impersonation** | "Urgent" email from "CEO" requesting wire/ACH payment |
| **Vendor impersonation** | Email from compromised vendor requesting updated bank info |
| **Payroll redirect** | Employee "requests" direct deposit change to fraudster account |
| **Lawyer impersonation** | Fake attorney requesting payment for confidential matter |

**Detection signals:**

-   Email domain slightly off (acme-inc.com vs. acmeinc.com)
-   Urgency pressure ("must send today")
-   Request to bypass normal approval process
-   New or changed bank account details
-   Request to keep transaction confidential

**Prevention:**

-   Verify bank changes by phone (using known number, not email signature)
-   Dual authorization for payments above threshold
-   Payment verification callbacks for new vendors
-   Email security (DMARC, SPF, DKIM)
-   Employee training on BEC tactics

### 2\. Unauthorized Account Activity and Debits

Someone debits a bank account without authorization. The account holder tells their bank, which can return the debit.

| Scenario | How It Happens |
| --- | --- |
| Stolen account credentials | Fraudster obtains routing/account numbers |
| Account takeover | Fraudster takes over the victim's account and sends money out. That's an outgoing credit, so the debit return may not apply |
| Continued debits | Company keeps debiting after the customer revoked permission |
| Identity theft | Fraudster opens account in victim's name |

**Return codes you'll see.** Check both the entry's SEC code and the account type, because R10 can also apply to a consumer entry sent to a business account ([Nacha's rule](https://www.nacha.org/rules/differentiating-unauthorized-return-reasons), effective 1 April 2020). Each code is a stated reason, not proof of fraud:

-   R10: Customer says a debit wasn't authorized
-   R29: A business says a CCD or CTX debit wasn't authorized
-   R07: The customer revoked permission for the debit

### 3\. Return Manipulation

Legitimate customer initiates payment, then claims unauthorized to get money back.

This is ACH's version of "[friendly fraud](https://paymentsandrisk.com/docs/fraud/types/friendly-fraud/)":

-   Customer authorized the payment
-   Customer received goods/services
-   Customer claims "unauthorized" to reverse payment

A return reason alone doesn't show this. Investigate before you call it.

**Challenge:** ACH has no 3DS or CVV. Your evidence is the authorization record. A consumer debit needs one that's written and signed or similarly authenticated, or a permitted oral route ([Nacha's authorization rules](https://www.nacha.org/rules/meaningful-modernization), effective 17 September 2021). Consent to share bank data is a separate thing ([Nacha bulletin](https://www.nacha.org/system/files/2024-11/Nacha_Operations_Bulletin_No3-2024_Open_Banking_and_ACH_Payments_10-31-24.pdf), 31 October 2024).

### 4\. Push Payment Fraud

Victim is tricked into sending money to fraudster's account.

Unlike unauthorized debits (pulls), push payments are initiated by the victim, so they're hard to recover. Call the bank anyway and ask what it can stop.

| Scenario | Example |
| --- | --- |
| Romance scam | Victim sends money to fake romantic interest |
| Investment scam | Victim invests in fake opportunity |
| Overpayment scam | Victim "refunds" overpayment from fake check |

**Your exposure:** If you're a platform facilitating person-to-person transfers, push payment fraud can hit your reputation and create regulatory scrutiny.

* * *

A customer overpaid a sale or job by check? [Check the original payment before sending money back](https://paymentsandrisk.com/docs/payments/p2p-and-project-deposits/#check-overpayment).

## ACH Return Codes and What They Tell You

| Return Code | Meaning | What to Read Into It |
| --- | --- | --- |
| **R01** | Insufficient funds | Not a fraud signal on its own |
| **R02** | Account closed | Could be stolen account |
| **R03** | No account / unable to locate | Fake or mistyped account number |
| **R04** | Invalid account number | Typo or fake |
| **R07** | Authorization revoked | Permission for the debit is gone. That doesn't have to cancel the contract or the debt |
| **R08** | Payment stopped | A stop payment. It doesn't say why |
| **R10** | Customer advises unauthorized | An allegation. Could be fraud, a false claim or a real authorization problem, so investigate |
| **R11** | Debit doesn't match the authorization's terms | Check the amount, date and other authorized terms |
| **R29** | Corporate unauthorized | The business route for CCD and CTX entries. Investigate it the same way |

### R10 Deep Dive

R10 (Customer Advises Not Authorized) is the closest thing ACH has to a fraud chargeback. It's a claim from the customer's side, not a finding of fraud.

**Timeline:**

-   For the bank's return deadline, use the [consumer debit return rules](https://paymentsandrisk.com/docs/payments/payment-methods/bank-transfers/#return-timeframes).
-   Regulation E's consumer notice clock is separate: 60 days after the bank sends the statement showing the error, longer in extenuating circumstances.

**Your options:**

-   Contact the customer to resolve the unpaid invoice.
-   Supply authorization records if your provider requests them for an inquiry.
-   An ordinary timely Stripe or Square ACH return has no card-style appeal.

**Prevention:** Check the bank account before you debit it, and keep the customer's authorization records.

* * *

## ACH Verification Tools

### Bank Account Verification

Tools that check an account before you debit it. Access to an account and the owner's name are separate checks, and neither proves the person in front of you is the owner ([what each one shows](https://paymentsandrisk.com/docs/fraud/types/ach-fraud/#what-verification-does-and-doesnt-prove)). Products as read on 3 November 2026:

| Tool | What It Does | Limitations |
| --- | --- | --- |
| **Plaid Auth** | Bank login, or automated, same-day or instant micro-deposit routes ([methods](https://plaid.com/docs/auth/coverage/)) | Coverage and timing depend on the method. A login could be a takeover |
| **MX** | Account and owner verification ([products](https://www.mx.com/products/instant-account-verifications/)) | Owner data shows who holds the account, not who's asking |
| **Yodlee** | Account verification, with holder details ([docs](https://developer.yodlee.com/products/yodlee/account-verification)) | Same limit |
| **Small-deposit verification** | Small deposits the customer confirms. [Nacha Micro-Entries](https://www.nacha.org/micro-entries) are small ACH entries, effective 16 September 2022. [Plaid](https://plaid.com/docs/auth/coverage/) also offers a coded Same Day ACH or instant RTP or FedNow deposit, read 4 November 2026 | Network time and the customer's response time depend on the method. Shows access, not ownership |
| **Prenotes** | Zero-dollar test transaction | Only checks account exists, not ownership |

### What Verification Does and Doesn't Prove

| Verification Type | Proves | Doesn't Prove |
| --- | --- | --- |
| Account login link | Account exists, someone can log in | The person is the owner (could be ATO) |
| Micro-deposit verification | Account exists, someone can see deposits | Account ownership |
| Name match, where the product checks it | Name on account | Account wasn't compromised |
| Balance check | Funds available when you checked | Funds will still be there tomorrow |

Verification Limits

Account checks alone won't stop BEC. An account can be real and verified and still belong to the fraudster. Confirm the payee through a contact you already had, and add risk-based monitoring for unauthorized payments and payments made under false pretenses.

* * *

## Timing Windows and Liability

### Consumer ACH (Reg E)

For an unauthorized debit made without an access device, Regulation E's $50 and $500 loss-or-theft tiers don't apply. A consumer who reports the debit within 60 calendar days after the bank sends the statement showing it has no liability for that debit. The bank's Nacha return deadline is separate; see [return timeframes](https://paymentsandrisk.com/docs/payments/payment-methods/bank-transfers/#return-timeframes).

### Corporate ACH (UCC)

Corporate accounts have different rules:

-   Regulation E covers qualifying consumer accounts, not ordinary business accounts ([section 1005.2(b)](https://www.consumerfinance.gov/rules-policy/regulations/1005/2/#b))
-   For an unauthorized CCD or CTX debit on a business account, the bank must meet the [ordinary R29 return deadline](https://paymentsandrisk.com/docs/payments/payment-methods/bank-transfers/#return-timeframes). Report it to your bank immediately
-   A separate [authorization-warranty claim](https://www.nacha.org/rules/limitation-warranty-claims) can follow (effective 30 June 2021)
-   Bank agreements vary significantly

**For merchants:** R29 has a shorter ordinary return deadline than a consumer unauthorized debit. It isn't absolute finality. Check the SEC code too, because R10 and R11 can apply when a consumer entry hits a business account.

### Same-Day ACH

Same-day ACH (SDA) speeds up settlement but also speeds up fraud:

-   Eligible entries can settle the same banking day ([windows and limits](https://paymentsandrisk.com/docs/payments/payment-methods/bank-transfers/#same-day-ach-settlement-windows-all-times-eastern))
-   Less time to catch fraudulent transactions
-   Returns can arrive the same day. Same-day settlement doesn't remove later return rights

* * *

## Prevention Strategies

### Required at Any Size

Two of these aren't choices ([2026 checklist](https://paymentsandrisk.com/docs/payments/payment-methods/bank-transfers/#nacha-requirements-in-effect-in-2026)):

-   **Validate the account number on online consumer debits.** Nacha's [WEB debit rule](https://www.nacha.org/rules/supplementing-fraud-detection-standards-web-debits), effective 19 March 2021, requires a commercially reasonable check at first use or when the number changes, with its stated exceptions.
-   **Run risk-based fraud monitoring suited to your role.** [Nacha's Phase 2 rule](https://www.nacha.org/rules/risk-management-topics-fraud-monitoring-phase-2), in practice from 22 June 2026, covers the remaining non-consumer originators whatever their volume, with a review at least once a year. It doesn't have to run before processing.

A balance check or a first-payment hold doesn't replace either one.

### For Inbound Payments (Customers Paying You)

| Strategy | What It Does |
| --- | --- |
| **Bank account verification** | Confirm account exists and customer can access |
| **Name matching** | Check name on account matches customer name |
| **First-payment holds** | Choose a fulfillment delay from return exposure, provider terms and customer promises. A hold doesn't eliminate later unauthorized returns |
| **Balance verification** | Confirm funds available before shipping |
| **Velocity limits** | Limit new account payment amounts |

### For Outbound Payments (You Paying Others)

| Strategy | What It Does |
| --- | --- |
| **Dual authorization** | Two approvers for payments above threshold |
| **Callback verification** | Call vendor to verify bank changes (use known number) |
| **Payment delay** | Choose an internal verification delay that fits payment deadlines and exposure; release only after independently checking the payee |
| **Email security** | DMARC, SPF, DKIM to prevent spoofing |
| **Training** | Employees trained on BEC tactics |
| **Monitoring** | Flag new payees, changed accounts and odd amounts, even when a payment looks authorized |

### BEC-Specific Controls

```text
□ All bank account changes require phone verification
□ Dual authorization for payments > $X
□ Set a new-payee delay from verification time and payment deadlines; don't release on elapsed time alone
□ Vendor management database (no ad-hoc payments)
□ Email security configured and monitored
□ Regular BEC awareness training
□ Clear escalation path for suspicious requests
```

* * *

## Responding to ACH Fraud

### When You Receive an R10/R29 Return

```text
□ Identify the transaction and customer
□ Review authorization evidence
□ Check for pattern (same customer, same behavior)
□ Contact the customer about the unpaid invoice
□ Send authorization records if your provider requests an inquiry response
□ At Stripe and Square, an ordinary timely return has no card-style appeal
```

### When You Discover BEC

```text
□ Immediately contact your bank
□ Request wire recall or ACH return (time-sensitive)
□ Document everything (emails, approvals, timeline)
□ Report to FBI IC3 (ic3.gov)
□ Engage legal if significant amount
□ Review and strengthen controls
```

What to say when you call:

> I'm calling about a fraudulent payment from our account: \[amount\] on \[date\] to \[receiving bank and account\]. We were deceived into sending it. What can you stop or recall, and what do you need from me?

### Recovery Options

Ask your bank what it can still do, as fast as you can:

| Situation | What to Do |
| --- | --- |
| Caught within hours | Ask for a recall now, while the funds may still be there |
| Caught a day or two later | Call anyway. Ask whether the receiving bank has frozen anything |
| Caught after settlement | Ask which return or recall route still applies, and file with IC3 |
| Fraudster's account still has funds | Ask your bank and a lawyer about freezing or recovering them |

* * *

## Test to Run

**ACH fraud prevention audit:**

```text
Inbound payments:
□ How do we check a bank account, and what does that check actually show?
□ Do we hold first ACH payments from new customers?
□ What's our R10 rate? Is it trending up?

Outbound payments:
□ Who can add new payees?
□ How do we verify bank account changes?
□ Do we have dual authorization for large payments?
□ When did we last train staff on BEC?

Record answers. If you can't answer these, you have gaps.
```

* * *

## Scale Callout

The two required items above apply at every size. This is the rest.

| Volume | Focus |
| --- | --- |
| **Under $100k/mo ACH** | Basic verification (Plaid or micro-deposits). Manual review of returns. |
| **$100k-$1M/mo ACH** | Automated verification. First-payment holds. R10 monitoring. |
| **Over $1M/mo ACH** | Full verification stack. Balance checks. Velocity limits. Real-time return monitoring. |
| **B2B outbound payments** | BEC controls are critical. Dual auth. Callback verification. |

* * *

## Where This Breaks

1.  **BEC can get past payment controls.** It tricks employees into making payments that look legitimate, so a control that only asks whether the payment was authorized says yes. Monitoring new payees and changed accounts can still flag it.

2.  **Verification doesn't prove payee identity.** Verifying a bank account confirms the account is real. It doesn't confirm the payee is who they claim to be.

3.  **Same-day ACH reduces detection time.** Faster settlement means less time to catch fraud before funds move.

4.  **Business accounts don't get Reg E.** A business has its bank agreement, Nacha rights and the transfer law that applies. Read the agreement before you need it.


* * *

## Next Steps

**Accepting ACH payments?**

1.  [Validate the account](https://paymentsandrisk.com/docs/fraud/types/ach-fraud/#bank-account-verification): Required on online consumer debits. Plaid, MX or micro-entries are ways to do it
2.  [Set when you fulfill a first payment](https://paymentsandrisk.com/docs/fraud/types/ach-fraud/#for-inbound-payments-customers-paying-you): Go by provider terms, return exposure and what you've promised the customer
3.  [Monitor R10 returns](https://paymentsandrisk.com/docs/fraud/types/ach-fraud/#r10-deep-dive): Track the rate and investigate spikes

**Making ACH payments?**

1.  [Require dual authorization](https://paymentsandrisk.com/docs/fraud/types/ach-fraud/#for-outbound-payments-you-paying-others): Two approvers above a threshold
2.  [Verify bank changes by phone](https://paymentsandrisk.com/docs/fraud/types/ach-fraud/#bec-specific-controls): Never trust email alone
3.  Train on BEC: Quarterly awareness training

**Had an ACH fraud incident?**

1.  [Contact your bank immediately](https://paymentsandrisk.com/docs/fraud/types/ach-fraud/#responding-to-ach-fraud): Speed matters for recovery
2.  Report to [FBI IC3](https://www.ic3.gov/)
3.  Review controls: What would have prevented this?

* * *

## Related Topics

-   [Prevent Fraud](https://paymentsandrisk.com/docs/fraud/): The fraud hub
-   [ACH Operations](https://paymentsandrisk.com/docs/operations/ach-operations/): ACH processing operations
-   [ACH Return Codes](https://paymentsandrisk.com/docs/reference/return-codes/ach/): Full return code reference
-   [Bank Transfers](https://paymentsandrisk.com/docs/payments/payment-methods/bank-transfers/): Payment method overview
-   [BEC & Phishing](https://paymentsandrisk.com/docs/fraud/types/bec-phishing/): Email-based fraud
-   [Third-Party Fraud](https://paymentsandrisk.com/docs/fraud/types/third-party/): Stolen credentials fraud
-   [Friendly Fraud](https://paymentsandrisk.com/docs/fraud/types/friendly-fraud/): False claims of unauthorized
-   [Settlement & Reconciliation](https://paymentsandrisk.com/docs/payments/settlement/): ACH timing
-   [Money Held or Frozen](https://paymentsandrisk.com/docs/operations/holds-and-reserves/): Managing ACH risk
-   [Outbound ACH Fraud](https://paymentsandrisk.com/docs/fraud/types/outbound-ach-fraud/): Supplier payment fraud and ACH origination risks
