R29 is the ACH return code for "Corporate Customer Advises Not Authorized." A business customer (a non-consumer) told its bank that a specific debit wasn't authorized. It applies to corporate debit types, CCD and CTX. Corporate debits carry the standard two-day right of return, not the 60 days consumers get. Nacha counts R29 as an unauthorized return, against a 0.5% threshold measured over 60 days or two calendar months. The debit can't be sent again unless the customer gives a new authorization after the return.
What does R29 mean?
R29 is "Corporate Customer Advises Not Authorized." Nacha describes it as the bank being notified by the receiver, a non-consumer, that a specific debit has not been authorized.
In plain terms, the account belongs to a business, and the business says it didn't agree to this debit.
When is R29 used instead of R10?
It depends on who owns the account and the type of debit:
| Code | Used for |
|---|---|
| R10, R11 | Consumers, or consumer debit types sent to business accounts |
| R29 | Corporate debits (CCD and CTX) to business accounts |
| R05 | A CCD or CTX debit sent to a consumer's account without authorization |
So if you bill a company on a corporate debit and it disputes the payment, expect R29. If you bill an individual, expect R10 or R07.
Who sends an R29, and how fast?
The business's bank (the RDFI). Nacha's guidance for originators is that corporate debit types carry the standard right of return of two days, while consumer debit types carry the extended 60-day right. Stripe describes the same split: customers can generally dispute a debit for up to 60 calendar days on a personal account, or up to two business days on a business account.
So an R29 arrives within days of the payment, not weeks.
Does R29 count against my return rates?
Yes. Nacha's unauthorized return rate covers R05, R07, R10, R11, R29 and R51. The threshold is 0.5% of debits over the preceding 60 days or two calendar months. R29 also counts toward the 15.0% overall level for all debit returns.
Can I send the debit again?
No. Nacha says an unauthorized debit cannot be remedied. Reinitiating any debit returned as unauthorized is an improper reinitiation. A later debit is allowed only with a new authorization obtained after the return. It can't be arranged in advance.
Stripe reports R29 as debit_not_authorized and tells you to collect a new mandate first. Stripe also notes that disputes inside these limits are final and can't be challenged through the ACH network.
What should I do when a plan payment comes back R29?
- Stop scheduled debits to that account.
- Call your contact at the company. Ask what happened and what they need from you to approve future debits.
- Get a new written authorization from someone who can approve it, after the return.
- Agree how the returned payment will be paid, and update the schedule if dates move.
Example: a company pays for an employee's program on a 12-payment plan by corporate debit. Payment three, $1,108.33, comes back R29. Payments four to twelve wait until someone at the company signs a new authorization.
For the consumer codes, see R10 and R07.
General information, not legal advice.
- Nacha: ISO 20022 guide to mapping U.S. ACH return codes (return code names, descriptions and SEC codes)
- Nacha: differentiating unauthorized return reasons
- Nacha: RMAG Originator Essentials
- Nacha: ACH network risk and enforcement topics
- Nacha: how to calculate unauthorized return rate
- Stripe: ACH Direct Debit
- Stripe: network decline codes
Every figure on this page was checked against these sources on Oct 6, 2026. General information, not legal or tax advice.