
The R10 return code means your customer went to their bank and said they do not know your business, or never authorized you to debit their account. The bank believed them, took the money back, and sent your ACH debit back through the network with code R10.
Of all the ACH return codes, R10 is one of the most serious. An R01 for insufficient funds or an R03 for an account that cannot be found describes a problem with the account. An R10 describes a problem with you: the account holder is saying the payment should never have happened. It cannot be fixed by sending the debit again, and it counts toward the return rate that banks watch most closely.
Here is what the code covers, how it differs from its close relatives, what it costs beyond the payment itself, and what to do when one posts.
What the R10 Return Code Means
Nacha, the organization that writes the ACH Network's operating rules, titles R10 "Customer Advises Originator is Not Known to Receiver and/or Originator is Not Authorized by Receiver to Debit Receiver's Account." In plain terms, the customer (the Receiver) has told their bank one of three things:
- They do not recognize who you are.
- They have no relationship with your business.
- They never authorized you to debit their account.
R10 also covers check-conversion entries (ARC, BOC and POP) where the signature on the source document or written authorization is not authentic, valid or authorized. For most online and phone merchants, though, an R10 means one thing: a consumer says they never agreed to this debit.
R10 is used for consumer accounts, and for consumer-type entries sent to business accounts. A CCD or CTX debit to a business account comes back as R29 instead. Either way, the return comes from the customer's bank, the RDFI, through your bank, the ODFI, and the funds come back out of your account.
R10 is also not meant for disputes about goods or services. Nacha's rule page says so explicitly for both R10 and R11. A customer who authorized your debit and is unhappy with what they received is not describing an unauthorized debit, even if that is the form they end up signing.
R10 vs R11, R07 and R29
Until April 2020, R10 was a catch-all. Nacha's own rule page describes it as having been used for many kinds of unauthorized claims, including debits where a valid authorization existed but something went wrong, such as a debit on the wrong date or for the wrong amount. Nacha's "Differentiating Unauthorized Return Reasons" rule split those error cases out into a repurposed R11 code, effective April 1, 2020.
The split matters because the two codes now lead to very different next steps:
- R10: no authorization, or the customer does not know you. To debit that account again, you need a new authorization.
- R11 ("Customer Advises Entry Not in Accordance with the Terms of the Authorization"): an authorization exists, but the entry did not match it. Examples include the wrong amount, a debit initiated earlier than authorized, a debit tied to an incomplete transaction, or an improperly reinitiated debit. You may correct the error and send a new entry without a new authorization, as long as it goes out within 60 days of the settlement date of the return.
- R07 ("Authorization Revoked by Customer"): the customer did authorize you, but has since withdrawn that authorization. You may not reinitiate the debit and must contact the customer directly.
- R29 ("Corporate Customer Advises Not Authorized"): the business-account counterpart to R10, used for CCD and CTX debits, with a 2-banking-day return window.
If you are looking at an R11 rather than an R10, our guide to the R11 check truncation entry return explains how that code changed in 2020.
How an R10 Return Reaches You
An R10 starts with the customer, not with the bank. The customer reports the debit, and before the bank can return it as unauthorized, Nacha requires the bank to obtain the customer's Written Statement of Unauthorized Debit, usually called a WSUD. Once the statement is signed, the bank returns the entry.
The window is long. Consumer debits carry an extended return period: an R10 can arrive up to 60 calendar days after the debit settled. A sale you considered closed two months ago can come back as an R10, and for a business on recurring debits, several months of payments from the same customer can be in play before anyone notices.
There is no representment process like the one for card chargebacks, where you submit evidence and the issuer decides. Your bank can dishonor a return only on narrow procedural grounds, such as a return sent after the deadline. If the return was on time and you believe the claim is false, that disagreement has to be pursued with the customer outside the ACH Network.
Why You Cannot Just Run the Debit Again
The instinct after any failed payment is to retry it. With an R10, that makes things worse.
Nacha's Reinitiation Rule states that an unauthorized debit "cannot be remedied," and that reinitiating any entry returned as unauthorized is an improper reinitiation practice. The only way back into that account is a new authorization from the customer, obtained after the return. Nacha does not allow you to collect that approval in advance. Sending the same debit again without one simply produces another unauthorized return, and another mark against your return rate.
If the customer is on a recurring schedule, stop it the day the R10 posts. A weekly or monthly debit that keeps running against an account whose holder has already called it unauthorized will keep coming back the same way.
What R10 Returns Cost Beyond the Payment
Losing the payment is only the first cost. R10 is one of six return codes Nacha treats as unauthorized returns: R05, R07, R10, R11, R29 and R51. Nacha's guidance for originators says an originator's unauthorized returns may not exceed 0.5% of its debit entries. Nacha measures that rate over the preceding 60 days or two calendar months.
That is a low ceiling. At 0.5%, five unauthorized returns on 1,000 debits puts you at the limit. Nacha also sets a 3.0% level for administrative returns (R02, R03, R04) and a 15.0% level for overall debit returns, but the unauthorized threshold is the one with the least room.
The other costs follow from there:
- The Unauthorized Entry Fee. For each debit returned as unauthorized, your bank pays a fee to the customer's bank. Payments association EPCOR advises banks to write agreements that let them pass that fee on to the originator, which is why it often shows up on your statement.
- Fines. Nacha fines are assessed against financial institutions and can reach $500,000 per month for egregious violations. Nacha notes that banks may contractually pass those fines on to their originators.
- Your ACH access. EPCOR notes that when an originator approaches or exceeds the 0.5% threshold, a bank's remediation may include suspending origination access or ending the relationship altogether.
For a high-risk business that already had to work to get ACH processing, losing it over a run of unauthorized returns is the outcome to avoid.
Why High-Risk Merchants See R10 Returns
R10 returns usually trace back to a handful of causes:
- The customer does not recognize the charge. A company name on the bank statement that does not match the brand the customer bought from makes "I don't know this business" a sincere answer.
- Fraud. Someone used another person's routing and account numbers, and the real account holder correctly reports a debit they never authorized.
- Thin authorization records. Nacha puts the burden of proving authorization on the originator. A checkbox with no record of who checked it, when, and for what terms is hard to stand behind.
- Buyer's remorse. Some customers who did authorize a debit claim they did not, especially on recurring billing they forgot about or regret.
The first three are largely within your control. The fourth is where your records and your relationship with the customer do most of the work.
What to Do When an R10 Posts
- Stop any recurring debits to that account immediately, before the next cycle runs.
- Pull your authorization record for the customer: the agreement, the timestamp, the IP address or call recording, and the terms they accepted.
- Ask your bank to request a copy of the customer's signed WSUD. EPCOR states that the customer's bank must provide a copy within 10 banking days of a request made within one year of the return's settlement date. Compare it against your records.
- Contact the customer. Some R10s come from customers who did not recognize your name and will re-authorize once they do.
- If the customer agrees to continue, obtain a new authorization before you debit the account again.
- If the claim is false, pursue the balance directly with the customer, through collections or the courts as your agreement allows. It cannot be recovered by sending another ACH debit.
- Log every R10 and watch your unauthorized return rate weekly, not just when your bank raises it.
How to Prevent R10 Returns
Prevention starts with making sure the customer recognizes you and that you can prove they agreed:
- Use a Company Name in your ACH entries that matches the name your customers know you by.
- Use the right Company Entry Description. Since March 20, 2026, Nacha requires the description "PURCHASE" on consumer debits for online purchases of goods. Our guide to the 2026 Nacha rule changes covers the other new requirements.
- Validate accounts on web-authorized debits. Nacha requires originators of WEB debits to use a commercially reasonable fraudulent transaction detection system, which can include prenotes, micro-deposits or a commercial verification service.
- Capture a complete authorization record for every customer, and keep it where you can find it quickly.
- Send a reminder before recurring debits, and make cancelling with you easy, so a customer who wants out calls you instead of their bank.
If a customer disputes a debit, our guide to ACH chargebacks walks through the full dispute process and the other return codes you are likely to see.
Keep Your ACH Processing in Good Standing
One R10 is a conversation with one customer. A steady run of them is a threat to your ACH access. High-risk payments are our whole business, and our ACH payment processing is built for merchants that mainstream processors decline. If unauthorized returns are climbing, contact us and we will review your ACH setup with you.
Category

Kyle Hall is a fintech entrepreneur, software engineer, and marketing strategist with over a decade of experience in high-risk payment processing and SaaS development. He is the CEO of PayKings, a lea...
More from Kyle Hall
Card-on-File Billing Without the $1 Test Charge
Plenty of merchants check a new card the same way: run a $1 authorization, see whether it approves, ...
Selling Ammo Online: Where a Shipping Address Isn't Enough
Ammunition is one of the few firearms products a business can sell without a federal firearms licens...
How to Sell Health Products Online: The Payments-First Guide
Most guides on how to sell health products online walk you through listing a product on a marketplac...
Remotely Created Checks Put the Loss on Your Bank, Then on You
A customer reads their routing and account numbers to you over the phone or types them into a form. ...