Which rule each control supports, and what the bank carries from 1 January 2027.
Risk teams start with the decision and the rule map: every control mapped to a dated, sourced rule in each market, and every decision logged with its reasons, the message shown and the policy version. DeepID supports compliance and never guarantees it.
What you measure
On your own traffic
- 01Payments cooled off or held that later proved fraud, against those you reimbursed
- 02Fraud caught that your controls missed, and the false-positive change
- 03Decisions with a logged reason and customer message, as a share of all decisions
- 04Controls mapped to a dated rule in each market you operate in
- 05Time from a disputed payment to the record of what was decided
Agreed in writing before the pilot, against what you see today.
What you start with.
The first question we hear: “What does the bank owe the customer from 1 January 2027, and which control answers each rule?” Most teams start at the payment, with these modules.
One decision, with reasons
DecisionOne decision at each moment, with reason codes, the customer message and the policy version logged.
SIM and device binding
AuthenticationOne customer, one SIM and one phone, bound again only after the face from sign-up holds.
Payee and mule graph
IntelligencePayees linked to mule accounts scored before the money leaves.
What you add next.
The same SDK reads the next moment, so each one you add is checked against what is already bound.
RBI’s 2027 liability framework
What changes on 1 January 2027, and what to do first.
Liability by market
Who pays for scams, market by market.
Scam signals
The coached payment, read before it leaves rather than reimbursed after.
Three things to know.
- From 1 January 2027, RBI’s amendment directions on limiting customer liability in digital transactions apply (RBI, 24 June 2026). The customer is reported to carry zero liability where the bank was negligent, with compensation for small losses (MediaNama, June 2026, press report); check RBI’s text before relying on the terms.
- Every decision carries its reasons, the message shown and the policy version, as evidence of what the bank did and when.
- DeepID supports compliance and never guarantees it, and claims no regulator approval.
Pages to read first.
Where to go next, in the order most risk teams read them, then the teams who sign off with you.
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.