Home › Mobile Locking
Device Locking Infrastructure for Financed Mobile Phones
DLC and native OEM locking for lenders and retailers financing mobile phones — lock on default, release on recovery, via API or Android app.
Home › Mobile Locking
Device Locking Infrastructure for Financed Mobile Phones
DLC and native OEM locking for lenders and retailers financing mobile phones — lock on default, release on recovery, via API or Android app.
Home › Mobile Locking
Device Locking Infrastructure for Financed Mobile Phones
DLC and native OEM locking for lenders and retailers financing mobile phones — lock on default, release on recovery, via API or Android app.
Device Financing with the Right Infrastructure
Device Financing with the Right Infrastructure
A Recovery Lever After Default
Secure assets when borrowers default. Save on expensive field recovery
Auto trigger collection
Locking a device prevents the common issue of device being sold away before recovery happens
OEM-Level Enforcement
OEM level locks which cannot be bypassed. Secure collections at scale
Compliant Framework for Device Locking
We provide the approved and effective implementation path to device locking in finance use cases
Lock on default. Release on recovery. No field visit needed
Four steps from loan origination to recovery. All automated for you
Step 1: Lock activated at point of sale
Device lock is set up at the time of sale or loan origination. Optionally, add a UPI Autopay or eNACH mandate alongside to automate collections
Step 1: Lock activated at point of sale
Device lock is set up at the time of sale or loan origination. Optionally, add a UPI Autopay or eNACH mandate alongside to automate collections
Step 2: Collections run automatically
If a mandate is set up, RocketPay collects on the due date. The device stays unlocked as long as payments come in
Step 2: Collections run automatically
If a mandate is set up, RocketPay collects on the due date. The device stays unlocked as long as payments come in
Step 3: Default triggers lock
On a missed payment or failed collection, the device is locked remotely — restricting access without a field visit
Step 3: Default triggers lock
On a missed payment or failed collection, the device is locked remotely — restricting access without a field visit
Step 4: Payment releases lock
Once payment is received, the device is unlocked automatically. No manual intervention required
Step 4: Payment releases lock
Once payment is received, the device is unlocked automatically. No manual intervention required
Built for every business financing mobile devices
From NBFCs to mobile retailers — secure every financed device on your portfolio
India trusts RocketPay for Mobile Financing
Devices secured
Devices secured
NPA with device locking
NPA with device locking
Worth of financed mobiles secured
Worth of financed mobiles secured
Worth of financed mobiles secured
Deploy RocketPay Device Locking Your Way
Deploy RocketPay Device Locking Your Way
Two ways to get started — pick what fits your team and technical setup
Two ways to get started — pick what fits your team and technical setup
API & SDK
Integrate RocketPay directly into LMS/LOS. Full control over mandate creation, collection scheduling & status tracking
For LMS/LOS integrations
Webhooks and mandate status APIs
Real-time debit status and retry hooks
Works with your existing PSP
Go live in 48 hours
Android App
Quick onboarding for smaller lenders or hybrid field teams. Create mandates and track collections on the go
No API integration needed
Mandate creation from mobile
Real-time collection status
Ideal for field officers and smaller NBFCs
Go live in 48 hours
API & SDK
Integrate RocketPay directly into LMS/LOS. Full control over mandate creation, collection scheduling & status tracking
For LMS/LOS integrations
Webhooks and mandate status APIs
Real-time debit status and retry hooks
Works with your existing PSP
Go live in 48 hours
Android App
Quick onboarding for smaller lenders or hybrid field teams. Create mandates and track collections on the go
No API integration needed
Mandate creation from mobile
Real-time collection status
Ideal for field officers and smaller NBFCs
Go live in 48 hours
Got questions?
We’ve got answers.
Still have questions?
Contact us and we’ll help you out.
01
What is a mandate?
A mandate is a one-time permission your customer gives you to collect payments automatically on a scheduled date. They approve it once — through UPI Autopay or eNACH, which are NPCI's systems for automated recurring payments — and every collection after that happens without any follow-up needed from either side
02
Which banks and UPI apps support UPI AutoPay mandate registration?
Any NPCI-registered UPI app and bank supports UPI AutoPay mandate registration — including PhonePe, Google Pay, Paytm, BHIM, WhatsApp Pay, Amazon Pay, and all major bank-native apps. The mandate is registered against the customer's VPA handle. For the complete and updated list of supported banks and PSP apps, visit the official NPCI page
03
What instruments can customers use to authenticate an eNACH mandate?
The three most common eNACH mandate authentication methods are — Net Banking, Debit Card, and Aadhaar OTP. Some banks additionally support PAN-based authentication, and a few offer Customer ID-based authentication via their own portal. Available methods vary by bank. For the complete list of supported banks and their authentication options, visit the official NPCI page
04
Does a customer need to approve each collection separately?
No. A mandate requires only one-time authorisation. Once approved, all subsequent collections within the mandate happen automatically on the scheduled dates — no OTP, no PIN, no action required from either party
05
Is KYC required to start using RocketPay?
Yes — your business will need to complete a one-time KYC verification as part of onboarding. This is a standard regulatory requirement for all businesses using payment infrastructure in India. No KYC is required from your end customers — they simply authenticate the mandate, and collections run from there
06
How long does settlement take after a successful collection?
Settlement happens on T+1 — funds are credited to your account on the next business day after a successful collection. This applies to both UPI Autopay and eNACH. Settlement timing starts from when the debit is confirmed on the customer's account. You can track exact collection and settlement timestamps in real time from your RocketPay dashboard
01
What is a mandate?
A mandate is a one-time permission your customer gives you to collect payments automatically on a scheduled date. They approve it once — through UPI Autopay or eNACH, which are NPCI's systems for automated recurring payments — and every collection after that happens without any follow-up needed from either side
02
Which banks and UPI apps support UPI AutoPay mandate registration?
Any NPCI-registered UPI app and bank supports UPI AutoPay mandate registration — including PhonePe, Google Pay, Paytm, BHIM, WhatsApp Pay, Amazon Pay, and all major bank-native apps. The mandate is registered against the customer's VPA handle. For the complete and updated list of supported banks and PSP apps, visit the official NPCI page
03
What instruments can customers use to authenticate an eNACH mandate?
The three most common eNACH mandate authentication methods are — Net Banking, Debit Card, and Aadhaar OTP. Some banks additionally support PAN-based authentication, and a few offer Customer ID-based authentication via their own portal. Available methods vary by bank. For the complete list of supported banks and their authentication options, visit the official NPCI page
04
Does a customer need to approve each collection separately?
No. A mandate requires only one-time authorisation. Once approved, all subsequent collections within the mandate happen automatically on the scheduled dates — no OTP, no PIN, no action required from either party
05
Is KYC required to start using RocketPay?
Yes — your business will need to complete a one-time KYC verification as part of onboarding. This is a standard regulatory requirement for all businesses using payment infrastructure in India. No KYC is required from your end customers — they simply authenticate the mandate, and collections run from there
06
How long does settlement take after a successful collection?
Settlement happens on T+1 — funds are credited to your account on the next business day after a successful collection. This applies to both UPI Autopay and eNACH. Settlement timing starts from when the debit is confirmed on the customer's account. You can track exact collection and settlement timestamps in real time from your RocketPay dashboard
