RecTym solutions
EMI Lock for NBFCs and Lenders
Evaluate RecTym device enrollment and remote management alongside your lender-controlled repayment and borrower-support processes. Start with a defined pilot and verify each operational requirement before rollout.
Across a retail network, the difficult cases are often mismatched customer records, delayed payment updates and unresolved release requests. Agree who owns each step between the lender, retail partner and device-management operator.
Customer records
Keep the financed customer and device connected.
Installment tracking
Review the repayment schedule and payment status.
Payment reminders
Discuss available reminder channels during onboarding.
Remote management
Manage authorized lock and unlock actions on supported enrolled devices.
Make ownership of exceptions explicit
Use this checklist when evaluating the workflow with your team. Confirm the behavior on your phone models and establish responsibility for each step.
- check_circleSpecify which system is the authoritative payment ledger.
- check_circleApprove the staff process for restrictions, disputes and authorized release.
- check_circleTest partner handoffs and device compatibility before expanding a pilot.
- check_circleRequest demonstrations of reporting, access controls and integrations you require.
Define the lender–retailer–device relationship
| Function | Responsible party to name | Evidence to retain |
|---|---|---|
| Financing account | Lender account owner | Account reference and authoritative payment state. |
| Enrollment | Authorized retail operator | Correct account-to-device match and enrollment outcome. |
| Dispute | Lender support / reconciliation owner | Payment evidence, decision and next action. |
| Device action | Authorized device operator | Reason, request and confirmed result. |
| Completion | Account owner and device operator | Settlement confirmation and release outcome. |
Make portfolio exceptions visible
A portfolio review should distinguish overdue accounts, unresolved payment references and device actions waiting for confirmation. Combining them into a single “locked” count hides the reason a case is still open.
Ask for demonstrations of the reports, exports, operator permissions and event history your controls require. These are procurement requirements, not a claim that every function or integration is available in RecTym.
- Test an account correction passed from the lender to a retailer.
- Test the same customer having more than one device record.
- Test a release request after the last installment.
- Agree who follows up when a device action has not completed.
Judge the pilot by reconciled outcomes
Review unmatched records, unresolved release requests, duplicate contacts and time to confirmed resolution. Record which phone models and partner processes were tested. Avoid treating more commands sent as evidence of better collections.
Expand after the lender and partners can explain and reproduce the process. Have the responsible advisers assess financing and device-management requirements; product selection is not regulatory approval.
Common Questions
Can we use our existing lender ledger?expand_more
What reporting should we request?expand_more
Is RecTym RBI-approved?expand_more
Related Resources
Browse all nbfc & lenders resourcesReview your workflow with RecTym
Bring a sample repayment schedule and the phone models you finance to a product walkthrough.