Reports, guides, advisories and articles, all in one place. Every rule and figure is cited to its source, with its publisher and period, and secondary sources are marked.
Longer pieces to keep and share.
One table for compliance and fraud teams: what India, Singapore, Malaysia, the Philippines, Australia, the UAE and Saudi Arabia ask of a bank app at login and at payment, when each rule applies, and who pays when a customer is scammed.
Patterns banks face now, dated and referenced.
Dated articles on the rules and the attacks.
Every DeepID decision carries one id: the same in the app that acts on it, in the event your FRM receives and in the decision log an auditor reads. Here is why, and how it is wired.
No regulator in DeepID’s markets has banned the SMS one-time password. What is changing is where it is enough: at login, for high-risk transactions, and as the floor under every payment.
In a coached payment the real customer signs in on their own phone and approves the payment themselves. Each check does its job, and the money still leaves. What changes the outcome is reading the session as a whole.
The pages teams keep open.
Short, dated guides on the rules now arriving and the fraud they answer.
All guides
Seven markets, each rule with its date, status and source.
The rule map
Fraud and KYC terms, defined plainly, one page per term.
The glossary
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.