Five moments · one decision at each
How DeepID works
One customer’s journey. Three times fraud passes every existing check; twice the real customer is spared a code.
Five moments. One decision at each.
Selfie2 of 3
Fit your face in the oval
Good light, nothing covering your face.
Secured by DeepID
A generated face, on an emulator.
Your checks sawDeepID read
IdentityPAN record foundPAN record found
SelfieA face, matched to the photoVirtual camera detected
PhoneNot checkedAn emulator, not a phone
TypingNot checkedScripted input
FaceNot checkedSeen on 6 other accounts
BlockA generated face fed through a virtual camera, on an emulator. Nothing is bound.
VIRTUAL_CAMERA · EMULATOR · FACE_REUSEDWelcome back
Sign in with your number
+91•••• 3210
From SIM 1 in this phone
Checking with your network
Continue
Her number, her SIM, her phone.
Your checks sawDeepID read
NumberSMS code sent and typedVerified by the network, nothing typed
SIMNot checkedMatches the registered number
PhoneNot checkedSame phone as at sign-up
TypingNot checkedRhythm matches the owner
AllowThe network confirmed the number, on the phone and SIM bound at sign-up. Nothing to type.
NUMBER_VERIFIED · SIM_BOUND · KNOWN_DEVICEIs this your new phone?
Your SIM moved to a new phone. Before you carry on, we need to check it’s you.
SIM changed2 hours ago
This phoneFirst seen 4 minutes ago
Check it’s me
This isn’t me
Her face, her SIM, in a new phone.
Your checks sawDeepID read
SIMChanged 2 hours agoMoved to this phone, confirmed with one text
PhoneA new deviceNew device, 4 minutes old
FaceNot checkedMatched to the sign-up face
SessionNot checkedNo call, nobody else in the session
Step upHer face is checked against sign-up, the SIM is bound to the new phone, then limits cool off.
SIM_MOVED · NEW_DEVICE · STEP_UP_FACEAdd payee
UPI ID
name@bank
Nickname (optional)
For example, Rahul
Add payee
A payee linked to 14 other accounts.
Your checks sawDeepID read
LoginCorrect MPINHer bound phone and SIM
PayeeUPI ID valid, name matchedAccount 2 days old
NetworkNot checkedLinked to 14 accounts
InputNot checkedPayee pasted from the clipboard
Cool offA first-time payee whose account is 2 days old and receives from many unrelated senders.
FIRST_TIME_PAYEE · PAYEE_MULE_LINKED · COOL_OFFPay
RSR. Sharmar.sharma77@okbank
New payee, added 3 minutes ago
₹96,000
From Savings ••4821
“Safe account, as instructed”
Send now
A customer being told what to do.
Your checks sawDeepID read
LoginCorrect MPINHer bound phone and SIM
PhoneHer own, known phoneScreen being shared
PayeeSaved 3 minutes ago, name matchedLinked to 14 accounts
PaymentUPI PIN entered, within her limitOn a call for 41 minutes
TypingNot checkedLong pauses, as if dictated
HoldA long call with an unknown number, a shared screen and a payee linked to other accounts.
ACTIVE_CALL · SCREEN_SHARED · PAYEE_MULE_LINKEDSix actions. Not a yes or a no.
- AllowEverything holds
- WarnSomething is unusual, but the customer is in control
- Step upIdentity is uncertain
- Cool offA new device, SIM or payee
- HoldSigns of coercion or a mule payee
- BlockClear attack
Where the decision goes, without a rip and replace.
One SDK in your app, one call at each moment. The same decision reaches the systems you already run.
- Your app
- Your FRM and AML
- Case management
- Core and data platform
- SIEM and SOC
Start where you are.
Onboarding teams start at sign-up, login teams at login, fraud teams with what their own history shows. One journey, one SDK, and a proof on your own data before you commit.