What Does a Returned Mobile ACH Payment Mean?

A returned mobile ACH payment means the electronic transfer you sent through your banking app or a payment platform was rejected by the receiving bank and pushed back through the network instead of clearing. The rejection comes with a standardized return code that tells you exactly why it failed, and once you know the code, the fix is usually straightforward.

Why Your Payment Came Back

Most mobile ACH returns trace to one of four problems.

Insufficient funds is the leading cause. ACH debits don’t post instantly. A payment you authorize on Monday might not try to clear until Wednesday, and if your balance drops below the transaction amount in between, the receiving bank sends it back. This is the R01 return.

Closed or frozen accounts come next. If you switched banks and didn’t update a biller, the debit aimed at the old account bounces. Freezes usually stem from fraud alerts or legal holds, but the effect on the payment is the same.

Data-entry errors cause a surprising share of failures. Transposing digits in an account number, picking the wrong account type, or entering a routing number that doesn’t match the account all produce returns. Small screens make these mistakes easy.

Bank-imposed transfer limits are the quiet fourth reason. Even with money in the account, exceeding your bank’s daily or per-transaction ceiling blocks the payment. Limits vary widely by institution and account type, so it’s worth checking yours.

Reading Your Return Code

Open the transaction details in your banking app or on the payment platform. The return code appears there, sometimes as just “R01” and sometimes with a short description. NACHA assigns these codes so every party knows exactly what happened.

Account and Funding Codes

R01 — Insufficient Funds. The account didn’t have enough money to cover the debit. The most common code by far.
R02 — Account Closed. The account no longer exists. Retrying won’t help; you need a different account.
R03 — No Account/Unable to Locate. The number format is valid but doesn’t match any open account at that bank.
R04 — Invalid Account Number. The number itself is structurally wrong, such as too few digits. This points to a typo during setup.

Authorization and Stop-Payment Codes

R07 — Authorization Revoked. You previously authorized recurring debits and then canceled that permission.¹
R08 — Payment Stopped. You placed a stop-payment order on a specific transaction. R07 revokes ongoing authorization; R08 targets a single payment.
R10 — Customer Advises Not Authorized. You told your bank the originator had no permission to debit the account at all.¹
R11 — Entry Not in Accordance With Terms. Authorization exists, but the specific payment doesn’t match what you agreed to — being charged $200 when you authorized $100, for example.¹

How to Fix It

If the Code Points to Funding (R01)

Check your available balance, not the posted balance. Pending transactions can eat into your available funds in ways that aren’t obvious on the main screen. Once the account holds enough to cover the payment plus any pending debits, resubmit through the app. If there’s no retry button, create the payment fresh.

Be aware that when a payment returns for insufficient funds, NACHA rules let the originator resubmit the same transaction up to two additional times. A single failed payment can therefore hit your account three times total, and each failed attempt can trigger another fee if the balance still hasn’t recovered. If you know a payment bounced and can’t fund the account quickly, contact the merchant to arrange an alternative rather than letting the retries pile up.

If the Code Points to Account Errors (R02, R03, R04)

Pull the routing and account numbers saved in your app and compare them digit by digit against a physical check or an official bank statement. Routing numbers are nine digits and identify the bank; account numbers vary in length and identify your specific account.² If you recently changed banks, update every app and biller that has the old account on file. An R02 won’t resolve itself — the old account is gone, and it needs to be replaced everywhere.

If the Code Points to Authorization or Stop-Payments (R07, R08)

If you intentionally revoked the authorization or stopped the payment, no fix is needed. If the return was a mistake, call your bank to lift the stop-payment order, then tell the merchant they can resubmit. Have the transaction ID and return code ready; it moves the call along.

After correcting any of these problems, allow at least two to three business days for a resubmitted payment to settle. If the situation involves a dispute or bank research, expect longer; some banks take up to ten business days to complete their review.

What a Return Can Cost You

Banks have historically charged non-sufficient funds fees when an ACH debit bounces. The average NSF fee has dropped in recent years and currently sits around $16 to $18 at most institutions, though some charge more and many large banks have eliminated the fee entirely or capped it well below that range. Your bank’s fee schedule shows the exact amount.

The fee exposure doesn’t end at your bank. The company you were trying to pay may charge its own returned-payment fee, and late-payment penalties can stack on top if the failed ACH pushed you past a due date. One bounced utility payment can generate fees from two directions.

When You Didn’t Authorize the Payment

Seeing R07, R10, or R11 on a charge you never made is actually a good sign. It means your bank caught it. But if an unauthorized ACH debit did clear, Regulation E limits your liability based on how fast you report it:

Within 2 business days of learning about the unauthorized transfer: maximum liability of $50.
After 2 business days but within 60 days of your statement: maximum liability of $500.
After 60 days from your statement date: potentially unlimited liability for unauthorized transfers that occur after that window.

Report unauthorized ACH debits to your bank immediately.³

Once you report an error, your bank must investigate within 10 business days and report its findings within three business days after that. If the bank needs more time, it can extend the investigation to 45 days, but it must provisionally credit your account within 10 business days while it works, and you get full use of those funds during the investigation.⁴

Stopping a Recurring Payment Before It Happens

Federal law also lets you stop any preauthorized recurring electronic payment. Notify your bank at least three business days before the scheduled transfer date, by phone, in person, or in writing.⁵

If you give the order orally, your bank can require written confirmation within 14 days. Miss that follow-up and the oral order expires, meaning the next debit can go through.⁵ Submit a written request right away and keep a copy. Also tell the company debiting your account that you’ve revoked authorization, which prevents them from resubmitting.

When Returns Start Adding Up

One returned payment won’t damage your banking record. A pattern of them can. Banks report accounts with repeated returned items or forced closures to ChexSystems, a consumer reporting agency most banks check before opening a new account. A negative record stays on file for five years from the report date.⁶

A ChexSystems record can make it difficult to open a checking or savings account elsewhere. Some banks and credit unions offer second-chance accounts for people with negative reports, but those often carry higher fees and fewer features. If you find inaccurate information on your report, you have the right to dispute it directly with ChexSystems under federal law.

1
Nacha. Differentiating Unauthorized Return Reasons
2
American Bankers Association. Routing Number
3
Consumer Financial Protection Bureau. Regulation E 1005.6 – Liability of Consumer for Unauthorized Transfers
4
eCFR. 12 CFR 1005.11 – Procedures for Resolving Errors
5
Consumer Financial Protection Bureau. Regulation E 1005.10 – Preauthorized Transfers
6
ChexSystems. Answers to Frequently Asked Questions