Loan Recovery Harassment: Evidence and Complaint Route

Default does not authorise threats, public shaming, contact-list misuse or payment to an agent’s personal account.

What the customer or business should understand

• RBI expects regulated entities and their recovery agents to avoid intimidation, harassment and intrusion into the privacy of borrowers.
• The lender remains accountable for outsourced recovery conduct.
• Borrowers should distinguish legitimate repayment communication from threats, impersonation or unlawful third-party disclosure.
• All payments should go through the lender’s authorised channel and be supported by a receipt and loan-account update.
• Complaints should first be lodged with the regulated entity and may later be escalated through RBI CMS if eligible.

For the connected rule, example or next step, see Loan App Recovery Data Misuse: Contacts, Harassment and Evidence.

The five-point review

Practical example

How to apply the framework

Do not delete abusive communication after blocking the number. Export the complete chat and preserve call logs.

Continue addressing the underlying debt through the lender. A conduct complaint does not erase the loan.

Dispute workflow

Classify the problem before choosing the remedy

Identify the regulated entity, transaction or loan account, date, amount, contractual document and exact failure. Review lender, agent and conduct together. A failed transaction, authorised mistake, unauthorised fraud, merchant dispute, credit-report error and lawful account freeze require different remedies.

Create one written chronology

Record the event, alert, discovery, first report, complaint number, response and financial impact in date order. Attach only the documents that prove each step. Phone calls can stop urgent harm, but a written acknowledgement creates the escalation record.

Escalate to the correct authority

Start with the bank, card issuer, lender, credit institution, app or other regulated entity responsible for the service. Use cybercrime or law-enforcement channels for suspected fraud. Use RBI CMS only after the regulated entity process satisfies the Scheme’s timing or rejection condition and the issue is within Ombudsman scope.

Implementation checkpoint

Before treating the case as closed, verify the actual bank statement, loan ledger, credit report, account status or merchant refund rather than relying only on a ticket message. Record who confirmed the financial outcome, the date, remaining open amount and the next escalation deadline. This final check prevents a complaint from being marked resolved while the money, lien, overdue status or credit record remains unchanged.

Action checklist

• Identify the regulated lender.
• Request agent authorisation.
• Preserve messages and call logs.
• Pay only official channels.
• Complain to the lender in writing.
• Escalate threats or unresolved deficiency appropriately.

Evidence to keep

• Loan agreement and statement
• Agent messages and call log
• Lender authorisation response
• Payment requests and receipts
• Complaint acknowledgements

Warning signs

Finin2min takeaway