Returned Payment Fees on Loans: State Caps and Retry Limits
How to set a returned payment fee on a loan by state rules without stacking fees on ACH retries, plus disclosures and waivers that hold up.
On this page 6 sections
Key takeaways
- Charge one returned payment fee per failed scheduled payment, however many times your system retries it.
- Fee caps sit in product-specific statutes, so look them up by borrower state and loan product together, not by state alone.
- Nacha's reinitiation rules and card network reattempt limits each restrict your retry schedule, and the schedule has to fit inside both.
- The fee your loan management system posts has to match the signed agreement for every state and product, and a quarterly sample test is how you prove it does.
A returned payment fee on a loan is set by the borrower's state, and the limit is tied to the loan product as well as the state. Your processor doesn't set it. State lending statutes and license conditions decide whether the fee is allowed and how large it is. The safe baseline is one fee per failed scheduled payment, at or below the cap for that product in the borrower's state. Write it into the signed agreement, and keep your retry schedule from multiplying it.
The fee amount is only half the problem. Retries carry their own limits: Nacha's Operating Rules for ACH debits and card network rules for cards. A lender can set a legal fee and still get into trouble by charging it on every attempt or by retrying more often than those rules allow.
This is general information, not legal advice. Fee caps and lending laws change, so confirm your fee schedule with counsel licensed in the states where you lend.
Returned Payment Fees vs. Late Fees on Loans
A returned payment fee, also called an NSF (non-sufficient funds) fee, is what a lender charges when a payment is presented and comes back unpaid. The usual trigger is an ACH debit returned for insufficient funds. A bounced check counts too.
A late fee has a different trigger. It applies because the payment wasn't received by the due date plus any grace period in the contract or statute.
One bad day sets off both. A borrower's ACH payment bounces on the due date, the grace period runs out, and that installment now qualifies for two fees. State lending statutes treat them as separate charges with separate caps, and some states bar charging both for the same missed payment. Your servicing system has to know which rule applies before it posts the second fee.
There is also a fee the lender never sees: the one the borrower's bank charges for the bounced debit. You don't control it, but the borrower experiences your fee and the bank's fee as one bad week. That combined cost drives complaints, so retry strategy matters as much as the fee amount. For apps that collect small repayments, our guide on collecting cash advance repayments without overdrafts covers timing tactics that cut returns before they happen.
Card payments work differently. A declined debit or credit card authorization is not a returned payment, because no money moved and came back. Whether your contract and state law allow any charge for a declined card attempt is a separate question, and plenty of lenders charge nothing.
How a Loan Returned Payment Fee Limit Varies by State
For licensed consumer lenders, state law sets the limits on returned payment fees, and those limits are spread across several statutes. A state with separate payday and installment laws writes fee language into each. The NSF fee on an installment loan and the late fee cap on a payday loan in the same state are two different lookups.
Here is where the rules live and what to check in each.
| Source of the rule | What it governs | What to check |
|---|---|---|
| Payday or deferred deposit statute | Short-term loans repaid from a check or ACH debit | Whether any NSF fee is allowed; limits on how many per loan |
| Installment or small loan act | Longer-term consumer loans | Cap per returned item; whether a late fee also applies |
| Title loan statute | Loans secured by a vehicle | Fee caps; whether fees can be added to principal |
| General returned-check statute | Bounced checks and similar items | Whether your lending license law displaces it |
| License conditions and regulator guidance | How the regulator reads the statute | Exam findings and published enforcement actions on fees |
The same patterns show up from state to state:
- A flat dollar cap per returned item.
- A limit on how many times the fee applies, counted per loan or per returned item.
- A requirement that the fee appear in the loan agreement before it is charged.
- Tighter NSF limits in short-term lending statutes than in installment laws, in some states a single fee over the life of the loan.
Licensing follows where the borrower lives, so the borrower's state is the first one to check. Tribal and bank-partnership models raise their own choice-of-law questions. Our article on the lender licenses processors ask for explains how underwriters look at those structures.
Build the fee schedule as a table in your loan management system keyed by borrower state and loan product, not as one global setting. Name an owner who updates it whenever a state amends its lending law. For a broader view of state-level oversight, see our merchant compliance plan for stepped-up state enforcement.
The Stacked-Fee Problem With Repeated Retries
Stacking happens when a servicing system charges a fresh fee every time a retry fails. Each fee sits under the cap on its own, while the total for one missed payment lands well beyond what the statute allows or the borrower expected.
Take an illustrative case. These assumptions are hypothetical and not drawn from any one state's law:
- One scheduled installment
- A returned payment fee stated in the loan contract (the "contract fee")
- A state rule allowing one returned payment fee per scheduled payment
- The payment presented on the due date and retried twice, with all three attempts returned for insufficient funds
A system that charges per return posts the contract fee three times. A system that charges per scheduled payment posts it once. The overcharge is two contract fees on a single installment. Any late fee is a separate question, and it applies only where state law permits both charges on the same installment.
To size your own exposure, count the extra fees posted per affected installment, multiply by your contract fee, then multiply by the number of affected installments in the lookback period your regulator examines. That total is the starting point for any refund an examiner orders, before penalties. The borrower has also paid their own bank for each failed attempt, and that cost will be in their complaint.
Stacking hurts your payments setup too. Every failed retry adds another ACH return to your record, and your bank watches return rates. Our guide to Nacha return rate limits for lenders covers how those reviews work.
The fix is configuration. Tie the fee to the scheduled payment ID, not the transaction ID, so a retry succeeds or fails without generating a new charge.
Failed ACH Retries and Card Declines Have Their Own Limits
Nacha's Operating Rules govern when a returned ACH debit is sent again, which the rules call reinitiation. They restrict which return reasons qualify, cap the number of retries and the time window for them, and prohibit workarounds built to evade those limits. Get the current requirements from the Operating Rules or from your ODFI, the bank that sends your ACH entries. If your servicing software has a feature that changes amounts or relabels retries to get around a limit, turn it off.
Returns that point to a problem with the account itself stay out of the retry queue. A closed account or a debit the borrower says they never authorized needs a conversation with the borrower before anything else is sent. Checking accounts before the first debit cuts these returns, which is the subject of our piece on Nacha account validation for borrower bank accounts.
Federal rules also restrict repeated withdrawal attempts on certain covered loans. Ask counsel whether they reach your products.
Card payments run on network rules, not Nacha's. The card networks restrict repeated reattempts of declined transactions and penalize merchants who exceed their limits. Certain issuer responses tell you outright not to try again, and your gateway should read those codes and stop. Whether you take cards for loan payments at all is a separate question, covered in our guide to accepting credit cards for loan payments.
A retry design that fits inside all of these limits follows four rules. Retry only returns eligible for it. Time each retry to the borrower's payday rather than the next business day, because a retry into an empty account produces another return. Stop at the limit. And charge one fee per scheduled payment, no matter how many attempts it took.
Disclosing Fees so They Hold Up
A fee that isn't clearly disclosed is hard to defend, even when the amount is legal. A complete disclosure covers five points:
- Amount. The exact figure, or the figure for each state if you lend in several.
- Trigger. Which events cause the fee: any unpaid return, or insufficient funds only.
- Frequency. A statement that the fee is charged once per scheduled payment, including when the payment is retried.
- Late fee interaction. Whether a late fee also applies to the same installment.
- Borrower's bank. A note that their bank's returned-item fee is separate from yours.
Put this in the loan agreement and repeat it in the ACH authorization. The authorization also describes your retry practice: how many times you retry and on what schedule. Borrowers who weren't told about retries are the ones who call a later debit unauthorized. Those disputes cost money to fight, as our guide to winning "I didn't authorize this" loan chargebacks explains.
Check that any federally required disclosures about late or returned payment charges match your agreement. Then test the control lenders skip most: whether your system charges what the document says. Each quarter, pull a sample of returned payments and compare the posted fees against the signed agreement for that borrower's state and product. A mismatch between agreement and system is the first gap a regulator or plaintiff's attorney looks for.
Waiver Policies That Cut Complaints
A written waiver policy lets your support team settle a complaint before it reaches a regulator. It also gives you a documented answer when an examiner asks how fees are applied and when they're forgiven.
Four waiver rules cover most situations:
- First return on a good account. Waive the first returned payment fee for a borrower in good standing.
- Lender error. Waive automatically when you caused the return, such as a debit sent on the wrong date or after the borrower revoked authorization.
- Quick cure. Waive when the borrower pays the missed installment by another method within a set number of days.
- Documented hardship. Grant hardship waivers for documented events, with an annual cap per borrower.
Let frontline staff apply the first two without escalation, and log every waiver with a reason code. Then watch the trend. If returned payment fee income keeps rising while waivers and complaints rise with it, your retry timing or your underwriting is producing failures that fees won't fix.
If you're reviewing your payment setup more broadly, MannyPay offers high-risk processing and payment gateways, with approval subject to underwriting. You can request a free quote, and a MannyPay specialist responds within one business day.
Start this week with an audit. Pull every returned payment from the last quarter and count the fees charged per scheduled payment. Check each against the statute for that borrower's state and loan product. Any installment carrying more than one returned payment fee needs review, and a refund wherever the cap was exceeded, before an examiner finds it.
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.


