January 2, 2026
For several years, many device financing programs quietly relied on enterprise-grade Mobile Device Management (MDM) solutions to control, lock, and manage consumer devices. While this approach worked initially, it was never designed for consumer device financing, and today, it is no longer valid.
Many NBFCs, financiers, telecom operators, device retailers and pay-as-you-go (PAYG) providers are now facing unexpected device locking behaviour, enrolment failures, and policy enforcement risks, primarily due to the strict enforcement of Android Enterprise (AE) policies. This blog explains what changed, why it matters, and what it means for businesses continuing to use enterprise MDM for device financing.
Organisations operating BNPL (buy now, pay later), PAYG (Pay-as-you-go), Retailers, and NBFC (Non-banking financial companies)-backed smartphone financing models are facing challenges with the current Enterprise MDM-based solutions for device financing.
Under Android Enterprise’s permissible usage policy:
- QR-based enrolment and zero-touch provisioning are meant only for enterprise use cases.
- Android Management API (AMAPI) and Device Policy Manager (DPM) APIs must not be used for consumer device financing.
Locking or restricting consumer devices for loan enforcement violates AE policy. In simple terms, device financing is a non permissible Android Enterprise use case.
The Android Enterprise team has already issued notices to companies that were:
- Using Android Enterprise APIs for financing-related activities
- Leveraging AMAPI or DPM to lock consumer-owned devices
- Enrolling financed devices through QR provisioning
These organisations were explicitly instructed to cease all device financing activities using Android Enterprise APIs. This enforcement impacts not only solution providers but also their customers, partners, and end users. Relying on enterprise MDM for consumer financing is no longer a workaround; it is a liability.
Unexpected issues with financed devices:
1. New Device Enrolment Failure on Android
The most common reason device financing solutions don’t work as expected is that the locking application is blocked or restricted by Android Protect (Google Play Protect), causing new devices to fail to enrol during activation. This typically occurs when:
- QR-based provisioning is used for consumer-owned financed devices
- Android Enterprise APIs are applied beyond their permissible enterprise scope
- Google restricts API access due to non-compliance
When enrolment fails, devices cannot be controlled or locked, directly impacting onboarding timelines and customer experience.
2. Random or Unexpected Unlocking of Devices
One of the most critical risks for any financier is loss of device control. Many organisations report issues such as:
Financed phone unlocking automatically
This happens when:
- Android Enterprise policies are revoked
- API access is limited or suspended
- Device Policy Manager enforcement becomes unstable
For lenders, this results in loss of control, revenue leakage, and increased credit risk.
The Core Issue:
Android Enterprise is NOT designed for Device Financing. Android Enterprise is built to manage work devices, corporate-owned devices, and work profiles, not consumer financing.
Other Expected Issues:
- Devices are unexpectedly getting released
- Loss of control after updates
What This Means for NBFCs, Financiers, and PAYG Providers – Business Impact?
As enforcement of the Android Enterprise QR enrolment policy tightens, many existing implementations are becoming unstable or non-functional. Organisations are increasingly reporting that their device financing solution is not working as expected.
From a business impact perspective, the risks are significant and immediate. Device financing programs built on non-compliant architectures face heightened operational risk, as enforcement failures, enrolment breakdowns, and unpredictable device behaviour disrupt day-to-day operations. More critically, financial capital is directly at risk, with devices unlocking without payment resulting in tangible financial losses across NBFC, PAYG, and BNPL portfolios.
In such cases, Google cannot provide assistance or remediation because these implementations violate Android Enterprise’s permissible usage policies. This leaves the financier with limited recourse once access is restricted or enforcement is disabled.
The Solution:
To operate sustainably, financiers must move away from Enterprise MDM and adopt a solution that is:
- Google certified device financing solution, which doesn’t use QR enrolment or enterprise zero-touch enrolment
Compliant Solution: Google Certified Device Financing Solution.
There are very few organisations authorised to deliver Google-certified solutions, and our offering is designed explicitly for compliant device financing. This compliant approach ensures consistent, predictable device control, enables a secure, policy-aligned setup, and significantly minimises operational and financial risk. Connect with our experts to transition to a compliant device financing solution built for long-term stability and scalability.