Compliance · India
RBI Device-Lock Rules, Mapped to Loksiz
From 1 January 2027, Indian lenders may restrict a financed device only under strict conditions. This page sets out each requirement, how Loksiz supports it, and which part stays your responsibility, so your risk, legal and compliance teams can review it line by line.
The India timeline at a glance
- Day 0EMI dueReminders before and on the due date
- Days 1–30OverdueReminders only. No restriction of any kind.
- Before day 31NoticeThe borrower is told what will be restricted and when
- Days 31–60GradualSelected apps paused. Calls (in and out), SMS, SOS and work apps stay on.
- Day 61+FullThe full restriction allowed, still with incoming calls, SMS and SOS
- PaymentUnlockWithin one hour, usually seconds
- Loan closedReleaseLoksiz is removed for good
GLOBAL VS INDIA
What Applies Everywhere, and What Applies Only in India
Loksiz works in 13 countries. The RBI directions apply only to regulated lenders in India. Elsewhere, the rules come from your own policy and local law.
In every market Loksiz works in
- Reminders before and after every due date, on the device itself
- Grace periods and restriction steps that you configure
- An always-available list: calls, SMS, SOS and any apps you choose
- A restriction screen showing status, amount due and how to pay
- Automatic unlock as soon as your system confirms payment
- Automatic release when the loan is closed
- No reading of contacts, messages, call logs, photos or location
- A time-stamped audit trail of every action
Additionally, in India (RBI)
- No restriction at all until the loan is 30 days past due
- Only gradual restrictions between 31 and 60 days past due
- Full restriction only after 60 days, and outgoing calls stay on until then
- Notice to the borrower before any restriction
- A loan agreement that expressly allows restriction and sets out the procedure
- Unlock within one hour of the dues being realised
- ₹250 per hour compensation for wrongful or delayed restriction
- A grievance mechanism for unlocking delays and disputes
REQUIREMENT BY REQUIREMENT
RBI Directions vs Loksiz Controls
Fifteen requirements, what each one asks for, how Loksiz supports it, and who's responsible.
| Requirement | What RBI says | How Loksiz supports it | Who owns it |
|---|---|---|---|
| Only the financed device | Restriction is allowed only on a device bought with the lender's own loan, and only when that loan is in default. | Each device is linked to one loan ID through the API. Restrictions follow that loan's status only. | Lender (correct loan link) · Loksiz (enforcement) |
| Consent in the loan agreement | The agreement must expressly permit restriction and set out the procedure. | Loksiz is enrolled at the point of sale, alongside the signed agreement. The enrollment date is recorded in the audit trail. | Lender |
| Notice before restriction | The borrower must get due notice of the impending restriction. | Notice messages appear on the device ahead of any restriction, on the schedule you set. Each one is logged. | Lender (policy) · Loksiz (delivery and log) |
| Nothing before 30 days past due | No restriction may begin until the loan is 30 days past due. | The India policy keeps the first restriction at day 31 or later. Before that, only reminders are sent. | Loksiz (policy setting) |
| Gradual restriction after 30 days | Restrictions must be gradual and must never start as an immediate full lock. | Restriction levels step up. For example, entertainment and social apps are paused first. | Loksiz (policy setting) |
| Full restriction only after 60 days | A full restriction applies only after 60 days past due. Outgoing calls can't be blocked before then. | The full level is available only from day 61, and outgoing calls stay available until then. | Loksiz (policy setting) |
| Essential functions always on | Incoming calls, SMS and emergency SOS can never be restricted. | These are always kept available under the India policy, at every restriction level. | Loksiz |
| Work and livelihood | Restrictions can't stop the borrower from working or earning a living. | Work apps can be added to the always-available list, per lender or per customer segment. | Lender (which apps) · Loksiz (enforcement) |
| Borrower can see the status | The borrower must always be able to see the current restriction status. | The restriction screen shows the status, amount due and how to pay, and the payment screen is always reachable. | Loksiz |
| No personal data | Neither the lender nor its provider may access or use personal data such as contacts, SMS, call logs, photos or location history, for any purpose. | Loksiz does not read contacts, messages, call logs, photos or location from the device. | Loksiz and lender |
| Unlock within one hour | Restrictions must be lifted within one hour of the dues being realised. | Payments sync through the API or webhooks and trigger an automatic unlock, usually within seconds when the device is online. Commands wait for an offline device and run when it reconnects. | Lender (fast payment sync) · Loksiz (unlock) |
| Compensation for delays | ₹250 per hour for a wrongful restriction or a delayed reversal attributable to the lender, capped at the loan amount disbursed. | Payment-received and unlock-completed times are logged, so any delay can be measured and settled. | Lender (pays) · Loksiz (evidence) |
| Release after full repayment | The lender must promptly give up the locking mechanism and guide the borrower through uninstalling it. | The device is released automatically when the loan is closed, and every restriction is removed. | Lender (closure) · Loksiz (release) |
| Grievance mechanism | There must be a dedicated way to raise unlocking delays and disputes. | The audit trail gives your grievance team the full history of each device in seconds. | Lender (process) · Loksiz (records) |
| Certified mechanism | The lender or its tech vendor must hold OEM or OS-platform certification for the locking mechanism. | Loksiz uses Android Enterprise, Apple Business Manager and OEM-native integrations with itel, Infinix and TECNO. Ask us for the documentation your compliance team needs. | Lender and Loksiz |
THE RULE ENGINE
Policy Settings, India vs Other Markets
Every lender gets a policy that controls when reminders, notices, restrictions, unlocks and releases happen. Indian lenders start from a policy built around the RBI directions.
| Setting | India (RBI policy) | Other markets |
|---|---|---|
| Reminders | Before and after every due date | Your schedule |
| First restriction | Day 31 past due at the earliest, after notice | Your choice |
| Restriction levels | Gradual from day 31; full only from day 61 | Your choice |
| Always available | Incoming calls, SMS, SOS, the payment screen, work apps, and outgoing calls until day 60 | Calls, SMS, SOS and the payment screen, plus your list |
| Unlock | Automatic on payment confirmation, well inside one hour | Automatic on payment confirmation |
| Release | Automatic when the loan is closed | Automatic when the loan is closed |
| Records | Every reminder, notice, restriction, payment and unlock, time-stamped | Same |
Exact options are confirmed with your team during setup.
FOR ENGINEERING AND INFOSEC TEAMS
Evaluate the Technical Side Early
Everything your engineers and security reviewers usually ask for, in one place.
This page is a plain-language summary of the RBI directions as Loksiz understands them. It isn't legal advice, and it isn't a substitute for the official text. Read the directions on rbi.org.in, and have your legal and compliance team confirm how they apply to your entity and products. Lenders remain responsible for their own compliance. Loksiz provides the technology and records that support it.
Get the Compliance BriefQuestions Compliance Teams Ask Us
For the full borrower-facing explanation, see our RBI device-locking FAQs.
Review Loksiz With Your Compliance Team
We'll walk your risk, legal and engineering teams through the policy, the device behaviour and the audit trail.