Fraud prevention for lenders and NBFCs
You decide in minutes and see the loss months later. The applications that default first share a face, a device or a payout account with another, and nothing at the desk shows it.
Block
BLOCK · face reused · emulator · scripted timing · payout account shared- Your customer sees
- We can’t continue with this application in the app. If you think this is a mistake, contact us and we’ll look at it with you.
- Your FRM receives
- FACE_REUSEDEMULATORSCRIPTED_TIMINGACCOUNT_SHARED
What lenders face now.
- Generated documents and faces build applicants who pass KYC.
- The same person, phone or face applies at many lenders within days, and the bureau has not caught up.
- Losses arrive months later, as first-payment default.
Across the customer journey.
Where each attack appears for lenders, what DeepID reads at that moment and the action it returns. Each moment is checked against what the one before it bound.
| Moment | The attack | What DeepID does | Decision |
|---|---|---|---|
| Application | Stacked applications and synthetic identities | A face already seen under another name, many applications on one device, and a form filled by a script. | Cool off or block |
| Verification | Edited documents and borrowed identities | eKYC and the document checked at the source, the live face matched to the portrait and searched across your applicants. | Step up |
| Disbursal | Payout to a mule or a ring account | The payout account verified against the name on it and scored against the mule graph before the money leaves. | Hold |
| Servicing | Account handover and collection fraud | A change of device or behaviour after disbursal, and a repayment account change read as a new-phone event. | Step up, then cool off |
Where to start.
The journey most at risk: application and disbursal. Start at application, where eKYC, the document and the live face are checked at the source and the phone is bound, so that disbursal has something to check against.
- 1Sign-upeKYC, the document and a live face, bound to the phone.
- 2Loan stackingThe synthetic ring, and the cool-off or block before disbursal.
- 3Video KYC deepfakesThe video KYC call, with the camera read below the picture.
- 4Assisted channel fraudThe customer confirms on her own phone before an assisted action.
Your free first analysis.
A free retrospective on 30 to 90 days of applications, disbursals and early repayment.
What it shows. The defaulted loans that shared a face, device or payout account with another application, and whether that link was visible before disbursal. No figure is published for this; you count it on your own data, against what you see today.
Use cases for lenders.
Each shows how the attack unfolds, what your checks saw at each step, what DeepID read and the decision it returned.
Loan stacking
Catch stacked and synthetic applications before disbursal.Cool off or blockVideo KYC deepfakes
A live person, in front of a real camera, on every video KYC call.Step up, hold or blockAssisted channels
Prove the customer is there, on her own phone, before an assisted action.Step up, or holdAccount takeover
Protect the account through recovery and the hours after.Step up, then cool offInsider fraud
Hold the takeover that starts with a contact change made from the inside.Step up, then hold
Rules that apply.
India first. Each rule is dated and sourced on its market page, and the rule map covers the six other markets.
- RBI Authentication Mechanisms for Digital Payment Transactions Directions, 2025In force 1 Apr 2026 (RBI (Press release: directions on authentication mechanisms for digital payment transactions, opens in a new tab), Sep 2025; RBI (Authentication Mechanisms for Digital Payment Transactions Directions, 2025, opens in a new tab), Sep 2025)
- SIM binding: UPI apps today, messaging apps nextIssued Nov 2025 · deadline reported as 31 Dec 2026 (The Hacker News (India orders messaging apps to work only with active SIM cards, opens in a new tab), Dec 2025, press report; Angel One (DoT extends SIM-binding deadline for WhatsApp, Telegram and Signal till year end, opens in a new tab), 2026, press report; NPCI (UPI user onboarding: product overview, opens in a new tab), as of Oct 2026)
- MuleHunter.AI and the I4C Suspect RegistryLive since Dec 2024 · MoU May 2026 (Outlook Business (Finance Ministry asks banks to use MuleHunter.AI to check digital fraud, opens in a new tab), Dec 2024, press report)
- Limiting customer liability in unauthorised electronic transactionsSince Jul 2017 (RBI (Customer protection: limiting liability of customers in unauthorised electronic banking transactions, opens in a new tab), Jul 2017)
DeepID supports compliance with these rules. It never claims to guarantee it.
The modules these use cases read with.
Open a module to see what it reads and the reasons it sends with each decision.
See DeepID on a real phone.
We show your fraud, security and engineering leads how DeepID would run your sign-up, login or payment journey, then plan a pilot on your own traffic.