Financed Phone Operations

EMI Lock & Device Financing
Software for
Retailers and Lenders

Enroll financed phones, track installments and send payment reminders from one dashboard. Manage remote device locking when payments become overdue.

Get Startedarrow_forward

verifiedRemote Device ManagementboltConfirm Setup RequirementsshieldSupported Android Models

lock

Device Locked

Contact your retailer for account review

Protected by

Rectym

Phone Status

Due Date

phone_android

4 paid · 1 overdue

check

warning

notifications_active

Review the agreed installment

Step 1

About RecTym

What is RecTym?

RecTym helps mobile shops manage financed phones and installment records. Verify received payments, reconcile the account and authorize any supported device action separately.

verified_user

Customer & Device Records

shield

Google FRP Protection

phone_android

Device Enrollment

support_agent

Confirm Support Coverage

dashboard

Retailer Dashboard

Illustrative

Total Devices

Active

Overdue

smartphone

Samsung A55 · Rashid

Paid

smartphone

Infinix 9 · Zubair

Overdue

smartphone

Redmi Note 13 · Fatima

Locked

smartphone

Vivo Y28 · Hina

Paid

What You Get

Features That Protect
Your Installment Sales

lock

Lock/Unlock Remotely

notifications_active

Installment Alert

location_on

Track Live Location

apps

Lock/Unlock Specific Apps

usb

USB Lock

bolt

Device Enrollment

power_settings_new

Reboot Device

wifi_off

Control Network Connectivity

Stand out with a safer, more professional installment experience

Simple Steps

How It Works

From adding a new phone to collecting the last installment — everything in one easy place.

Customer's New Device

touch_app

Tap to Begin

sync_alt

Retailer App

dashboard

Dashboard

qr_code_scannerScan QR Code

boltConfirm Setup

downloadComplete Enrollment

person_addAdd or Link Customer

event_availableSet the Plan

Confirm enrollment, account responsibilities and final release before rollout.

Turn financed-phone sales into a manageable daily process

When a shop sells a handset on installments, the work continues after the customer leaves the counter. Someone needs to keep the payment schedule accurate, record receipts, follow up on overdue accounts and resolve mistakes. RecTym brings customer and device records, installment tracking, reminders and authorized device management into the same operating conversation. Begin with those handoffs rather than treating a lock command as the whole system.

A financed phone should remain connected to the correct account throughout that process. Before any device decision, staff need to distinguish an unpaid installment from an unmatched receipt, a disputed amount or an update waiting for approval. A clear support route gives the customer somewhere to report that problem. The aim is a workflow the retailer, lender and device operator can explain and run consistently.

Choose the workflow for your team

Mobile retailers

At the counter, start with the customer, handset and agreed schedule. Staff should know how to explain enrollment, record a receipt and hand an unresolved account to the next shift. Evaluate the process on the Android models you actually sell, with the people who will use it on a busy day.

NBFCs and lenders

For a lender, device operations need a clear relationship with payment reconciliation and customer support. Agree who checks the receipt evidence, approves an action and resolves a dispute. Software does not replace underwriting, funding decisions or the lending entity’s responsibilities; evaluate each part of the arrangement separately.

Distributors

A network needs an explicit handoff between each retailer and the team supporting it. Identify the account owner and the person who handles a delayed unlock or final release. Confirm permissions, reporting and any branding requirements in a demonstration and written terms, rather than assuming every network feature is included.

Enterprise teams

A larger rollout needs a documented process for exceptions across sales, finance, support and administration. Map the receipt sources, approval steps and export requirements before a pilot. Expand only after representative teams can complete the workflow and agree how unresolved cases reach the responsible operator.

From enrollment to the final installment

