EMI Device Locker Solution
Enterprise Android Device Policy Controller (DPC) & FinTech Lock System
An enterprise-grade Android Device Policy Controller (DPC) and kiosk lockdown ecosystem designed for consumer finance institutions to prevent loan defaults through remote device management, QR enrollment, and automated kiosk locking.
Key Verified Outcomes & Results
FinTech lenders financing smartphones suffered significant non-performing asset (NPA) losses when borrowers defaulted on EMI payments. Traditional apps could be easily uninstalled, bypassed, or factory reset by delinquent borrowers.
Engineered an Android Enterprise Device Policy Controller (DPC) app operating with full Device Owner privileges. Features Knox-level tamper protection, QR-code zero-touch factory enrollment, background heartbeat telemetry, and automated kiosk locking triggered by payment status APIs.
Android DPC Architecture + Native Platform Channel + Event-Driven Microservices
The native Kotlin layer acts as the Android DeviceAdminReceiver and DevicePolicyManager controller, communicating over high-speed binary platform channels with a custom Flutter lockdown UI. The backend orchestrates commands via Redis Pub/Sub and WebSocket sockets with fallback to high-priority FCM data pushes.
1. Device Provisioning
Device scanned via enterprise QR code at retailer during unboxing; becomes Device Owner.
2. Persistent Telemetry Stream
Heartbeat worker pings backend with battery, SIM IMSI, and security posture.
3. FinTech Payment Webhook
Banking API fires overdue EMI trigger to Node.js backend when payment grace expires.
4. Instant Lockdown Execution
Device locks down into single-task mode with payment QR and support dialer.
Core Engineering Features & Capabilities
Complex Engineering Challenges & Technical Solutions
Challenge #1Bypassing Android OS Power-Saving & Doze Mode
Aggressive OEM battery savers (Xiaomi, Vivo, Samsung) killed background services, delaying lock commands.
Utilized DevicePolicyManager system-level battery optimization exemptions and structured a hybrid waking mechanism using WakeLocks, JobScheduler, and dual-channel persistent notification foreground services.
Challenge #2Offline Borrower Evasion (Airplane Mode)
Borrowers intentionally turned off Wi-Fi/data permanently to prevent lock signals from reaching the phone.
Implemented an onboard Hardware Cryptographic Countdown Timer. If the device fails to authenticate with the licensing server within a 72-hour rolling window, local DPC rules trigger lockdown automatically until network reconnect.
Challenge #3Factory Reset & Recovery Mode Tampering
Users attempted hard key recovery resets to bypass software control.
Enforced `DISALLOW_FACTORY_RESET`, `DISALLOW_SAFE_BOOT_PROMPT`, and configured FRP (Factory Reset Protection) credentials tied exclusively to enterprise Google accounts.
Complete Technology & Tooling Stack
Key Architectural Takeaways
- Android Enterprise system APIs offer unmatched device control when implemented with strict native Kotlin adherence.
- FinTech hardware security requires robust offline fallback mechanisms rather than relying solely on server pushes.