Recurring payments in lending are automated, scheduled payment collections processed on a repeating basis — weekly, bi-weekly, semi-monthly, or monthly — without requiring manual initiation for each payment cycle. Enabled by ACH debit authorization, card-on-file arrangements, or direct debit agreements, recurring payments reduce payment friction for borrowers and improve collection reliability for lenders, while carrying specific regulatory obligations around authorization, notice, and cancellation rights.
Introduction to Recurring Payments
For installment lenders, auto title lenders, and small dollar lenders, recurring payment collection is the operational backbone of the business. A lender with 5,000 active loans cannot afford to chase individual payment remittances — the economics only work when most payments are collected automatically on schedule. Recurring ACH debits, properly authorized and managed, allow lenders to collect payments at scale while minimizing the operational cost of payment processing and reducing reliance on borrower-initiated action that leads to missed payments and delinquency.
The regulatory environment governing recurring payments has grown significantly more complex over the past decade. Nacha’s Operating Rules for ACH — the primary framework governing recurring ACH debits — impose specific requirements on authorization language, revocation rights, notification obligations, and retry limits after return items. The CFPB’s Payday Lending Rule (for covered products) adds additional restrictions on payment collection attempts after two consecutive failures. State laws in some jurisdictions impose further notice requirements before recurring debits are initiated. Lenders that run recurring payment programs without systematic compliance controls face both regulatory risk and Nacha rule violations that can result in ACH network access restrictions.
How Recurring Payments Work
A recurring payment program begins with proper authorization. Under Nacha’s rules, a recurring ACH debit authorization must: (1) be in writing or be a recorded oral agreement (for telephone-authorized entries), (2) clearly authorize the specific lender (or servicer) to initiate debits from the borrower’s account, (3) specify the amount or describe how the amount will be determined, (4) specify the timing and frequency of debits, and (5) inform the borrower of their right to revoke the authorization. The authorization must be retained for two years following the last entry and must be provided to the RDFI (borrower’s bank) on request within ten business days.
Once authorized, the lender (or their payment processor) initiates ACH debit entries to the borrower’s depository account on each scheduled payment date. The entries are processed through the ACH network — either standard next-day settlement or same-day ACH for expedited processing — and the funds are credited to the lender’s account upon settlement. If a debit returns (NSF, account closed, stop payment, or other return codes), the lender’s system must handle the return appropriately: applying return fees if authorized, triggering retry logic within Nacha’s retry limits (no more than two retries on a returned item for the same dollar amount), and updating the loan’s delinquency status.
Retry logic is a particularly important area of compliance risk. Nacha’s rules prohibit re-initiating an ACH debit entry more than twice after an initial return — and for certain return codes (R07 authorization revoked, R10 customer advises not authorized), re-initiation is prohibited entirely. Lenders that automatically retry returned payments without regard for return code type or retry count history risk Nacha rule violations and potential network suspension. Systematic return code management — categorizing returns, tracking retry counts by account, and blocking re-initiation when prohibited — must be built into the payment management workflow.
Example
A consumer installment lender with 7,500 active accounts runs a recurring ACH debit program collecting payments on the 1st and 15th of each month. In a typical month, approximately 6% of ACH debits return — a mix of NSF returns (R01), account closed returns (R02), and stop payment returns (R08). The lender’s automated retry logic retries all R01 returns once after five business days, which is permissible under Nacha rules. For R08 stop payments, the system flags the account for manual review rather than retrying — since a stop payment indicates a potential authorization dispute. The lender collects approximately $2.1 million in recurring payments monthly, with the automated retry recovering an additional $87,000 from initial NSF returns — demonstrating that well-configured retry logic materially improves collection rates without manual intervention.
Borrower Notice and Cancellation Rights
Recurring payment programs carry ongoing borrower communication obligations. Nacha’s rules require that lenders notify borrowers of any changes in the debit amount (for variable-amount authorizations) at least ten business days before the debit occurs. Many lenders send pre-debit notifications as a standard practice — alerting borrowers 3-5 days before each scheduled debit, confirming the amount and date — which reduces NSF returns by giving borrowers time to fund their accounts and reduces disputes by ensuring borrowers aren’t surprised by account debits.
Borrowers have an absolute right to revoke an ACH authorization at any time. When a borrower revokes, the lender must stop initiating debits — even if the loan remains in good standing and subsequent payments are due. The lender’s right to collect the debt is separate from the right to collect via ACH; a revocation ends the ACH authorization but not the loan obligation. Lenders must have systematic processes to receive revocation notices (via phone, email, or written communication), document the revocation, stop future ACH entries, and transition the account to alternative collection methods. Failure to stop debits after revocation notice is a Nacha rule violation and potentially a UDAAP violation. See Nacha’s Operating Rules for complete authorization and retry requirements, and the CFPB’s Payday Lending Rule for payment collection restrictions on covered products.
Bottom Line
Recurring payments are the operational engine of installment and consumer lending — but without systematic authorization management, return code handling, and retry controls, they create significant compliance and financial risk. Vergent LMS includes built-in ACH recurring payment management with configurable retry logic, return code classification, same-day ACH support, and NSF automation — giving lenders the operational infrastructure to run a compliant, high-performance recurring payment program at scale.