Prepare the sale. Confirm the supported model, Android version and setup state. Connect the correct customer and handset to the agreed installment schedule. Explain the management process and customer support contact before handover, and use only the supported enrollment instructions for that configuration.
Keep receipts usable. Assign responsibility for counter payments and transfers received elsewhere. Record the amount and reference, review unmatched receipts and make shift handovers clear. Test partial payments and duplicate entries so an account correction is handled deliberately rather than improvised during a customer complaint.
Review before escalation. Check the account, due date and payment evidence before deciding on an authorized device action. Confirm how the proposed setup handles reminders, connectivity and pending commands. A record saying an action was requested is different from confirmation of the outcome on the phone.
Close the account properly. After final settlement, arrange the supported release process and confirm completion. Keep a reference the customer and support team can use if the outcome is still pending. Review export and exit responsibilities before committing the portfolio, not only when you want to change providers.

Review the full operating workflow

Prepare for your market

Use a country guide to prepare questions about payment evidence, billing currency and customer communication. Country-specific content does not establish a local office, a translated application or a commercial package available to every business. Confirm current availability, supported devices and language requirements with the team before promising a capability to customers.

India: INR quote requirements

Prepare questions about cash and transfer reconciliation, shop handovers and lender responsibilities. Request a written quote and a demonstration that fits the way your team collects installments.

Pakistan: PKR quote requirements

Prepare questions about qist records, receipt matching and Urdu/English communication requirements. Request a written quote and a demonstration that fits the way your team collects installments.

Bangladesh: BDT quote requirements

Prepare questions about counter and off-counter receipts, Bangla communication and account ownership. Request a written quote and a demonstration that fits the way your team collects installments.

UAE: AED quote requirements

Prepare questions about sales-to-finance handovers, Arabic/English requirements and commercial scope. Request a written quote and a demonstration that fits the way your team collects installments.

Nigeria: NGN quote requirements

Prepare questions about transfer evidence, connectivity-dependent commands and local support requirements. Request a written quote and a demonstration that fits the way your team collects installments.

Philippines: PHP quote requirements

Prepare questions about payment-channel confirmations, Filipino/English explanations and final release. Request a written quote and a demonstration that fits the way your team collects installments.

Compare a complete quote

Compare enrollment or device charges, recurring fees, reminder messages, onboarding, support and applicable taxes over the same period. Ask what happens after a failed enrollment, replacement or final release. Use measured additional repayments and staff effort when assessing value; an outstanding balance is not cash recovered. Our device-count bands organize quote enquiries and do not establish a minimum purchase or numeric starting rate.

Request pricing for your device count

Build a partner relationship with clear responsibilities

If you support a retail network, describe your country, expected device volume and proposed onboarding role. Discuss who supports each shop, how customer disputes are escalated and which party owns the account record. Any commission, revenue share or territory arrangement needs written confirmation. The partner enquiry begins that conversation without promising an appointment, earnings or a funding relationship.

Discuss a RecTym partnership

Questions before your first demo

Who is RecTym for?

RecTym is presented for mobile retailers, distributors and lending businesses managing financed phones. Start with the responsibilities of your team, then evaluate enrollment, installment records, reminders and authorized device management against that operating process.

Does device software provide customer financing?

A software workflow does not establish a funding agreement or credit approval. Decide who finances the sale, checks eligibility and carries the credit risk separately from your device-management purchase.

What should I verify before enrolling customer devices?

Confirm supported phone models, setup requirements, customer explanations, receipt handling and the authorized release process. Use store-owned test devices and fictional accounts to evaluate the workflow before expanding to a live portfolio.

How can I compare costs?

Request quotes for the same device count and period, with currency, enrollment charges, recurring fees, messaging, support and taxes stated separately. Treat omitted costs as unknown. Confirm current commercial terms with the team.

Read the full retailer and lender FAQ

Evidence you can evaluate

Ask for a demonstration on your devices and written commercial terms. Our verified operating metrics will appear here when available.

WhatsApp and SMS payment reminders

Make payment follow-up part of your installment workflow. Review reminder options alongside due dates and customer records, and confirm channel availability during onboarding.

Explore installment collection and reminders

Google Factory Reset Protection (FRP)

RecTym supports Google Factory Reset Protection (FRP) on compatible enrolled Android devices. FRP helps prevent unauthorized use after an untrusted factory reset by requiring verification during setup. Availability depends on the device and enrollment configuration; confirm supported behavior in a demo.

Explore Google FRP and device protection Read the Google FRP retailer guide

Find your workflow