Nine guides to the rules now arriving
RBI’s directions, SIM binding, scam interventions, injection attacks and liability by market. Every fact carries its publisher and period.
All guides
Everything a fraud, risk or technology team needs to judge DeepID before a first call. The rules, dated and sourced; the attacks, step by step; what the SDK does and what is agreed first; and how a pilot is measured on your own traffic.
A compliance lead starts with the rule map and the guides. A fraud lead starts with the use cases and the retrospective. An engineer starts with the developer docs and the security review. Each page says what it proves, and nothing on them is a success rate.
RBI’s directions, SIM binding, scam interventions, injection attacks and liability by market. Every fact carries its publisher and period.
All guides
Six controls across India, Singapore, Malaysia, the Philippines, Australia, the UAE and Saudi Arabia, with each rule’s date, status and source.
The rule map
Try it on your own number, a free retrospective on your own history, a shadow proof, then one journey live. Criteria agreed in writing first.
How a pilot runs The free retrospective
The four-step model, the events your app sends, the decision object and its reason codes, policies, webhooks and sandbox access.
Developer docs
What the SDK reads and where it runs, how data is handled, what the security pack contains, and how to report a vulnerability.
Security review
SIM binding, mule networks, coached payments, injection attacks, reason codes and the rest, defined plainly.
The glossary
India’s rules, scams, mules, hosting and the proof path, answered plainly and with the caveats a bank needs.
Every question
Digital arrest, mule accounts, account takeover, video KYC deepfakes and more: what existing checks see, what DeepID reads, and the decision.
All use cases
Short guides for the people who answer for fraud at a bank. Each one is dated, and each rule and figure in it is cited to its source, with secondary reporting marked as such.
India first, where DeepID was built, then the six markets whose rules follow the same pattern: a real-time rail, the scams that ride it, and the duties that follow. A UPI payment, held before the PIN, has its own page.
DeepID publishes no detection rates and names no customer figures. Every number on this site is a regulator’s or a publisher’s, with its period beside it, and every rule is linked to its text or marked as reported until the text has been read. Where a page describes what DeepID does, it stays within the modules on the platform page: four families, 15 modules, one decision with its reasons.
Proof is always on your own traffic. A free retrospective shows what your history already holds, a shadow proof measures the session signals that only exist once the SDK runs, and one journey goes live against criteria agreed in writing before it starts. DeepID supports compliance and never guarantees it, and it sits beside your FRM, never instead of it.
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.