Signal Capture
Device, behavioural, network, contact and SMS signals — ingested from your web and mobile app in real time. Drop-in SDKs, no data team required.
Lendscope unifies device, behavioural and network signals into one intelligence system, so lenders can act on a default 30–60 days before it happens.
Most platforms only react once a borrower goes days-past-due. By then the options narrow to collection calls. Lendscope catches the behavioural fingerprint of an upcoming default — engagement drops, SIM swaps, competing-lender SMS, contact-graph churn — and gives you a 30–60 day head start.
Device, behavioural, network, contact and SMS signals — ingested from your web and mobile app in real time. Drop-in SDKs, no data team required.
Ten scored conditions, weighted 8 to 30, plus up to 25 points of DPD. Who is about to default, and why — before the due date, not after it.
The band escalates and Lendscope fires a signed webhook into your stack. Nudge, urgent, critical — you keep your own WhatsApp, SMS and email vendors.
No heartbeat from your app for three days, with the due date inside the window. The borrower has not missed a payment. There is nothing for a collections team to act on yet — which is exactly the point.
An illustrative sequence, not a customer's data. The signal codes, the weights, the trigger conditions and the thresholds are exactly what riskScoringEngine.js runs in production. Nothing here is late: the whole escalation happens before the due date.
₹40,000 over 30 days. The SDK is in your app; the first snapshot lands the same evening.
Three competing-lender SMS in seven days. This condition only fires while the loan is not overdue — its whole job is to warn you early.
A fantasy or gambling app appears in the installed-app scan.
No heartbeat from the app for three days, with the due date inside the three-day window.
No heartbeat at all for five days. The borrower has most likely removed your app.
After the due date the picture only gets worse — new_device_overdue, geo_drift, comm_avoidance and up to 25 points of DPD keep pushing it toward critical. But by then you are collecting, not preventing. Note that other_lending_app_burst stops contributing the moment the loan goes overdue: it exists to fire before.
The webhook lands in your stack the moment the band changes. Who calls, on what channel and in what words stays yours — Lendscope only tells you which loan, which band, and which conditions fired.
Weights are the values in the engine. · marks a condition that can fire before the loan is overdue. Further signals are written as records by the device and SMS services and carry their own weights.
early warning for modern lending books.
Every open loan is rescored on each snapshot. Weighted conditions sum into a 0–100 number, plus up to 25 points of DPD, measured against per-tenant thresholds — nudge at 60, urgent at 75, critical at 85. A band change leaves as an HMAC-signed webhook into your own stack.
Get API keys