One SDK for Android, iOS and web
Device intelligence Know every phone, every session.
Whether it has been tampered with, and whether someone else is driving it. One SDK, read from sign-up to the payment.
Why it matters.
Almost every attack leaves a trace on the phone. Read it, and the rest of the session makes sense.
One phone, one identity
A device ID that survives reinstall and factory reset, so the same phone is recognised when the app comes back.
Tampering, every session
Rooting, jailbreaks, emulators, hooking frameworks and cloned apps, checked from sign-up onward.
Someone else driving, seen
Remote-access and screen-sharing tools are read while a payee is added or money moves, with malware and overlay signals.
Weighed in one decision
The device meets the SIM, the behaviour and the payee, so a phone known for 412 days and a shared screen are weighed together.
Four layers of device intelligence, one SDK.
Read on the phone in every session, and turned into the rules your policy runs.
A device ID that survives reinstall and factory reset, bound to the account at sign-up. One phone behind many accounts shows the moment it signs up again.
SIM and device bindingRooted and jailbroken phones, emulators, hooking frameworks and cloned apps, read in every session and refused before any route runs.
Remote-access tools and a screen being shared while a payee is added or money moves, with malware and overlay signals, so a coached payment holds.
Scam signalsA virtual camera feeding the selfie or the video call, read with emulators and VPN use, so an injected face never reaches the match.
Liveness and face match
Device intelligence adapts to every risk, wherever your customers are.
Onboarding fraud
Read the phone before an account is opened on it.
Emulators and rooted phones: the customer sees “Can’t continue. We couldn’t verify this session. Your money is safe.” Your console records Block, for Emulator, with EMULATOR.
Many accounts on one phone: the customer sees “Confirm it’s you. Confirm it’s you with a quick face check.” Your console records Step up, for Phone linked to other accounts, with SHARED_DEVICE.
Injected selfies: the customer sees “Can’t continue. We couldn’t verify this session. Your money is safe.” Your console records Block, for Virtual camera, with VIRTUAL_CAMERA.
Account takeover
Tell the owner’s phone from a stranger’s, at every login.
A phone not seen before: the customer sees “Limit for now. You can send up to ₹10,000 from this phone now. You get the full limit in 12 hours.” Your console records Cool off, for New device, with NEW_DEVICE and COOL_OFF.
A hooked or cloned app: the customer sees “Can’t continue. We couldn’t verify this session. Your money is safe.” Your console records Block, for Tampered app, with DEVICE_TAMPERED.
A new phone, checked first: the customer sees “Confirm it’s you. Confirm it’s you with a quick face check.” Your console records Step up, for New device, with NEW_DEVICE and STEP_UP_FACE.
Scams and remote control
See when someone else is in the session while money moves.
payment.initiateYour console
- Signal
- Screen shared, call active
- Decision
- Hold
- Reasons
SCREEN_SHARED ACTIVE_CALL
A screen being shared on a call: the customer sees “Payment paused. Payment paused. Your money hasn’t left your account. We’ll call you on +91 •••• 3210.” Your console records Hold, for Screen shared, call active, with SCREEN_SHARED and ACTIVE_CALL.
login.attemptYour console
- Signal
- Remote access
- Decision
- Step up
- Reasons
REMOTE_ACCESS
A remote-access app at sign-in: the customer sees “Confirm it’s you. Someone may be able to see your screen. Stop sharing it, then confirm it’s you.” Your console records Step up, for Remote access, with REMOTE_ACCESS.
payee.addYour console
- Signal
- Overlay signal
- Decision
- Hold
- Reasons
DEVICE_TAMPERED
Malware and overlays: the customer sees “Payment paused. Payment paused. Your money hasn’t left your account. We’ll call you on +91 •••• 3210.” Your console records Hold, for Overlay signal, with DEVICE_TAMPERED.
Mule rings
Follow phones across accounts to the people running them.
payee.addYour console
- Signal
- Phone shared across senders
- Decision
- Hold
- Reasons
SHARED_DEVICE PAYEE_MULE_LINKED
Many senders, one phone: the customer sees “Payment paused. Payment paused. Your money hasn’t left your account. We’ll call you on +91 •••• 3210.” Your console records Hold, for Phone shared across senders, with SHARED_DEVICE and PAYEE_MULE_LINKED.
payment.initiateYour console
- Signal
- Sender across many phones
- Decision
- Hold
- Reasons
SHARED_DEVICE
One sender, many phones: the customer sees “Payment paused. Payment paused. Your money hasn’t left your account. We’ll call you on +91 •••• 3210.” Your console records Hold, for Sender across many phones, with SHARED_DEVICE.
signup.startYour console
- Signal
- Emulator, shared device
- Decision
- Block
- Reasons
EMULATOR SHARED_DEVICE
Device farms: the customer sees “Can’t continue. We couldn’t verify this session. Your money is safe.” Your console records Block, for Emulator, shared device, with EMULATOR and SHARED_DEVICE.
One SDK, every module.
Device intelligence is read by everything else DeepID decides.
SIM and device binding
The account bound to the customer’s own phone and SIM.
Silent network verification
One-tap login: the mobile network confirms the number silently, then the SIM, Aadhaar or a code.
Liveness and face match
A live person, a real camera, the right face.
Scam signals
The call and the shared screen, while money moves.
Payee and mule graph
Where the money is going, before it goes.
One decision, with reasons
Allow to block, sent to the app and the FRM.
Read next.
Injection attacks
How a fake camera feed reaches a selfie check, and how the device gives it away.
Scam interventions
What to do when the customer is the one being played.
SIM and device binding
What each one ties down, and why banks use both.
Questions banks ask.
Does the device ID survive a reinstall?
Yes. It is built to persist across reinstalls and factory resets, so the same phone is recognised when the app comes back.
Is a device ID personal data?
In India, under the Digital Personal Data Protection Act, 2023, it can be. What is collected, where it is held and for how long are agreed with your security team before a pilot, and set out in the security pack.
Can it see a screen-sharing app during a payment?
Yes. Screen sharing and remote-control tools are read while a payee is added or a payment made, and the reading reaches the decision with the call and the payee.
Will a rooted phone be refused?
That is your policy. The signal comes back as risk; many banks block at sign-up and step up at login. Nothing is refused on the device alone unless your policy says so.
Try one-tap login on your own number.
See the network confirm your number with nothing to type, and the next check take over when it can’t. Then plan a shadow proof on one journey, measured on your own traffic.