Paybitz logo Paybitz Book a demo
Finance locker + MDM

Every financed phone stays in your control.

Paybitz enrols a device at the point of sale, links it to the loan account, reminds the customer before the EMI is missed, and restricts the phone only when it has to. Payment clears, the phone unlocks in seconds.

Android Enterprise Device Owner  ·  iOS supervised  ·  Deployed by NBFCs, banks and retail financiers

Device console — live Active
Device active

Full access. Next EMI due in 12 days.

EMI 4 / 9 · ₹1,499
2.2M+Devices enrolled per year at peak across lender programmes
15+ yrsBuilding enterprise mobility and device financing infrastructure
< 60 secFrom box to enrolled device at the retail counter
OfflineLock policy holds even when the device has no network
The lifecycle

Four states. One console.

The device moves through the same sequence every loan follows — so your collections team and your customer always see the same status.

01

Enrol at the counter

QR or zero-touch provisioning sets Paybitz as device owner before the customer walks out. No manual steps for the retailer beyond a scan.

02

Link the loan

Map IMEI to the loan account from your LMS through the API. Repayment schedule, grace period and lock policy come along with it.

03

Remind, then restrict

Graded nudges before anything is blocked: notification, full-screen reminder, then restricted mode with payment and emergency calls still open.

04

Release on payment

The payment webhook unlocks the device in seconds. At the final EMI, Paybitz removes itself and hands the phone over clean.

What you get

A finance locker and a full MDM, in one agent.

One app on the device does both jobs, so you are not stitching a collections tool onto a separate device management stack.

Finance locker

Recover the asset without losing the customer

  • Graded lock stages. Reminder, partial restriction, then full lock — each with its own trigger day.
  • Payment-linked unlock. Webhook from your collection stack releases the device automatically.
  • Offline lock policy. Time-based rules apply on device, so going off network is not an escape route.
  • Emergency access always on. Calls to emergency numbers and the payment screen stay reachable in any state.
  • Field agent codes. Time-boxed offline unlock codes for agents collecting cash where there is no connectivity.
  • Tamper resistance. Factory reset protection, uninstall block and SIM-change alerts on financed devices.
Device management

Manage the fleet after the loan closes

  • Kiosk and app control. Single-app or multi-app kiosk, allow and block lists, per-app notification permissions.
  • Remote actions. Lock, locate, wipe, reboot, reset password and push messages to one device or a whole batch.
  • Bulk enrolment. Import by IMEI range, assign policy groups by dealer, branch or product.
  • Branded lock and charging screens. Your logo and messaging on the screens the customer sees most.
  • Android and iOS. Device Owner on Android Enterprise, supervised profiles and managed app config on iOS.
  • Fleet reporting. Enrolment funnel, lock rates by dealer, compliance drift and battery or storage health.
Regulatory position

Built for the rules that take effect on 1 January 2027.

Remote locking of financed smartphones now sits inside a defined regulatory boundary. Paybitz is built around that boundary: disclosure at origination, notice before restriction, emergency access preserved, and an audit trail for every command sent to a device.

Consent captured at enrolment Notice before lock Emergency calling preserved Immutable command log
6 August 2026

Directions issued

Remote locking of financed smartphones is formally addressed, with conditions on disclosure, notice and customer access.

Now — Q4 2026

Programme readiness

Map your lock policy, consent language and escalation ladder to the conditions before the compliance date. Paybitz ships with a default policy set you can adjust per product.

1 January 2027

Effective date

Lenders running device-locking programmes need documented policy, audit trails and customer-side transparency from day one.

Integration

Talks to the systems you already run.

A REST API and signed webhooks connect Paybitz to your LOS, LMS, collections engine and payment gateway. Device state follows the loan record — no parallel spreadsheet.

REST API Signed webhooks Bulk CSV import SSO / SAML Role-based access Sandbox keys
# Restrict a device when the EMI crosses grace period
POST /v1/devices/{imei}/lock
{
  "reason": "emi_overdue",
  "loan_id": "LN-88213",
  "notice_sent_at": "2026-08-21T09:00:00+05:30",
  "allow": ["payments", "emergency_calls"]
}

# Webhook you receive when the customer pays
{ "event": "device.released", "imei": "35•••••••••••17",
  "released_in_ms": 2140 }
Deployment

Run it your way.

Cloud, hosted in India

Multi-tenant, data resident in India, rolling upgrades. Fastest way to start a pilot with one dealer network.

On-premise

Deployed inside your data centre or private cloud for lenders with internal hosting mandates. You hold the keys and the logs.

White label

Your brand on the app, the lock screens and the customer portal. Paybitz stays behind the scenes.

Get started

See it on a real device.

Tell us your portfolio size and we will run a 30-minute walkthrough on a live handset — enrolment, lock, and release, end to end.

Emailsales@paybitz.com
Phone+91 00000 00000
OfficeGothi Tech LLP, Ahmedabad, Gujarat, India

We reply within one business day.