
An R07 return means your customer's bank sent an ACH debit back with the reason "Authorization Revoked by Customer." Your customer is not saying they never agreed to pay you. They are saying they did agree, then told you to stop, and you debited them anyway.
That makes R07 different from most return codes. It usually points to something inside your own business: a cancellation that never reached billing, a retention offer that held a cancel request open, or a recurring schedule nobody switched off. This guide covers what the code means, what you can and cannot do once one posts, and how to stop the next one.
What the R07 Return Code Means
In ACH terms, your customer is the Receiver, their bank is the RDFI, and your business is the Originator. A customer's bank can use R07 when the customer has signed a Written Statement of Unauthorized Debit (WSUD) saying the authorization was revoked directly with the Originator, under the terms of the authorization agreement. The Clearing House's payments association described the code that way in its 2021 guidance to banks.
Two points in that description matter most to a merchant:
- The revocation was made with you, not with the bank. R07 is the customer's claim that they told your business to stop.
- The bank does not have to prove it. The Clearing House notes that the customer's bank is not required to produce proof that authorization was revoked. Your bank can ask for a copy of the customer's signed statement.
When Nacha reorganized its unauthorized-return rules, in a change that took effect in two phases on April 1, 2020 and April 1, 2021, it folded "authorization revoked" into the rule section on unauthorized debits. It kept R07 as the return code for that situation. A consumer's bank has 60 calendar days to send an R07 back, according to EPCOR's return reason code guide for originators. A debit from early in the quarter can still come back weeks later.
R07 vs R08 and R10
Three return codes get confused because each one starts with a customer talking to their bank. Here is how they differ:
- R08 (Payment Stopped): the customer asked their bank to stop one specific debit. It is a stop-payment order, not a claim that the authorization is gone. The relationship can often be repaired with a phone call. See our guide to the R08 return code.
- R07 (Authorization Revoked by Customer): the customer says they ended the authorization with you, so every debit after that point is unauthorized.
- R10: the customer says they never authorized the debit at all, or does not know your business. See our guide to the R10 return code.
The difference between R07 and R08 often comes down to what the customer said and how the bank coded it. Under Regulation E, a consumer can stop payment of a preauthorized transfer by notifying their bank at least three business days before the scheduled date. Once a bank is told that the consumer's authorization is no longer valid, the CFPB's official commentary says it must block all future payments for that debit from that payee. (The commentary allows an alternative procedure for a bank that has no way to block the debit.) The bank may not wait for the merchant to stop the debits. It may ask the consumer for a copy of the revocation as written confirmation within 14 days of an oral notice. If that confirmation does not arrive, it may honor later debits.
In practice, this means a customer who tells their bank "I canceled with them and they keep charging me" can have every future debit from you blocked. You may not hear about it until the debits start coming back.
Why R07 Returns Count Against You
Nacha treats six return codes 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 originated debit entries. At 10,000 debits a period, that is 50 unauthorized returns in total, across all six codes.
Nacha's enforcement runs through the banks. Its guidance says Nacha assesses fines to financial institutions, and those institutions may contractually pass the fines on to originators. In practice your processor or ODFI also passes the pressure down through reserves, origination limits or a review of your ACH program. A merchant with a cancellation problem can reach that line faster than one with a fraud problem, because every customer who canceled and kept getting billed is a potential R07 on every later cycle.
Can You Debit the Account Again?
Not on the authorization you had. Nacha's position on unauthorized returns is blunt: an unauthorized debit cannot be remedied. Reinitiating any entry returned as unauthorized is an improper reinitiation. EPCOR's guide says the same about R07 in particular: you may not reinitiate entries returned with this code, and you must contact the customer directly.
There is one way back. Under Nacha's reinitiation rule, a debit is not a reinitiation if you get a new authorization from the customer after you receive the return. The timing is strict. Nacha says originators may not get advance approval to debit an account in a way that would otherwise break the reinitiation rule. A clause in your original terms saying the customer pre-agrees to re-debits after a return does not count.
If the customer really does owe you money, for example for services they used before canceling, collect it with a new authorization, a different payment method, or your normal collections process. Do not resend the ACH debit.
What to Do When an R07 Posts
- Stop the schedule. Turn off every recurring debit tied to that account today, before the next cycle runs. Every later debit on that schedule is likely to come back R07 as well.
- Find the revocation. Search your support tickets, emails, chat logs, call recordings and cancellation forms for the customer's request. In most cases it is there, and it shows exactly where your process broke.
- Ask your bank for the WSUD if you need it. Your ODFI or processor can request a copy of the customer's signed statement from the customer's bank. It tells you what the customer claimed and when.
- Contact the customer. If they canceled, confirm the cancellation, refund anything billed after it if you owe it, and close the account cleanly. If they owe a legitimate balance, ask for a new authorization or another way to pay.
- Fix the cause. One R07 is a customer-service problem. A pattern of them is a billing-system problem, and it is visible to your processor.
Where R07 Returns Usually Come From
R07s are seldom about fraud. They come from the gap between what the customer did and what your billing system did next. Common causes:
- A cancel request that sits in a support queue while the billing run goes out.
- Retention flows that make the customer go through several offers, so they give up and call their bank instead.
- A cancellation recorded in your CRM that never reaches the payment schedule in your gateway or billing platform.
- Cancellations sent to an email inbox or phone line no one checks, especially after a staff or vendor change.
- Paused or downgraded plans whose old debit schedule keeps running.
How to Prevent R07 Returns
Most R07 prevention is ordinary operations work. Start with the authorization itself. Nacha consultants describe a compliant ACH authorization as one that tells the Receiver how to revoke it directly with the Originator, including the timing, and how to let the Originator know. If your authorization does not say clearly how and when to cancel, customers will go to their bank instead, and the bank's answer is an R07.
- Name a revocation channel you actually monitor, such as an online cancel button, a dedicated email address or a phone line. State it in the authorization and in every receipt.
- Connect cancellation to billing automatically. A cancel event should remove the customer from the next debit run without someone having to update it by hand.
- Set a cutoff and honor it. If a cancel arrives too close to a scheduled debit to stop it, refund the debit right away instead of waiting for a return.
- Send confirmation. Email the customer when a cancellation takes effect, so they have no reason to call their bank to make sure.
- Keep records. Bank guidance for originators states that authorizations must be kept for two years after they are terminated or revoked. Keep the cancel request too, with its date and time.
- Watch your unauthorized return rate weekly, not monthly. A rise in R07s usually tracks a specific change, such as a new retention script, a billing migration or a support backlog.
R07 Returns in High-Risk Recurring Billing
Subscription, membership and continuity businesses carry more R07 exposure than one-time sellers because they debit the same accounts again and again. One missed cancellation turns into a return on every cycle until someone notices. High-risk merchants also tend to have less room before a processor steps in, so a run of R07s can lead to a reserve, a volume cap or an ACH shutdown long before the 0.5% line is crossed.
If you bill by ACH on a recurring schedule, make your cancellation process as easy to find as your signup. It is the cheapest fix there is for R07 returns.
PayKings works with recurring-billing merchants in high-risk verticals to set up ACH and card processing that can handle a real return rate. If R07s or other unauthorized returns are putting your ACH program at risk, talk to our team about your options.
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
Merchant Account Early Termination Fee: How It's Calculated
Most merchants learn what their processing contract says about leaving at the moment they try to lea...
What Is Mastercard BRAM, and Why Does It Close Merchant Accounts?
Most merchant account terminations come with a reason the merchant can see coming: a chargeback rati...
How Does a Merchant Account Work & What It Is
A merchant account is a specialized account that holds funds from your customers' card payments befo...
How Do Chargebacks Work? The Chargeback Process Explained for Merchants
A chargeback is money leaving your account whether you agree with it or not. Knowing exactly how tha...